12-07-2021, 03:42 PM (This post was last modified: 12-07-2021, 03:43 PM by Phillip.)
Hello, sorry for the slow response
Yes the set digital IO on the driver currently does nothing, I would display a message in the log to tell users as such but that would cause the robodk api to break when communicating with the driver.
As you noted, the IO ports don't match across all the robots and to further add complication, if my understanding is correct these IO ports also need to be connected to real IO's in the ladder programmer for setting and reading these IO values to provide anything useful.
Generally we try and make the drivers and post processor behave as interchangeably as possible. I'm open to suggestions on how best to implement this but from my understanding I just use the value the user sets in robodk directly in the function that the motoman HSE manual calls "I/O Data Reading / Writing Command"
Currently I don't have access to a motoman robot and controller to test significant changes to the driver like adding the underlying function for setting and reading a digital output and dynamically changing a tools center point (TCP) but when I do the version number of the driver will read 6.x.x
12-09-2021, 03:24 PM (This post was last modified: 12-09-2021, 04:20 PM by Phillip.)
No, currently there is no way to set digital IO in real time directly for motoman, you could get around it by creating a program on the controller to set the digital IO and then having the robot driver call that program, you need to uncheck the highlighted option in the attached screenshot in robodk's options in order to forward program calls from the driver to the native robot. In this example setIO would be a jbi file on the robot's controller