- Joined
- Aug 13, 2019
- Messages
- 2,088
- Reaction score
- 2,772
Ok, just to get this out in the open in case it is documented somewhere and I just missed it. I’m more than slightly visually challenged and use a screen reader to read aloud everything. There really isn’t a step by step guide that I could find other than the YouTube. The Neptune diy service video is quite long and maybe I got fatigued and somehow missed it, but hopefully this will save someone else from the frustration of repeating test a fails when calibrating after performing the diy service (or probably anytime the trident shutdown procedure is performed). Scheduled tests, and manual tests work perfectly, as usual. It’s only when calibrating that test a fails occur, repeatedly. Don’t panic and immediately and feverishly take things apart thinking a line got pinched, or something is leaking, or a hose got disconnected or clogged. Especially when you can’t see and are doing everything by feel.
Apparently you need to let the trident run for up to five days to create a baseline before it will allow you to calibrate. Well, it DOES allow you to. It just will go through the motions, waste a bunch of reagent, and an hour later post a test a fail and not calibrate anything. Seems, stupid to me. I mean if they can program it to look for x amount of data samples before it will calibrate, they certainly could add a line or two so that a message pops up if you attempt to calibrate that tells you, sorry there is not enough test data available please allow the unit to run for up to five days and try again.
Anyway, this message is just in case anyone else runs into the issue and searches for it. I do not remember hearing this mentioned in the video or online. I was about to throw the trident at the wall with all the troubleshooting, disassembly, reassembly, flushing, etc. that I was doing all night and this morning.
In case anyone from Neptune (@NeptunePaul) reads this…..please add a couple lines in the next firmware release so that calibration is disabled, or a warning message appears, something to let you know that the unit must run for x amount of time before allowing calibration to be performed. Thank you! Again, could be totally my fault for missing something but I’m pretty sure I didn’t.
Apparently you need to let the trident run for up to five days to create a baseline before it will allow you to calibrate. Well, it DOES allow you to. It just will go through the motions, waste a bunch of reagent, and an hour later post a test a fail and not calibrate anything. Seems, stupid to me. I mean if they can program it to look for x amount of data samples before it will calibrate, they certainly could add a line or two so that a message pops up if you attempt to calibrate that tells you, sorry there is not enough test data available please allow the unit to run for up to five days and try again.
Anyway, this message is just in case anyone else runs into the issue and searches for it. I do not remember hearing this mentioned in the video or online. I was about to throw the trident at the wall with all the troubleshooting, disassembly, reassembly, flushing, etc. that I was doing all night and this morning.
In case anyone from Neptune (@NeptunePaul) reads this…..please add a couple lines in the next firmware release so that calibration is disabled, or a warning message appears, something to let you know that the unit must run for x amount of time before allowing calibration to be performed. Thank you! Again, could be totally my fault for missing something but I’m pretty sure I didn’t.