01-30-2019, 08:12 AM
(01-29-2019, 02:50 PM)Jeremy Wrote:Hi Andy,
Just to be sure that we start on the right foot, the KUKAVARPROXY.exe is on the desktopof the robot controller?Right? (Kuka controllers are running embedded version of Windows.)
//m.sinclairbody.com/doc/en/Robots-KUKA.html#DriverKUKA
Hi Jeremy,
Yes, kukavarproxy.exe is on the desktop of the Controller. I have also pasted it into the startup folder so that it automatically starts on bootup of the robot. The pop up screen appears but it does not seem to do anything , is that normal ?
As I said to Albert I have not been able to locate the MainCom.src file in order to copy it into KRC\R1 it was not in the folder of files sent to us by Albert.
RoboDK远程桌面欺诈nected to the controller via LAN cable. I have disabled the Firewall on the Controller just in case it was interfering with the connection.
I have tested the apikuka.exe and the system gives me a message "The code execution cannot proceed because Qt5 network.dll was not found"
I did an ipconfig to find the controller IP to verify it was right. It does Ping successfully, but when we try to connect the robot via Robodk the system just keeps looping its attempts to connect without success.
Would it be better to install RoboDK on the robot controller directly to avoid networking problems ??
The Robot tool is only a very small enabler to my overall PhD Research so I am desperate to get this working now as I need to proceed in the other areas.
Thank you an advance for your assistance it is very much appreciated.
Andrew
p.s. I have been over the installation procedure document a few times now to make sure that I have not done something stupid. But all seems to be in place apart from the above points.