Hello, I have a PR55-44 RTD temperature sensor. I am using a third party 100ohm 3 wire probe and am getting extremely inaccurate data reporting from the sensor. No matter how I adjust the 3 ends of the probe to get normal values, I repeatedly get two values output, a 0 value and then a 46,070.55 value. When using the provided trial probe, I was getting accurate data most of the time, but would frequently get spikes up past 46,000, which we obviously can confirm were not accurate readings. I have attached photos of my sensor.
I have attempted to factory reset the device, have pulled the batteries, and have swapped the exisiting batteries with brand new ones. Still, getting very inaccurate data.
I have removed the third party probe and have attached the originally provided probe.
I get more accurate data when I swap to this probe, but I still get spikes over 40,000 almost every 10 minutes on the minute. I have made sure the connection is secure, but still getting odd data. Could this possibly be an issue with the sensor itself? We are exploring using these as glycol based monitoring probes for refrigerators but want to make sure they can be a good solution.
Here is the entire data dump from the debug node. One thing to note is the battery % shows is a very odd value, even when using brand new lithium pro-cell batteries.
the packet you shared above the the FLY packet not data packet. is this the packet you are seeing with high temp data?
FLY packet – Once an hour the sensor sends FLY message to the gateway and stays on for few sec, during this time gateway can send any commands to configure the sensor like sampling interval.
@jacob@Eduardo_Mtz the RTD supports FLY can you enable this in node red as well.
This is the data dump from directly connecting a debug node to the gateway node in node-red. The high temperature data was in this data dump as well but just did not copy over. If I connect a debug node to the wireless device node, I still get the high temperature data, but I don’t receive additional data with it like you mentioned.
Can you let me know what version of our library you’re running?
This can be found in the Palette Manager. Click the menu button in the top right of node-red (three horizontal lines) > Manage palette > Nodes tab > take a screenshot of this pane and send it.
If there’s an update pending could you run the update and try again? You’ll need to restart node-red for the update to take effect. The best way is to add an inject node connected to an exec node. The exec node will need to use the command: pm2 restart all
Then deploy the flow and hit the button next to the inject node.
Hello, here is the screenshot below, it does appear I have the option to update to 1.6.24 for the ncd-red-wireless nodes. I’ll go ahead and perform the update and then restart the gateway.
Hi, after updating, I’m not seeing the device in FLY mode anymore, it appears to consistently be in run mode, but instead of getting erroneous values, I am getting a 0 reading consistently. I’ve adjusted the probe(s) and power cycled the device but still cannot obtain a normal reading.
Hi yes, I get a 0 temperature reading whether I use the provided probe or any one of the three pt100 three wire probes we purchased separately. Here is the last data dump of the sensor.
