I have an ABB IRB 6400 with a s4c controller that has an Ethernet port in place of the floppy disk reader. It was set up to communicate with an older laptop using the software WS_FTP98. How ever this laptop has broke and no longer works. We have a new laptop but I dont know how to get the laptop and robot to communicative with other so I can transfer files like before as it was not me set it up. Can anyone help me out.
laptop to robot via ethernet
-
Sean_MMSNI -
September 7, 2018 at 4:22 PM -
Thread is marked as Resolved.
-
-
Code
IP Address: Laptop PC IP = 192.168.125.82 Robot Service Port IP = 192.168.125.1 Subnet Mask: 255.255.255.240 Gateway: 192.168.125.81
You can try this one. I have a more complete setup somewhere...
I use FileZilla as an FTP client - "Normal" login using "a" as username and password.These would be default settings. If robot was on a network, these values may have been changed.
-
If the robot is configured properly, FileZilla will take care of the job, as Iowan pointed.
But don't forget to save the program or modules inside tje robot HDD. With FileZilla, you can't handle the "real" files.
You will need to save a copy of the desired module (or complete program), download it with FileZilla, edit it, upload it with FileZilla, and load it on the robot from File menu.
-
Thanks, I have downloaded FileZilla What do I do after I plug in the Ethernet to get it to recognise and connect to the robot. Do I have to create a site or what?
-
Set your IP settings on your laptop to what Iowan said, launch filezilla and connect to the robot IP 192.168.125.1
-
Those settings work for my S4C+ controllers - my S4C does not have Ethernet capability. The S4C+ requires an X-start to get to network settings.
My notes said straight cable - which contradicts gut feeling that either crossover or hub/switch would be necessary. You can ping the robot address to verify communication.
Do I have to create a site or what?Once you get all the settings figured out, FileZilla's Site Manager DOES make it easier to re-connect later.
-
Wops - I missed the fact that there was no + in Sean's original post...
S4C's are a different animal all together.
To the best of my knowledge they never had a built in FTP server (like S4C+ or IRC5 does) instead they only had clients for either FTP or NFS (your keystring will tell you which one).
In order to boot them from an Ethernet connection you also need a BootP server (handles the connection and assigns an IP to the client).This was never easy to set up, but once configured and if you liked to edit the install.cmd files you could have it set up so that it cold booted a complete AW system with lots of options in about 5min from power on.
I'll dig through the archives later to see if I can find more on this....
-
No sorry it is an S4+, just a typo. I got it working using the IP addresses Iowan listed. Thanks everyone