Hardware issue of IoT Wireless One Channel Counter

I have 2 units of IoT Wireless One Channel Counter (PR52-3B) working on 2.4GHz. Additionally, I have the IoT Wireless USB Modem for sensor configuration and the Enterprise IIoT Gateway Lite for the sensor gateway (both operating at 2.4GHz).

When the modem was connected to my laptop (using the FTDI driver), the Alpha Station software couldn’t detect any of my sensors (which were in battery mode).

I used the Enterprise IIoT Gateway (Robustel EG5100) to connect to my sensors using Node-Red. I successfully configured it and adjusted the time delay. Node-Red received the data without any issues. However, when I triggered the sensor count terminal, the device would hang up and stop sending data until I powered the sensor off and on.

Please assist me with this issue if I missed something important in the sensor configuration.

Thank you.

Hi,

Just in case something got set incorrectly you can factory reset the sensor as explained in the user guide here:

Please give that a try and let us know what you find.

Thank you,
Travis Elliott

Hi @rhettmark, If you perform the factory reset mentioned by Travis and the issue persists, then:

  1. Could you please provide screenshots of your Node-RED sensor configuration?
    (Also the messages you get in Debug tab inside Node-RED)
  2. What values did you use for the Delay, Counter Threshold, and Input Debounce Time settings?
  3. What type of sensor is connected to the meter’s digital input? If possible, could you share a picture of the sensor setup?

Let us know what you find or if you have any question.
Thank you,
Eduardo M.


I tried this instruction but it did not reset to default.

1. Could you please provide screenshots of your Node-RED sensor configuration?
(Also the messages you get in Debug tab inside Node-RED)

these are the data from Debug 1 and Debug 3:

