-
Notifications
You must be signed in to change notification settings - Fork 18
Description
I have similar problem to newaetech/ChipSHOUTER-python#8, but not after 5s.. after 15-60 min of run with or without triggersafe used
ChipSHOUTER xformer: 51, MOSFET: 44, diode: 35 - temperature
ChipSHOUTER voltage measured: 457, set: 470
ChipSHOUTER absent time after trigger: 1
ChipSHOUTER glitched 73 times, runs: 00:17:25
Faults current: [], latched: ['fault_temp_sensor'] ['fault_temp_sensor']
Also after that when you read temp values they are all -1 or 65535
Only device reset clear them
ChipSHOUTER xformer: 65535, MOSFET: 65535, diode: 65535 - temperature
This is a bug I think. This values should never be overshoot like that. When reading this value it goes in fault state. It is also possible to Arm with this failure values. If trigger_safe is not set you can still arm.. but only reset of device clear them
Then when you enable trigger_safe and ARM with xformer: 65535, MOSFET: 65535, diode: 65535 ChipSHOUTER goes to Fault state. This should prove that this is software bug
Of course you can see this -1 values in normal UART menu, so it is not python API problem