ros-industrial / staubli_val3_driver

ROS-Industrial (simple message) driver for Stäubli CS8 and CS9 robot controllers (VAL 3 application)
Apache License 2.0
26 stars 21 forks source link

Question - How to transfer val3 from USB to the controller? #28

Closed Niknu closed 3 years ago

Niknu commented 3 years ago

Hi there,

I'm not sure how I should transfer the val3 driver to the controller, you are writing as followed:

" There are multiple ways of transferring VAL 3 applications to the controller:

  1. Copy the contents of val3 folder onto a USB memory stick (<2GB if using CS8), plugging the stick into the controller and using the teach pendant to copy the folders "

In my case, I have a CS8 controller and the controller can see the USB stick with ros_libs + ros_server. But when I try to load the ros_server it says something with the incorrect type in SimpleRosMsg on the line 1.

I'm doing it correctly, or?

pratipo commented 3 years ago

same here, not using SRS

i managed to upload both folders using filezilla you need to plug your controller to the network and check the ip in the control panel -using the pendant-, then use

host:192.168.1.10/usr
username: default
password:
port:

inside /usr there is a folder called /usrapp where you place the 2 folders

controller: cs8c val: 7.11.2

gavanderhoorn commented 3 years ago

This starts to sound a bit like #27. Could you both take a look?

Niknu commented 3 years ago

I have tried to clone and download zip on Linux and Windows. It doesn't work with the #27 solution,

What I have is :

Controller : cs8 System: s.7.9.1

Below is images of what I assume is needed information

IMG_20210219_110819 IMG_20210219_111027 IMG_20210219_111537

When I see the Event loggers output

IMG_20210219_111553 IMG_20210219_111615 IMG_20210219_111619

gavanderhoorn commented 3 years ago

So both with the .zip as with git clone gives you these errors?

And #27 wasn't really intended to be a solution. It was just a reference to an issue which seems similar.

gavanderhoorn commented 3 years ago

As this seems to be the same -- or a similar enough -- error as in #27, I'd like to suggest we re-open #27 and continue there.

gavanderhoorn commented 3 years ago

I'm going to close this one, we'll continue in #27.