"Your cobot definitions were updated"
Looks like this one doesn't do Parkour like Boston Dynamics Atlas (yet), but I read that are units being tested on a Ford plant at US.
Sim Érico, é possível que as diferenças de hardware estejam causando esses problemas.
Antigamente, pra esse tipo de upgrade, você precisaria de uma imagem do KSS 8.3 feita especificamente para o seu controlador. Hoje isso parece ter melhorado.
De qualquer maneira, se você puder postar as mensagens de falha aqui, talvez alguém possa ajudar.
As far I know, VRP 1.1 works with KSS 8.2 and 8.3, and there is a there is a VRP 1.2, that works with KSS 8.2, 8.3, 8.6 and 8.7.
I don't know why, KSS 8.5 was skipped on VRP 1.2 docs, but I almost sure that 1.1 will not work with KSS 8.5.
This option is present on WoV 5.0.10, and I performed a small test here, opening a KSS 8.2.22 project from a robot that uses ProConOS, and the PLC Configuration option worked, but with fewer options.
The file size option refers just to ProConOS file, not WorkVisual project as a whole. But downsizing PLC file will, evidently, reduce the project size.
I think this option is enabled only when You have the ProConOs option on your robot.
Are you sure You robot is KSS 8.3.39?
On picture on first post, It looks like a KSS 8.5 or 8.6.
And, depending on Your KVP version, it will not work with newer KSS, as message "Cannot connect to this device" states.
A robot program, or an external program?
Unfortunately, theres not much information about Panasonic robots in the wild.
Well, this is new to me.
On previous versions of RobotStudio, You couldn't install RW 5.x from Add-Ins tab, but You could download them from there, and install it manually later.
In fact, You can do the same on RS 2020.2, but just with RW 5.16. In 6.08, You could download downwards to RW 5.11.
What is the KSS of this robot, by the way?
You have some bus errors related with robot's internal network. If you have an recent backup/archive, I would recommend You try to restore it.
Was this robot running previously, or its been commissioned right now?
Shut down the robot, and check the green cables inside its controller. Maybe disconnect and connect them again.
Switch on the robot again an see if the problem persists. If yes, maybe You will need to check Your workvisual project.
iosys.ini file is written as follows
I don't remember if the multiplicator is obligatory or not, but on mapping section You can also try this:
Mapping is done on iosys.ini, and looks ok.
It was a long time since I touched a KRC2 with DeviceNet, but If I recall correctly, You should have DEVNET or MFC driver enabled at a time. You shouldn't have the both enabled at same time.
I think in this case, DEVNET should be enabled, and MFC, disabled.
Best option would be RoboDK, that can produce code for lots of brands, has customizable post-processors and is way cheaper than other competitors.
Documentation states that RS 2020.x is compatible with RW 5.07 and onward, but I think is curious that these versions aren't available to download from Add-Ins tab anymore.
I think Install Package will not work on this case, because RW 5.15 wasn't distributed on .rspak format.
But, through Add-Ins page, there is a RobotWare 5.16. Maybe this can solve the problem.
I don't think so. Documentation states that the WoV debugging mode just works on T1 or T2 states.
But if You just want to monitor some variables, You can make a remote access on robot and "bring" the Smartpad to your laptop screen.
The right way to install is running setup.exe, so I think this isn't the problem.
Did You tried to run WoV as Admin, from Windows context menu? I suppose Your user has admin privileges, but I would give it a try.
Also, do you have any antivirus? Maybe stop it for a while.
And, last but not least, did You restarted Windows? You normally don't need to do this, but since WoV install some dependencies, a restart can help in some cases.