Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: JeffS on November 06, 2025, 04:38:47 PM
-
I have a remote IO module reporting a configuration mismatch on Slot 255. I tried re-writing booter/firmware, reset defaults, rewrote booter/firmware to the BRX Master with no luck. I am assuming this remote IO module is dead, but wanted to report the odd message.
-
So the customer replaced the BX-DMIO and it is still showing an error light on the DMIO and when I log into the BRX PLC I see the same Slot 255 error.
So at this point I guess the BRX Master is the bad component here, just very misleading as the error points toward the DMIO device?
-
So the customer replaced the BX-DMIO and it is still showing an error light on the DMIO and when I log into the BRX PLC I see the same Slot 255 error.
So at this point I guess the BRX Master is the bad component here, just very misleading as the error points toward the DMIO device?
Slot 255 actually points to the onboard I/O, which there isn't any. It isn't a hardware problem, it's probably garbage in the config. I've been out on vacation, but I'll look into it when I'm back in the office.
-
So I sent them a new PLC and they got the same error. I had them factory reset the PLC (Dips and RUN/TERM/STOP dance) and I remotely reloaded the program and got the same error. I am only getting this error at this one site luckily, but so far not able to rectify it. This setup ran fine last year and nothing has changed on the system (no changed code/sensors/wiring). They were running 2.9.6 firmware so I did update to 2.10.3 but the error persists.
So at this point we replaced the BX-DMIO and the BX-DM1E-M-D, initially restored the new PLC from a backup of the old PLC, then since the problem persisted, factory reset that PLC using run/stop dance, reloaded from a clean copy, and the problem persists.
Any thoughts on what to check next?
-
I've been communicating with JeffS off the forum, but to complete the public record, we found a bug in the Ethernet Master where in certain conditions (rare, I think), the master sent a malformed request that resulted in this symptom. The fix will be in the next OS to be released shortly.
-
Today we got the Slot 255 Error. This is a system that has been running for several months with no glitches. I updated firmware (from 2.9.x to 2.10.2) and gate array but was unable to get it to RUN mode because of the error. After power cycle on the PLC, it came back with no errors and it went right into RUN mode, all looks good.
Is the Ethernet Master bug also present in firmware 2.11?
-
Today we got the Slot 255 Error. This is a system that has been running for several months with no glitches. I updated firmware (from 2.9.x to 2.10.2) and gate array but was unable to get it to RUN mode because of the error. After power cycle on the PLC, it came back with no errors and it went right into RUN mode, all looks good.
Is the Ethernet Master bug also present in firmware 2.11?
So you got this on 2.10.2? Or 2.9.x?
-
The error occurred on 2.9.x.
I upgraded the firmware before power cycling but I don't know if the firmware update was neccessary, maybe a power cycle on 2.9.x would have fixed it.
-
The error occurred on 2.9.x.
I upgraded the firmware before power cycling but I don't know if the firmware update was neccessary, maybe a power cycle on 2.9.x would have fixed it.
Did you upgrade EBC/DMIO before it happened?
-
I only upgraded firmware on the PLC/DM1E. Didn't upgrade the DMIOs (I have two of those). Works like a charm now.
-
Today we had another stop on the PLC that previously gave me the Slot 255 error. Unfortunately, I was unable to remotely connect to the system and thus unable to inspect the error. But I suspect another occurence of the Slot 255 error. The operator power cycled the PLC and the system is now up and running.
Is there any planned release date for the fix?
-
v2.11.2 contains the fix we made for that problem. It's available for download through Help -> Check for Updates.
-
Great, thank you!
This is a fix for the PLC (DM1E), right? Do I need to update the DMIOs too?
-
Correct, it is only a fix for the CPU. As a general rule, we recommend keeping the DMIOs up to date on firmware.