iSpindel got wet last brew and now it won't power on

[rkhanso]

Something is hosed with my iSpindel. When I plug power into it to charge, the red light comes on. It goes out later, I'm assuming after the battery is fully charged.
When I power it on, the blue light on the controller board doesn't light up at all. It doesn't get any power in either position of the power switch (I'm not sure which side is on and which is off).

I bought the iSpindel, didn't build it. Not sure the best way to troubleshoot it.
It looks like the board opposite the D1 Mini is the power/charge controller board, right? Maybe just replacing that is all that's needed?

Or should I just buy another one?

 

[rkhanso]

I took the D1 Mini off the long PCB and had no serial output when connect it to Arduino IDE.
I flashed a new D1 Mini and am getting output, but it won't start up the AP mode. Do I have to solder it onto the board before the AP mode will start?

Output of the D1 mini when not soldered on the board:

rl
09:18:36.131 -> FW 7.2.1
09:18:36.131 -> 2.2.2-dev(38a443e)
09:18:36.131 -> Worker run!
09:18:36.131 -> mounting FS... mounted!
09:18:36.131 -> ERROR: failed to load json config
09:18:36.131 ->
09:18:36.131 -> ERROR config corrupted
09:18:36.131 -> scanning for OW device on pin: 5
09:18:36.131 -> No devices found!
09:18:36.366 -> scanning for OW device on pin: 12
09:18:36.366 -> No devices found!
09:18:36.645 -> scanning for OW device on pin: 0
09:18:36.645 -> No devices found!
09:18:36.878 -> scanning for OW device on pin: 0
09:18:36.878 -> No devices found!
09:18:37.111 -> ERROR: cannot find a OneWire Temperature Sensor!
09:18:37.111 -> Acc Test Connection ERROR!
09:18:37.157 -> offsets not available
09:18:37.157 -> Boot-Mode: Deep-Sleep Wake
09:18:37.157 -> ...........
09:18:38.232 -> ERROR no Wifi credentials
09:18:38.232 ->
09:18:38.232 -> going to Config Mode
09:18:39.256 -> Acc Test Connection ERROR!
09:18:39.256 ->
09:18:39.256 -> --------------- CUT HERE FOR EXCEPTION DECODER ---------------
09:18:39.256 ->
09:18:39.256 -> Exception (28):
09:18:39.256 -> epc1=0x4020fdf9 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
09:18:39.256 ->
09:18:39.256 -> >>>stack>>>
09:18:39.256 ->
09:18:39.256 -> ctx: sys
09:18:39.256 -> sp: 3ffffd30 end: 3fffffb0 offset: 0190
09:18:39.256 -> 3ffffec0:  0030e831 3fff04a0 3fff432c 40207260 
09:18:39.256 -> 3ffffed0:  3ffe9063 3fffff10 00000000 60000600 
09:18:39.256 -> 3ffffee0:  0030e831 3fff04a0 3fff1110 4021060e 
09:18:39.256 -> 3ffffef0:  00000000 3fff04a0 00000000 40206b9f 
09:18:39.302 -> 3fffff00:  4022237f 3fff04a0 3fff0954 40206a64 
09:18:39.302 -> 3fffff10:  00000000 00000000 00000000 402071c0 
09:18:39.302 -> 3fffff20:  4025dbfa 3fff04a0 3fff10f4 402072ec 
09:18:39.302 -> 3fffff30:  00000000 000000f0 00000000 40227896 
09:18:39.302 -> 3fffff40:  40275638 3fff10f4 3fff04a0 40228216 
09:18:39.302 -> 3fffff50:  60000600 3fff10f4 3ffeb3a8 40275645 
09:18:39.302 -> 3fffff60:  4027568a 3fffdab0 00000000 3fffdcb0 
09:18:39.302 -> 3fffff70:  3fff04c0 3fffdab0 00000000 00000004 
09:18:39.302 -> 3fffff80:  40000f49 40000f49 3fffdab0 40000f49 
09:18:39.302 -> 3fffff90:  40000e19 0008fbd1 00000000 00000005 
09:18:39.349 -> 3fffffa0:  00000000 aa55aa55 000000f6 40105631 
09:18:39.349 -> <<<stack<<<
09:18:39.349 ->
09:18:39.349 -> --------------- CUT HERE FOR EXCEPTION DECODER ---------------
09:18:39.349 ->
09:18:39.349 ->  ets Jan  8 2013,rst cause:2, boot mode:(3,6)
09:18:39.349 ->
09:18:39.349 -> load 0x4010f000, len 3460, room 16
09:18:39.349 -> tail 4
09:18:39.349 -> chksum 0xcc
09:18:39.349 -> load 0x3fff20b8, len 40, room 4
09:18:39.349 -> tail 4
09:18:39.349 -> chksum 0xc9
09:18:39.349 -> csum 0xc9
09:18:39.349 -> v0008fbe0
09:18:39.349 -> ~ld
09:18:39.443 ->
09:18:39.443 -> FW 7.2.1
09:18:39.443 -> 2.2.2-dev(38a443e)
09:18:39.443 -> Worker run!
09:18:39.443 -> mounting FS... mounted!
09:18:39.443 -> ERROR: failed to load json config
09:18:39.443 ->
09:18:39.443 -> ERROR config corrupted
09:18:39.443 -> scanning for OW device on pin: 5
09:18:39.443 -> No devices found!
09:18:39.676 -> scanning for OW device on pin: 12
09:18:39.676 -> No devices found!
09:18:39.959 -> scanning for OW device on pin: 0
09:18:39.959 -> No devices found!
09:18:40.193 -> scanning for OW device on pin: 0
09:18:40.193 -> No devices found!
09:18:40.426 -> ERROR: cannot find a OneWire Temperature Sensor!
09:18:40.426 -> Acc Test Connection ERROR!
09:18:40.426 -> offsets not available
09:18:40.473 -> Boot-Mode: Exception
09:18:40.473 -> ...........
09:18:41.547 -> ERROR no Wifi credentials
09:18:41.547 ->
09:18:41.547 -> going to Config Mode
09:18:41.547 -> reboot RFCAL
09:18:41.734 -> rl

 

[rkhanso]

When connecting everything up as before - D1 mini on the long PCB (but using the new D1 Mini), I still don't see the AP Mode/SSID of the iSpindel. I wonder if the DS18B20 or the Gyro sensor is fried since they're the lowest in the tube when beer got in it last time.

I measured the following with the power switch in either position:
With the iSPindel connected at the charging Micro-USB to my computer (battery installed), I measured the input side of the TP4056 charging board. It was at 4.88v DC.
4.17 was measured on the TP4056 at both the battery output and the board output (with red LED lit). But 0V at the D1 mini and the Gyro board.

I removed the battery and powered up the D1 Mini while on the iSpindel PCB. In the serial output, it could not find the DS18B20. I replaced that and nothing changed. This time, I did measure 5V at the gyro board and the Dallas sensor.

The odd thing to me is that it seems like the on/off switch does nothing. The normal output of the charging PCB seems to always be tied to the Battery Charging output and there's always 4v at both the battery charging and PCB output pins no matter what position the switch is in. Shouldn't the switch shut off the output of the charging board so the iSpindel is off? Would this mean that the switch or the charging board is bad? When the iSpindel filled up with beer, it was only at the bottom of the tube, I don't think more than 1/4" deep but that's off memory and suspect.

 

[rkhanso]

I think one of the problems is my on/off switch is bad. If I short the on-side pins of the switch together, I get 4v at the gyro board and Dallas Sensor.
I'm using a new D1 mini with the angular cut corners (not rounded corners) - which I remember seeing in some other thread that it might be a problem. But it's all that I have for now.

The blue LED flashes a few times and I see a SSID show up on my phone -- FaryLink_DAFED8. But I get a Denied Access error when trying to connect with my phone. Then a little while later, the SSID is not found.

 

[rkhanso]

▒bl`▒n▒`
        FW 7.2.1
2.2.2-dev(38a443e)
Worker run!
mounting FS... mounted!
ERROR: failed to load json config

ERROR config corrupted
scanning for OW device on pin: 5
No devices found!
scanning for OW device on pin: 12
No devices found!
scanning for OW device on pin: 0
No devices found!
scanning for OW device on pin: 0
No devices found!
ERROR: cannot find a OneWire Temperature Sensor!
offsets not available
Boot-Mode: Deep-Sleep Wake
...........
           ERROR no Wifi credentials

going to Config Mode

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Exception (28):
epc1=0x4020fdf9 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

>>>stack>>>

ctx: sys
sp: 3ffffd30 end: 3fffffb0 offset: 0190
3ffffec0:  00310014 3fff04a0 3fff41cc 40207260
3ffffed0:  3ffe9063 3fffff10 00000000 60000600
3ffffee0:  00310014 3fff04a0 3fff1110 4021060e
3ffffef0:  9e224130 7f93604c 3fff1134 40211ac4
3fffff00:  fffff3ce 3fff04a0 3fff0954 40206a64
3fffff10:  00000000 405395a6 00000000 40206c48
3fffff20:  3fff04a0 3fff04a0 3fff10f4 402072ec
3fffff30:  0030bf24 3fff04a0 3fff0478 40227896
3fffff40:  40275638 3fff10f4 3fff04a0 40228216
3fffff50:  60000600 3fff10f4 3fff04a0 40275645
3fffff60:  4027568a 3fffdab0 00000000 3fffdcb0
3fffff70:  3fff04b8 3fffdab0 00000000 00000004
3fffff80:  40000f49 40000f49 3fffdab0 40000f49
3fffff90:  40000e19 0008fbd1 00000000 00000005
3fffffa0:  00000000 aa55aa55 000000f6 40105631
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 3460, room 16
tail 4
chksum 0xcc
load 0x3fff20b8, len 40, room 4
tail 4
chksum 0xc9
csum 0xc9
v0008fbe0
~ld

FW 7.2.1
2.2.2-dev(38a443e)
Worker run!
mounting FS... mounted!
ERROR: failed to load json config

ERROR config corrupted
scanning for OW device on pin: 5
No devices found!
scanning for OW device on pin: 12
No devices found!
scanning for OW device on pin: 0
No devices found!
scanning for OW device on pin: 0
No devices found!
ERROR: cannot find a OneWire Temperature Sensor!
offsets not available
Boot-Mode: Exception
...........
           ERROR no Wifi credentials

going to Config Mode
reboot RFCAL
rll▒r$▒n

It looks like a lot of people have had bad switches in the past. I've just shorted the on side of mine and will remove the battery when I'm not using the device.

I am still getting the FaryLink SSID temporarily when the ESP boots up. I connected the USB and monitored the serial output and it's not detecting a Dallas Sensor. Could this be the reason it's not broadcasting the iSpindel SSID as it normally should?

The serial output:

 

[DuncB]

Hi
I've been there with a drowned ispindel, this thread has a lot of info and best for ispindel questions.

https://www.homebrewtalk.com/threads/ispindle-diy-electronic-hydrometer.598187/
This new software works great and doesn't need the dsb1820 sensor. VERY good support as well with this software.
https://www.homebrewtalk.com/threads/replacement-firmware-for-ispindel-gravitymon.698058/
I sank an ispindel in one brew. The issue I had was that it destroyed the battery.

I gave it all a good wash in warm water then air dried it with a hairdryer and then isopropyl alchohol and then a few days in box with dessicant.

Switches have been an issue for some people. Some photos would help to see the model of ispindel you are using.

My ispindel after a sinking

https://www.homebrewtalk.com/threads/ispindle-diy-electronic-hydrometer.598187/post-9108516

 

[rkhanso]

I did get it working with the help of the GravityMon software. I could see that the gyro board was working but I didn't get the dallas sensor data showing up. Tracing the board, noticed there was an open in somewhere, so I added a jumper wire. It's working now, but the battery was dead. I'm charging it and will see how long it can run the iSpindel. I wonder if my charging board might be bad.

I did go back to the original iSpindel firmware because it's what I'm used to. But I'll read up on Gravitymon and see if I can understand it and figure it out.

Thanks - your ideas helped me solve the problem.

 

[DuncB]

I did get it working with the help of the GravityMon software. I could see that the gyro board was working but I didn't get the dallas sensor data showing up. Tracing the board, noticed there was an open in somewhere, so I added a jumper wire. It's working now, but the battery was dead. I'm charging it and will see how long it can run the iSpindel. I wonder if my charging board might be bad.

I did go back to the original iSpindel firmware because it's what I'm used to. But I'll read up on Gravitymon and see if I can understand it and figure it out.

Thanks - your ideas helped me solve the problem.

Could be the battery failed rather than the charger.
Each ispindel I've built I've removed a bit to the left of programming usb connection on the d1 mini. With the usb towards/closest to you. This makes it safer when charging the ispindel.
This does need bridging if you repurpose the d1 for other roles such as a WiFi repeater if you direct power rather than run repeater off a battery.