It is not a parameter, Its a macro defined inside the ardupilot code in AP-temperature library
And how can I change that? I have experience in ardupilot as a user of the software but not a developer or programmer
connect me on discort friek_coder I will help you out.
@Rahul_Yadav @JoaaltCATUAV Did you solve this?
I experienced the same. I’ve used the Custom Firmware Builder to build a firmware that enables these sensors. I’m trying 4 MCP9600 and will need to get around both of the issues mentioned in this thread:
- TEMPn_ADDR always resets to 96 (0x60)
- can’t configure beyond TEMP3_*
Did you have any luck getting past it?
Thanks in advance.
No, I haven’t had time to come back to this although I would like to. Thanks @Rahul_Yadav for the discord proposition, but again, I haven’t had time to come back to the topic. If you have any luck exploring a solution I would very much like to read it
@Fred_Darnell Hey !
This is because if you set address < 96 (0x60) or if you set address > (0x66) then it will reset to default 96 (0x60). You have to adjust this condition in the code if you need adjustment as per your requirement
You are suggesting that it’s limited to 0x60 to 0x66. I see. My second test was with a sensor set to 0x67 then I just assumed something was wrong. I will try the other addresses. Thanks for the note.
I can confirm TEMP1 through TEMP3 are working when given valid I2C addresses. Currently unable to access TEMPn_ greater than 3.