+- RoboDK Forum (//www.sinclairbody.com/forum)
+-- Forum: RoboDK (EN) (//www.sinclairbody.com/forum/Forum-RoboDK-EN)
+ - - -论坛:通用RoboDK问题(//www.sinclairbody.com/forum/Forum-General-questions-about-RoboDK)
+--- Thread: Unstable connection with TM12 (/Thread-Unstable-connection-with-TM12)
Unstable connection with TM12-MarcoB2A-06-07-2023
Hello,
I have a TM12 running its TMFlow software and works as expected.
Then I have tried to "run-on-robot" my simple test program, creating a TM12 project as suggested
on this RoboDK guide:
//www.sinclairbody.com/doc/en/Robots-Omron-TM.html#TM-StartProg
but the connection seems unstable; sometimes the job start and sometimes not.
The speed when it runs is not that set on RoboDK, and only one movement is executed...
I have doubts about the parameters to use in the suggested TM12 project about listen-node and wait-for objects, because not specified in the example...
Have you useful details about this Listener to create on TM12?
Regards
PS: found also a strange (wrong) behaviour when I ping the robot from RoboDK;
Often I get Success even with ethernet cable disconnected from TM12...
Of course from terminal the ping Fail as expected.
RE: Unstable connection with TM12-Albert-06-07-2023
Are you setting linear speeds or joint speeds? Can you send us the RoboDK project file?
Once you senter a listen node you don't need to worry about other nodes.
Regarding the ping issue: Are you using Windows? Can you send us a print screen of the result of the ping through the terminal and what you get through RoboDK?
RE: Unstable connection with TM12-MarcoB2A-06-07-2023
I am working with linear speed.
I was wondering if the Timeout and Delay values I have put in the "listen-node" and "wait-for" objects of TM12,
could influence stability connection with RoboDK...
RDK project and screenshot, from windows, in attach.
Regards
RE: Unstable connection with TM12-MarcoB2A-06-08-2023
A quick update;
I have found that in the TMflow objects (Listener and Waitfor) it's better leave all values to zero.
Then the program was stopping due to RoboDK disconnection after the first movement,
because of an I/O instruction which seems leave in timeout the RoboDK comms...
Removing the I/O instruction the program is fully executed on the robot.
Note that the Digital Ouput is set correctly on robot, but seems that RoboDK do not receive an acknowledge or is unable to handle it...