We have an elusive problem on our FabLab with Unisolder where the wrong tip is detected, and this resulted in a burned tip. Troubleshooting has not been successfull. We would like to implement a software workaround, and I open this issue for advice.
I was thinking to add a parameter to disable the auto-detection in IronIdentify() function, with a logic as follows:
1) if a new tip is detected, different from the last model saved in EEPROM
2) check if the auto-detect parameter is enabled, if YES -> keep the existing logic
3) if NO, set a global variable to flash on the screen the "auto-detect disabled" message and keep old tip ID
Other changes required:
Edit pars / eprom accordingly
Add saving in EPROM at poweroff of the last valid tip
Potential design issue:
Behaviour in case of this sequence : old tip -> 0x1919 -> new tip . Should we keep the old tip ? Allow autodetect if tip has been disconnected? Maybe we will have spurious changes anyways.
Alternative design:
add a parameter to allow setup a fixed IronID and bypass detection ?
Thanks for your feedback about the kind of solution to this problem would you be open to merge as pull request.
We have an elusive problem on our FabLab with Unisolder where the wrong tip is detected, and this resulted in a burned tip. Troubleshooting has not been successfull. We would like to implement a software workaround, and I open this issue for advice.
I was thinking to add a parameter to disable the auto-detection in IronIdentify() function, with a logic as follows:
1) if a new tip is detected, different from the last model saved in EEPROM 2) check if the auto-detect parameter is enabled, if YES -> keep the existing logic 3) if NO, set a global variable to flash on the screen the "auto-detect disabled" message and keep old tip ID
Other changes required:
Potential design issue:
Alternative design:
Thanks for your feedback about the kind of solution to this problem would you be open to merge as pull request.