Remote Module Warning

[franji1]

What is the value for X16:UW (i.e. the 16 bits of X16 thru X31 as an UNSIGNED WORD)?

You can enter that in Data View.

[RBPLC]

Currently running 2.8.3 Production. See the same thing on two computers. One running Win10 the other Win7. X16:UW is 0. No individual bits are showing on.

[MikeS]

can i assume the firmware in your BXEBC100 is up to date (v4.2.133) it needs to be at least v4.2.120 or later as we fixed an error reporting issue in that version.

i haven't been able to dup this problem using your arrangement of modules, so if you're game i'd like to try single stepping through the setup to see where the problem shows.

the EBC100 can only have one master, so you'll need to temporarily disconnect your CPU as the master by powering the CPU down or unhooking the ethernet cable from the master.

then fire up the Do-more Simulator and configure it to be the Ethernet I/O master, add that ebc100 as the slave - but don't configure the UT yet - simply add the slave (remember to increase the Timeout in the Slave Config to 150ms), save the config, download it to the Sim, and go to RUN to see if that works with no errors or warnings.

if that works cleanly, configure the UT module as it should be, 6 channels enabled and proper probe type. then save the config, download, and see if that still works cleanly.

if we're still good, then induce a problem - remove one of the wires from one channel - that should cause a warning. Open the I/O System view to make sure it's the right channel showing the warning. then replace the wire and see if that warning goes away.

If the I/O System View is still open, the warning should clear itself.
If the I/O system View is NOT open, the warning will remain until you manually clear it.

[RBPLC]

can i assume the firmware in your BXEBC100 is up to date (v4.2.133) it needs to be at least v4.2.120 or later as we fixed an error reporting issue in that version.

Yes. v4.2.133

then fire up the Do-more Simulator and configure it to be the Ethernet I/O master, add that ebc100 as the slave - but don't configure the UT yet - simply add the slave (remember to increase the Timeout in the Slave Config to 150ms), save the config, download it to the Sim, and go to RUN to see if that works with no errors or warnings.

Setup the slave with the three installed modules shown in posted photo. Poll rate 50ms, timeout 150ms. Without setting the 08UT up, download to controller and get the warning message indicating "This module is reporting an error".  Configure 08UT with 6 TC's, re-download, seems to be reading correct temperatures but with warning message still displayed.

[MikeS]

This tough, i have exactly that layout and can't duplicate what you're seeing.

I did notice one difference in I/O System View that may be a clue, when i induce an error on the one channel i have configured, i see text expounding on what the actual error is:

[RBPLC]

Without unplugging the 6 TC's that I currently have installed, if I change all channels to 10k thermistors as you've shown, I get out of range and burn out errors for channels 7 and 8. For reference, when I do this, the error bits show up as well.

[MikeS]

are you familiar with Wireshark - the ethernet packet trace software? we use it to debug the packets between ethernet clients and servers. Would you be willing to try to capture a packet stream between the SIM and the EBC100 so that we can see what questions the SIM is asking and what answers the EBC100 is giving.

What appears to be happening is the EBC100 is telling the CPU that is has a problem with one of the modules, but when CPU queries the EBC100 for the error/warning information there's nothing reported. Seeing the contents of the packets gives up the ability to trace back through the code to see what's going wrong.

[RBPLC]

I've only briefly tried out wireshark. Never attempted to capture info. I don't mind trying, it's something I need to add to my toolbox. Is there be some other firmware/booter/configuration setting that I need to check?

[MikeS]

no other configuration settings of concern, that's the reason i wanted you to use the Do-more Simulator as the master, so there'd be a clean sysconfig and no ladder program that could be interfering in any way.

pretty much all you need to do is get the simulator running and showing the warning that won't go away, then start Wireshark, click the shark fin button on the toolbar to start a capture, let it run for about 10 seconds so that it will capture several transactions between the SIM and the EBC100, then click the red square to stop the capture. save that trace to a file then email it to us at Support@Hosteng.com.

[RBPLC]

The attached is a third system running with the simulator with a EBC with firmware version 4.2.123. One image shows all channels configured for TC with no TC's plugged in. All the error bits are present but nothing in the I/O monitor window. The other image is with only the first input configured for TC with no TC's plugged in.

[RBPLC]

I've emailed two different Wireshark captures for troubleshooting purposes.

[BobO]

I've emailed two different Wireshark captures for troubleshooting purposes.

We looked through the traces. It appears that the module status function wasn't returning all of the errors to DmD. Not sure if this is *the* error, but it appears to be *an* error. We've fixed it, and can send you new EBC firmware if you'd like to try it.

[RBPLC]

Yes. I've got time to try them currently as my systems that these are installed on aren't running at the moment.

[BobO]

Yes. I've got time to try them currently as my systems that these are installed on aren't running at the moment.

Same email as the traces?

[RBPLC]

Yes.