Roboguide to AB PLC?

    Is you UOP I/O setup in the same slot as the rest of your Ethernet/IP?

    I believe I found it in another thread on this forum, but Roboguide does not like the UOP to be on the same slot as anything else. On my project my Ethernet/IP was on Slot 1. I configured the UOP to be on Slot 2 and the UI inputs now work correctly. For whatever reason though Roboguide still over rides the colors of some of the UI.

    Anyone have any luck with writing position registers from AB PLC to RoboGuide? Everything else seems to work (read/write DI/DO/UI/UO/R)...I can read the PR's...just not write to them. I'm guessing there's either another variable preventing this...or it's a limitation of RoboGuide.

    Any thoughts?

    Update:

    My issue was related to my custom data type on the PLC side of the equation. No issues with RG...I'm able to write to PR's without issue after I modified the PLC.

    Edited once, last by sgarthwa: Update (June 10, 2022 at 4:29 PM).

    try changing the Sys variable $RMT_MASTER to 0. it should work.

    I am also facing the Same problem. Have you got a solution for this?

    Quote from lexx905

    Thank you! it works. I now connected RG and the robot via EiP. The software 8.30.

    hi, i have sucessfully connected but small problem some of the UOP signals not working like RSR/PNS/Style selection bits do not get ON even if I turn it on from PLC same with UI18 production start . any Idea why it is happening. I am sure it has nothing to do with I/O assignment. because Other UI signals are working like HOLD signal CSTOP etc

    Quote from ttsjithin

    hi, i have sucessfully connected but small problem some of the UOP signals not working like RSR/PNS/Style selection bits do not get ON even if I turn it on from PLC same with UI18 production start . any Idea why it is happening. I am sure it has nothing to do with I/O assignment. because Other UI signals are working like HOLD signal CSTOP etc

    Hi ttsjithin,

    found some time to go one with this again, had to re-read the treads again to know where i was the last time. :smiling_face:

    Anyway : Did you managed to get the setup running ? because it seems we where facing the same problem, being the PNS slection not being high nevertheless the PLC sends is a logical 1

    any help would be great...

    Unfortunately its not working for me and I gave up. But I have seen a video on YouTube where it was working, unfortunately he has not shown the connectivity/settings to follow. Hope those who claimed that they run this will provide insight into this matter

    Hi everyone. I've been following this thread and some other threads. I've got an AB 5069-L320ER PLC talking to roboguide, and I've been successful with reading DOs and numeric Registers FROM the virtual robot, but I can't seem to figure out how to write to numeric registers and turn on DIs from the PLC. I've got the EIPCFG.XML setup the same way I use in real life (which I know works). I read and write the default adapter setup for DI/DO which is 4 words. But we also read and write 50 numeric registers.

    Has anyone else had this issue?

    The PLC is seeing the virtual robot and not giving any communication faults, but when I set a DI bit to 1 in the PLC, I'm not seeing it come on in the robot controller. I've not mapped any UI or UO to EIP rack either.

    PLC is sitting on the office network: PLC IP address is set to 192.168.1.10

    Laptop IP address is set to 192.168.1.240, roboguide IP address is set to 192.168.1.240, subnet 255.255.255.0. Laptop also is connected to the office network. My laptop's original ethernet port is shot, so I use a USB3 to gigabit ethernet adapter (not sure if this is affecting things). The usual office IP addresses are something like 10.20.20.xxx and gateway is 10.20.20.1 (also not sure if this would cause issues). The PLC can be routed directly to my laptop, but I'd prefer not to do that.

    Additionally, I couldn't get the PLC to even see the virtual robot controller until I set the router address in the virtual controller to be 192.168.1.1.

    Thank you all for your patience and your time.

    UPDATE: I realized that the PLC I was using was not in run mode, so it wasn't sending any of the data out. Once that was fixed, the writing to the registers and turning on DIs worked. :uglyhammer2:

    Edited once, last by IanMSmith (December 22, 2022 at 12:20 AM).

    Quote from Scipio

    Hi ttsjithin,

    found some time to go one with this again, had to re-read the treads again to know where i was the last time. :smiling_face:

    Anyway : Did you managed to get the setup running ? because it seems we where facing the same problem, being the PNS slection not being high nevertheless the PLC sends is a logical 1

    any help would be great...

    Hi Scipio, in the past I contact FANUC roboguide teams and what you need is just change a key in the windows register

    PNS_RSR signal control by Roboguide :

    [HKEY_CURRENT_USER\Software\VB and VBA Program Settings\RGCore\Settings]

    "MapPnsRsrSignals"="True"


    PNS_RSR signal control manually by user (or PLC):

    [HKEY_CURRENT_USER\Software\VB and VBA Program Settings\RGCore\Settings]

    "MapPnsRsrSignals"="False"

    Thank you! That works!

    For anyone without working UOP Signals, I hope this helps.
    Just got it from Fanuc, haven't tested it myself until now.

    Imgur
    Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining…
    imgur.com

Advertising from our partners