7/9/2024, 10:18:56 PM[node: debug 1]
(http://192.168.0.1:1880/#)sensor_data : msg : Object

object

topic: “sensor_data”

data: object

nodeId: 2

firmware: 6

battery: “3.29”

battery_percent: “99.64”

counter: 15

sensor_type: 35

sensor_data: object

counts: 0

sensor_name: “One Channel Counter”

type: “sensor_data”

addr: “00:13:a2:00:42:0c:33:2c”

received: 1720534727544

original: object

modem_mac: “00:13:A2:00:42:0C:31:69”

payload: object

time: 1720534727547

_msgid: “b1df931aed5cc190”

7/9/2024, 10:18:56 PM[node: debug 3]
(http://192.168.0.1:1880/#)sensor_data : msg.payload : Object

object

nodeId: 2

addr: “00:13:a2:00:42:0c:33:2c”

counts: 0

received: "2024-07-09 22:

2. What values did you use for the Delay, Counter Threshold, and Input Debounce Time settings?
Node ID and Delay
Active: enabled
Node ID: 2
Delay: 15

Power
Active: disabled
Value: +24 dBm (250 mW)

Retries
Active: disabled
Value: 10

Counter Threshold
Active: disabled
Value: 50

But I don’t see any Input Debounce Time in the config properties.

3. What type of sensor is connected to the meter’s digital input? If possible, could you share a picture of the sensor setup?

I used relay timer with 0.1 sec OFF delay timer (one shot pulse for 0.1 sec)

Thank you.

You will need to update the node red lib and then set the deboucne time to 30msec.

I just updated the Node-Red library and reboot the system,


the version now is 1.0.2

But I can’t still find the Deboucne time parameter,

please help.

For clarification of the sensor’s digital input (CH 1 & COM), is this can be used for any dry contact from timer relay?

I saw in the sensor’s documentation regarding this,

the connectivity is just a contact from COM to CH1?

Thank you!

correct, to trigger the CH1 connect VCH1 with COM.
@jacob is lib live ?

If my trigger is correct but why the sensor’s input will not count properly?
Any advice pls on how this sensor’s counts working?

Hi @rhettmark, I share you the step-by-step to update the NCD Node-RED Library:

  1. Access Node-RED:

  2. Click on the main menu (three vertical lines) located in the top right corner of the Node-RED editor.
    Select the option “Manage Palette.”
    main_menu

  3. You’ll see the currently installed libraries. Locate “@ncd-io/node-red-enterprise-sensors” and click on “Update” in the bottom right corner of the box.

(NOTE: you should see in button “Update to 1.0.3”.)

  1. The update process will start automatically. Once completed, you’ll see a message displayed in the middle section.

Restart Node-RED: You can restart Node-RED by importing a simple flow:

  1. Copy the following flow.
[{"id":"484bbb685325d602","type":"inject","z":"659f98d7808980b1","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":260,"y":260,"wires":[["6d3c86433f09e5f3"]]},{"id":"6d3c86433f09e5f3","type":"exec","z":"659f98d7808980b1","command":"pm2 restart all","addpay":"","append":"","useSpawn":"false","timer":"","winHide":false,"oldrc":false,"name":"","x":440,"y":260,"wires":[[],[],[]]}]
  1. Go back to Node-RED and select “Import” from the main menu.
    import

  2. Paste the copied flow into the text input box and click “Import.”

  3. Click the “Deploy” button (top right) to save and apply the changes.

  4. Click the button next to the Inject node (right side) to trigger a restart command.
    flow

  5. Finally, refresh the web page where Node-RED is running.

You should now see the “Set Input Debounce Time” property within the “Wireless Device” node. Check the box and enter the value of 30, as recommended by @Bhaskar.
debounce

Please try this and let us know how it goes! We’re here if you have any questions.
Thanks,
Eduardo M.

Hello @Eduardo_Mtz,
I successfully followed your instructions.
Then I check the sensor’s counts, I found out that the sensor will restart after a series of counting.

pls check the debug results,

7/11/2024, 8:08:04 AM[node: debug 1](http://192.168.0.1:1880/#)sensor_data : msg : Object

{ topic: "sensor_data", payload: object, time: 1720656468045, _msgid: "080839b70cfc56d1" }

7/11/2024, 8:08:04 AM[node: debug 3](http://192.168.0.1:1880/#)sensor_data : msg.payload : Object

{ nodeId: 2, addr: "00:13:a2:00:42:2a:34:e6", counts: 1, received: "2024-07-11 08:07:48" }

7/11/2024, 8:08:10 AM[node: debug 1](http://192.168.0.1:1880/#)sensor_data : msg : Object

{ topic: "sensor_data", payload: object, time: 1720656474306, _msgid: "cae76e6b3510cc35" }

7/11/2024, 8:08:10 AM[node: debug 3](http://192.168.0.1:1880/#)sensor_data : msg.payload : Object

{ nodeId: 2, addr: "00:13:a2:00:42:2a:34:e6", counts: 2, received: "2024-07-11 08:07:54" }

7/11/2024, 8:08:16 AM[node: debug 1](http://192.168.0.1:1880/#)sensor_data : msg : Object

{ topic: "sensor_data", payload: object, time: 1720656480562, _msgid: "9ce55bf7446eb09b" }

7/11/2024, 8:08:16 AM[node: debug 3](http://192.168.0.1:1880/#)sensor_data : msg.payload : Object

{ nodeId: 2, addr: "00:13:a2:00:42:2a:34:e6", counts: 3, received: "2024-07-11 08:08:00" }

7/11/2024, 8:08:21 AM[node: Format Data](http://192.168.0.1:1880/#)function : (error)

"Invalid payload structure received"

7/11/2024, 8:08:21 AM[node: debug 1](http://192.168.0.1:1880/#)sensor_mode : msg : Object

object

topic: "sensor_mode"

payload: object

mac: "00:13:a2:00:42:2a:34:e6"

type: 35

nodeId: 2

mode: "RUN"

lastHeard: 1720656485656

time: 1720656485657

_msgid: "0b1b1fcca76dc580"

7/11/2024, 8:08:22 AM[node: debug 1](http://192.168.0.1:1880/#)sensor_data : msg : Object

{ topic: "sensor_data", payload: object, time: 1720656485879, _msgid: "2275c708da906731" }

7/11/2024, 8:08:22 AM[node: debug 3](http://192.168.0.1:1880/#)sensor_data : msg.payload : Object

{ nodeId: 2, addr: "00:13:a2:00:42:2a:34:e6", counts: 0, received: "2024-07-11 08:08:05" }

I noticed at 7/11/2024, 8:08:21 AM[node: debug 1]
the transmitted data was different with “Run Mode”?

object

topic: “sensor_mode”

payload: object

mac: “00:13:a2:00:42:2a:34:e6”

type: 35

nodeId: 2

mode: “RUN”

lastHeard: 1720656485656

time: 1720656485657

_msgid: “0b1b1fcca76dc580”

Then the succeeding data count will reset to zero,

Object

{ nodeId: 2, addr: “00:13:a2:00:42:2a:34:e6”, counts: 0, received: “2024-07-11 08:08:05” }

Please see the screen shots of my Node-Red flow and config:

Please advise what should I do to fix this issue.

thank you,

Hi @rhettmark
Yes, when a reset is performed on the sensor, the counter also resets. However, let me ask you the following:

  1. Could you share the battery level percentage that the sensor is reporting?
  2. Could you try to power the sensor with an external power supply and see if the issue persists?
  3. If the sensor is not counting (there is not digital input), the reset persist?

Thank you,
Eduardo M.

1. The Battery value is the same:
7/11/2024, 8:08:22 AMnode: debug 1sensor_data : msg : Object

object

topic: “sensor_data”

payload: object

nodeId: 2

firmware: 6

battery: “3.29”

battery_percent: “99.64”

counter: 1

sensor_type: 35

sensor_data: object

counts: 0

sensor_name: “One Channel Counter”

type: “sensor_data”

addr: “00:13:a2:00:42:2a:34:e6”

received: 1720656485879

2. I used 12V DC for external power supply (I tried 30, 50, 80, 100 Input Debounce Time), the issue regarding RESET did not occur, but afterwards the sensor stop sending data and were not getting any counts.
It needs to press the reset button to start the transmission again.

3. If the sensor is not counting (there is not digital input), the reset persist? No, the sensor continuously sending data (without digital input activity).

Pls advise.

thank you,

can you measure voltage between
COM and Gnd
CH1 and Gnd
Reset and Gnd

If you remove the relay and just short CH1 and COM does the counter increments ?

ps- The installation looks great

1 Like

Hello Bhaskar,

Battery Mode:
COM and Gnd = 3.264V
CH1 and Gnd = No Voltage (100k ohms Resistance)
Reset and Gnd = No Voltage (100k ohms Resistance)

12V DC Power Supply Mode:
COM and Gnd = 3.263V
CH1 and Gnd = No Voltage (100k ohms Resistance)
Reset and Gnd = No Voltage (100k ohms Resistance)

If you remove the relay and just short CH1 and COM does the counter increments ?
Yes, the counts will increment.

Additionally,
CH1 and Com = 2.912V

Please advise what to do next?

thank you.

Now we know that the units works by itself.
Lets introduce the relay.

What the voltage when relay is on
Whats the voltage when relay is off

1 Like

Hello Bhaskar,
I checked the voltage across the Relay timer’s contact when the relay in ON and OFF, I don’t get any voltage reading.

I will try to isolate the counter sensor from the panel board, using a simple limit switch to trigger the digital input of the sensor so that I can test if the RESET will still occur.

thank you,

I got it working, the Hangup and Reset issues were solved.

I used software Debounce time = 30
and hardware Debounce module (using optocoupler)

Thank you so much.

2 Likes

for future install will recommend this product

it has optically isolated counter inputs.

2 Likes