I think my power sensor is faulty, my spare shows reasonable outputs.
It did give the reading of 260Amps the first time I plugged it in and that might be reasonable for an analog signal of 3,7V.
Then navigator seem fine, but maybe it is damaged now.
There is nowhere in the software where I can get the analog input reading on the current pin?
I can do a reasonable calibration but the Battery monitor in Vehicle setup/ Overview doesn’t move in correlation to the analog input. But I haven’t managed to draw a lot of amps either, but some tenths of an amp…
From the technical details on the Navigator product page, the power sense input pins expect a maximum of 3.3V, so if you know that’s been exceeded then it’s quite possible the corresponding ADC pin has been fried and can’t measure correctly anymore
Not really, at the moment, outside of just setting the battery monitor scale and offset values to 1 and 0 respectively.
Hi guys -
You may be able to read directly from the analog input via lua script - I’ve had success doing this with both a load cell and simple switch… the gcs.send_text will report the raw value scaled to voltage I believe. The 6.6V ADC breakout on the Navigator uses a voltage-divider set of resistors to double the input voltage range, at the expense of resolution…
But if the 3.3V input pin has had 3.7V on it, I agree it is likely damaged
There is some documentation of the successor of this Power sensor, it is supposed to have an inbuilt stop, so it is not possibly to exceed the 3,3V.
I saw how you set up a second power sensor in a different thread Elliot. I will try that when I get connectors for it. Maybe one can re-route the damaged pin to another connector, I will look into that.
I should have a spare Navigator, but they are out of order for the moment.
That script thing, maybe when I get better known with the system. Cool feature though!
I appreciate the work you are doing on this topic.
I look forward to the day a suitable higher-current module becomes available for the BR2 (one that is easy for the rest of us to install and configure).
Do you know what current you reached when this happened?
I’m would like to understand whats the practical max continuous current that this module can safely take.
Yes it’s been very consistent for me, but it does take correct setup/calibration to your robot. It should have come with a little slip of paper with some numbers on it for you to use to get it right for your use
Yeah I used that one in the “other” category of PM unit in QGC, but strangely when I hooked up the ampermeter to main battery the readings are different (use 3 different multimeters to test).
Number from the piece of paper that comes with MAUCH model need to be divided in half (that’s what I found).
So I decided to find a relation how the values changes to find sweet spot. Giving some load about 5-10amps and making it constant, while it running putting the values into calibration current menu its calculated new Amps per volt value which is usually somewhat around half of that value in the paper.
So, the intersting thing after giving differnt load more than 15amps the values goes off by 2-5amps more, and giving more load consequently increasing that offset.
Not sure what seems to be problem either way calibration method in the qgc or my all multimeteres are wrong or the mauch module faulty itself.
Hi @nurjan14 -
There is likely variation in what the correct amps per volt and volts per volt should be for your alternative sensing module. That can happen often if sourced components are not quality controlled! There is a power supply module calibration extension that can be used to help you determine the correct values, and set them. It was used with the BlueBoat, but works just fine with ArduSub! Simply install it from the extensions manager.
