I need some help troubleshooting an NCD Wireless 2 Channel 4-20mA Receiver that stopped transmitting.
Here is the situation:
The sensor stopped sending data on January 11th.
I found that the lithium batteries were dead, so I removed the receiver from the machine, disconnected CH1 and CH2, and brought the device to my desk.
I inserted new batteries and now the LED is blinking normally again, so the receiver seems powered and alive.
Before reinstalling it back in the production area, I wanted to perform a bench test to confirm that it can communicate with the NCD EG5120 gateway
My test setup:
Sensor with new batteries, on my desk
Gateway online
Node-RED open
I am monitoring the debug node associated with this sensor (debug 26)
Problem:
The sensor is NOT sending any packets to the gateway — nothing appears in Node‑RED debug for this device. Even after factory reset.
So now I’m unsure what the correct behavior should be:
Is a desk test valid?
Does the sensor transmit even if CH1/CH2 probes are disconnected, or does it only send packets when installed on the machine?
Could I be missing a step to make it communicate again with the EG5120 gateway?
(Pairing, network ID, etc.)
Is it normal that the LED blinks but the gateway receives no packets?
Could the sensor have lost its pairing or configuration when the batteries died? As i said i already performed several hard reset of the receiver and also restarted the gateway from its dashboard.
At this point I’m not sure if:
The bench test is not valid,
The sensor needs to be re-paired with the gateway,
Or if I’m simply not triggering the correct transmission test.
Any guidance on how to properly test the sensor on the bench — or how to ensure it talks to the gateway again — would be greatly appreciated. Thanks!!
Hi @davidemagno First, I recommend monitoring the battery levels on your sensors. A good rule of thumb is to schedule a battery replacement once the voltage drops below ~2.9V.
Regarding your bench test, the setup appears correct, and the sensor should be communicating with your gateway. To help us narrow down the cause of the connection issue, could you please confirm the following:
Antennas: Are the antennas securely connected to both the gateway and the sensor?
LED Diagnostics: Could you describe the LED behavior on the sensor after you press the Reset button?
Hi @Eduardo_Mtz thanks for the quick reply!! regarding our battery alerts, they are triggered when the battery level is lower than 20%. We use the battery level which is a percentage. More in general, alerts are trigged only by analyzing a json message sent by the sensors, which contains in the body said values, see image attached
But the problem is, the sensors didn’t sent some messages regularly and I don’t know why. It seems like we have messages only when a machine is running…
regarding the antennas, they are secured, not problem in that. Led keeps blinking regularly on “test” light. If i press reset, the blinking stops for a second, then starts again normally. I don’t see anything strange also in that
Hi @davidemagno could you attach a video of the LED behavior after pressing the reset button, this will help us to determine if the he Wireless Radio module might be damaged.
attached you find the recording. Do you also have any insights regarding the other points that i have highlighted (sensor sending data only when machine is running: is this even plausible or my false guessing? is desk test valid, and if so, how to make it possible?). Please notice that i am not the person who configured these sensors in first place, so i appreciate your efforts and patience
Hi @davidemagno thank you for the information. Double blink means device cant talk to the wireless radio module. Could you try a factory reset and share your results please:
Press and release the RESET button
Wait for a second, then press and hold the CONFIGURATION button
Hold the CONFIGURATION button for about 20 seconds
Hi @davidemagno do you have another sensor nearby that we could use for a quick test? I would like to swap the wireless radio modules between the two units to see if the issue follows the radio
@Eduardo_Mtz i have a similar issue with another sensor, where the batteries died on july 2025 and no one replaced them. Now with new batteries the LED blinks twice. What is the best way to diagnostic RF module issues, apart from switching them? I have to either buy a NCD USB Modem or send it to your support team each time, or are there any alternatives? Thanks
n the 868 MHz module, the radio module’s memory can sometimes become corrupted due to brownouts. We have discussed this issue with the radio manufacturer, but so far, they haven’t provided a solid explanation. The onboard MCU attempts to recover the memory; however, if it fails, it will stop trying and start flashing the LED.
In the newer designs, we are adding some additional guardrails to address this issue. You don’t need to use a USB modem; a board like this can be utilized instead.
Hi @Bhaskar thanks for the useful insights!! this clarifies what i am experiencing here. Now, before buying the USB Configuration Adapter, I would like to understand a few things:
How difficult is it in practice to reprogram a corrupted 868 MHz module?
Is there a step‑by‑step guide or tool that makes the process mostly “click and configure”, or is it a low‑level/XCTU‑style procedure?
Which exact parameters do I need to know to bring the module back into my existing DigiMesh network?
For example:
network ID / PAN ID
encryption key or password
sleep mode / baud rate / firmware profile
any NCD‑specific settings that must match the EG5120 gateway
Also where can I obtain these parameters? How likely is it that an incorrect setting would make the module unusable?
Thanks a lot for the info and your support, it was great. For now, I’ll send you two modules that aren’t working, until I get the adapter and i figure out how to use it. I’ll let you know as soon as the shipment is ready.
