I've got a CR10X logging various data, and it works for a while and then starts giving garbage numbers for everything from external sensors (pulse counters, analog readings, everything) to internal DC voltage.
And then it works fine for a while, and then it doesn't.
The CR10X is running off a 12V lead-acid battery with a float charger, so somewhere around 13.8 volts. It's a 5AH battery, if that matters.
I used to have the NL100 ethernet interface running off a separate 12V supply (from a Power Over Ethernet splitter on the Ethernet feed), and that was right around 12.0 volts.
Just because I couldn't find any other voltage anomalies in the system that might be upsetting the CR10X, I recently moved the NL100 power feed over to the battery system, so they are the same.
So far, it's working OK (or maybe it's just waiting till it's Critical Need detector goes off 8*).
Was that likely the problem? Should the power supplies for the CR10X and the NL100 matter, as long as they are each within spec?
In an ideal world I'd like to get the (140mA?) load of the NL100 off the battery, as when the power fails there's no point to having it powered up, and the CR10X would otherwise run for weeks on the battery.
Thanks for any thoughts!
"Was that likely the problem?"
I don't think so, you might check the signal wires coming from your sensors to see if they could occasionally be over ranging the logger input channels, perhaps something like a 12V wire shorting to a signal wire.
"Should the power supplies for the CR10X and the NL100 matter, as long as they are each within spec?"
No, however it is typically good practice to take the different power supplies and the sensor references to a common ground, so that everything has the same ground reference.
"In an ideal world I'd like to get the (140mA?) load of the NL100 off the battery, as when the power fails there's no point to having it powered up, and the CR10X would otherwise run for weeks on the battery."
I agree