Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: PLCwannabe on October 15, 2024, 10:32:24 AM
-
Just noticed an issue with a BX-DM1E that i recently updated to 2.10. The first 3 blocks of Peerlink do not subscribe to the network, all values remain at 0. I have multiple plcs on the same network that all continue working well with peerlink with all blocks. In memoryview, some of the PL registers are whited, even though they are not used in the program, not sure if this is part of the issue.
-
Just noticed an issue with a BX-DM1E that i recently updated to 2.10. The first 3 blocks of Peerlink do not subscribe to the network, all values remain at 0. I have multiple plcs on the same network that all continue working well with peerlink with all blocks. In memoryview, some of the PL registers are whited, even though they are not used in the program, not sure if this is part of the issue.
Not sure.
It appears to be working as expected and there were no (intentional) changes to PEERLINK for 2.10. Your status display is indicating that the PLC is receiving those blocks, so I'm really not sure what might be going on.
-
It was working at some point, the pl0-47 registers were populated with valid data, but I'm not sure when that data was recieved, I'm assuming before the update happened. I only started using the registers yesterday and noticed that they are not working. I've powered down and rebooted multiple times, with no success. Is there anything else I can try?
-
It appears from the PEERLINK status that those first 3 blocks are inhibited (by the publisher and/or subscriber). Blocks 1, 2, and 3 in your PEERLINK status screen shot appear to be grayed out. Check out your PL.xxInh "Inhibit" bits in a Data View (check all the PL heap item structure members and make sure they are all what you expect - some are readonly, some are read/write)
From the PEERLINK help topic DMD0300:
Green, Yellow, or Red background with Grayed Numeral indicates that updates to the block have been inhibited,in the example above Blocks 3 and 5 have their updates inhibited. The inhibit bits for the blocks allow both the publisher and the subscribers to control updates to the CPU's PEERLINK memory.
In the PLC that is publishing the block, setting the inhibit bit prevents that block from being published.
In the PLC that is subscribing to a block, setting the inhibit bit prevents that block from being updated in the CPU.
-
It appears from the PEERLINK status that those first 3 blocks are inhibited (by the publisher and/or subscriber). Blocks 1, 2, and 3 in your PEERLINK status screen shot appear to be grayed out. Check out your PL.xxInh "Inhibit" bits in a Data View (check all the PL heap item structure members and make sure they are all what you expect - some are readonly, some are read/write)
From the PEERLINK help topic DMD0300:
Green, Yellow, or Red background with Grayed Numeral indicates that updates to the block have been inhibited,in the example above Blocks 3 and 5 have their updates inhibited. The inhibit bits for the blocks allow both the publisher and the subscribers to control updates to the CPU's PEERLINK memory.
In the PLC that is publishing the block, setting the inhibit bit prevents that block from being published.
In the PLC that is subscribing to a block, setting the inhibit bit prevents that block from being updated in the CPU.
Good catch. My monitor contrast made that kinda subtle.
-
Okay, so that was the issue, the inhibit bits were on, not sure how that happened.I didn't even realize that they existed, before browsing through the help topic.In my defense, the greyed out numbers are very hard to distinguish from the black, even on the monitor itself. Thanks for the quick resolution.