I am trying to configure the transmission delay on the particulate sensor through the new Edge gateway. The wireless device node for that sensor seems to require a manual configuration. I have followed the steps and get the config results with the id_and_delay:true.
However, the delay interval does not ever change. I have tried this several times changing other values including pointing the destination address at the gateway address, but I can’t get the transmission rate to change. Is there a step I am missing? I know I have done this before…
Steps:
Place and Configure Wireless Device Node for sensor type and MAC address
Hi @haljones422 The procedure you are following seems to be correct. Could you please confirm whether you have set the “serial device” and “Serial Device for config” parameters in the “Wireless Device” node to “/dev/ttymxc2 (115200)”? Additionally, could you provide screenshots of your procedure, configurations, and results for further review?
Yes that is the serial device / config I have.
I will try to take screenshots of the process in the morning, but I have limited time.
Should I try and ‘reset’ the sensor - what is that process?
Is there a ‘minimum’ delay - seems to be stuck to 15 minutes - I need to test sub-minute transmissions - like 15 sec to 60 sec. Would that impact anything?
Excellent. I have verified that the NCD library in Node-RED for this specific type 53 is functioning correctly. Please proceed with the factory reset and provide me with the screenshots.
Hi Edwardo, attached are the images from the config. I first did a factory reset and then ran the config. I have set it to 30 seconds and received confirmation, but the sensor is still on a 15 minute delay.
Also, I have an older model of the same sensor. I brought it in and confirmed that I was able to set the delay to 30 seconds - actually works out to about 36 seconds.
Could it be the sensor hardware / firmware?
Hi @haljones422 Thank you for your feedback; It is interesting. Could you please provide me with the firmware version of the sensor? This information is included in the sensor message.
Also, curious what is driving the minimum transmissions of 30 seconds. Is there any way we can modify this? Ideally, I would like to read faster and only send the data to the cloud when it exceeds a threshold. I am using it to control an exhaust fan. I can work with 30 seconds, but not ideal.
The minimum interval is determined by the sensor’s internal sampling process, which takes approximately 8 seconds to complete. We intentionally skip a few samples to ensure consistent and reliable readings. Additionally, the sensor includes a CO2 measurement component that has its own boot time, contributing to the overall data acquisition duration.
That makes sense.
I am running (all) sensors on external power. Is it feasible to keep the system / sensors powered continuously to eliminate the start up time - like a delay time of 0? Just thinking out loud, but in an industrial setting, 30 seconds is a LONG time…
The most important problem is getting this new sensor to recognize the delay configuration. Any new thoughts?
You can use Node-RED to update this new firmware on your NCD sensor using the Enterprise IIoT Gateway. We have a guide that shares a flow and explains how to perform this procedure step-by-step. We highly recommend using Option 1, where you will use the GitHub repo to download the firmware. I will share the guide with you:
It is connected to my local network with internet access. Is there a specific setting on the gateway? Maybe I inadvertently change it???
Can you tell me where to look if there is a setting?
