I have some machine uptime counters that are working but have had some issues with the configuration.
I originally had setup a shift time, but then needed to revert it. I think I completed the task through the device update. I did a factory reset on the device
For a single device, it is sending data but the “report_type” is showing as either ‘Regular’ or ‘Shift’. What does this mean and should it only have 1 value?
The sensor is also not sending every 2 seconds but instea it seems like the data is sending every 1000 or on the hour.
Hi @danempiric I recommend updating the firmware on your Machine Uptime Monitoring Sensor over the air (OTA) using Node-RED.
To do this, please download and import the attached flow into your Node-RED workspace. ncd-firmware-update-t108.json (2.8 KB)
This flow is already pre-configured with your sensor’s MAC address and the necessary firmware link. Once imported, simply click the Deploy button and follow the on-screen flow instructions.
I’ve also included an article for your reference that details the OTA process. Refer to section 12 Enable Flow:
Try this and share your results,
Thank you,
Eduardo M.
Check Version: Go to the Node-RED main menu, click Manage palette, and locate the @ncd-io/node-red-enterprise-sensors library to see your current version.
Update & Restart: If an update is available, click the Update button. You will then need to restart Node-RED. Please import the attached restart flow into your workspace, click Deploy, and enable the flow to restart Node-RED. Finally, refresh the webpage.
When you say reset, do you just mean to press the ‘reset’ button or to do a hard reset i.e. press reset and then hold config for 20s , then press reset again?
What version of the pallet/ machine uptime firmware should it be on? 1.4.5 ncd library is okay.
When you say reset, do you just mean to press the ‘reset’ button or to do a hard reset i.e. press reset and then hold config for 20s , then press reset again? No, just Reset the sensor (Press and release the RESET button), or you can wait for next FLY transmission, after enable the firmware flow.
I’m not getting any messages from the gateway through the MQTT. When I was troublshooting on-site, I noticed that the MQTT out to the broker would disconnect.
Is there something that if there are too many messages that the mqtt out would freeze and not be able to publish anymore?
I am using the same credentials as previous and the gateway says it’s connected to the internet.
I don’t think we’re hitting the limits of the MQTT broker. I have an ‘is alive’ message that appears to be working. But the devices are sending their signal.
Is there a procedure to do a full reboot of the the gateway?
I have an export of the xml to re-upload but it won’t let me.
Do I just do that though the webportal for the gateway on the factory reset?
I was able to get the devices to start reading again. But I noticed that it’s not picking up all of the signals. I should be running 100 units/minute but some are getting skipped. It appears that the debounce time doesn’t update will from 50ms to 10ms. Would this be part of the issue? I have tried to update the configuration for the debounce but it doesn’t seem to want to stick.
Ideally I want to see each time it counts. This is an example of the database, for our signals, You can see that it jumps from 1765 to 1869 without any data in between.
For your specific application, I would recommend two changes: Increase the Data Transmission Interval and enable the Push Notification setting. Enabling Push Notification ensures that the sensor will immediately transmit data upon detecting a signal change on the specified input(s). When this occurs, the report_type property will be set to 'Interrupt'.
Could you please carefully check if the sensor data matches the corresponding values in your database? For example, at the timestamp ‘13:27:28’, the value recorded is 1763, which then increases to 1764. However, the subsequent entry shows 1763 again. This fluctuation (a decrease in an accumulating counter) should not be possible.
Note: It is important to consider that the sensor will transmit a message every time it detects a change in the input signal state (i.e., transitioning from low to high, or from high to low). In addition, in case you only want to manage or transmit data to your database when the input changes from low to high, you can use a Switch node in Node-RED.
You would need to:
1. Evaluate the corresponding input property within the Switch node. 2. Configure the Switch to only allow the message to flow when the input property is equal to 1 (indicating a high/ON state).
The Input property within the data message contains the current logical status of the corresponding input (High/Low). You can check this on the User Manual.
Let me ask you, what type of input is your sensor using to count?
I am trying to measure bottles going through a conveyor. Each bottle is appox 2 inches in diameter and targeting up to 100 bottles per minute.
The note about the change in input state, I set it to rising edge trigger. Does that mean that the value should actually be double counting? Would that counteract that?
I was able to get the report_type to interrupt. Which field is the transmission interval? The ‘node id and delay field’? I have that set to 1.
No, the sensor will count only on rising edge events. However, it will still transmit data upon each status change (both rising and falling edges).
The setting is Data transmission Interval. This interval operates independently of any interrupt-driven (Push Notifications or Resets) and report_type will be 'Regular'.
Are you currently using a photosensor to detect the bottles?
For your application, I would recommend disabling Push Notifications, as enabling it will cause the sensor to transmit data approximately every second or less.
The sensor can transmit data reliably based on a scheduled time interval (Data Transmission Interval); therefore, you can configure it to transmit every minute. With this setting, the sensor will count the bottles and transmit the accumulated counter value every minute, which should be approximately 100+ units each transmission.
Could you please try disable push notification, and setting the Data transmission Interval to 1 minute and the Input Debounce Time to 25? and share your results.
