Hello,
We can connect our robot and run programs on it in RoboDK but when we try to send program to robot selection, it gives "bad authentication" error.
service_key.pem is copied at Robodk/api folder and the other settings are also set but we are getting the error.
Also explore button redirects to filezilla but connection gives ECONNREFUSED error.
If I connect the robot with Keba Driver, it connects but can't create an FTP connection.
Connection protocol should be SFTP but Filezilla starts an FTP connection with port number 21.
I tried something different. If I connect to UR5 (or any other Universal Robot), it connects with SFTP and port number 22.
So if you change the driver of UR5 from "apiur" to "Keba Driver" you can connect to your Keba robot and create an SFTP connection.
But those are not fixing our main problem. Is there any solution? Anyone else?
(07-23-2024, 03:21 PM)Phillip Wrote: It appears that for whatever reason the robot is configured to only accept FTP files via keys (hence the 'publickey' response from the server).
We have already followed instructions outlined but there is an issue with port number. Connection protocol should be SFTP but Filezilla starts an FTP connection with port number 21.
As @h_orhun mentioned; if we connect UR5, it connects with SFTP with port number 22. Then, if we enter credentials for KEBA and change driver to "Keba Driver" from "apiur", we can connect Filezilla and use button "Send Program to Robot"(Ctrl + F6).
But this is not fixing our main problem. Is there a way to change the configuration for only accepting FTP files via keys to SFTP?
07-31-2024, 02:15 PM (This post was last modified: 07-31-2024, 05:59 PM by Phillip.)
There was an issue with the compiled version. It will be fixed in the next version of RoboDK. You can copy and overwrite the existing file in C:\RoboDK\Posts with the one attached to this post. I was able to reproduce your issue with the version installed directly with RoboDK and it has since been fixed.