iSpindle - DIY Electronic Hydrometer

Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum

Help Support Homebrew Talk - Beer, Wine, Mead, & Cider Brewing Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
I'm having an issue getting my iSpindel to run correctly with the battery installed. When I switch it on, it pings to Ubidots and goes to sleep, but when it wakes up it just stops and I get a solid blue LED on the Wemos. It works fine with the battery removed and the WEMOs USB plugged in. During my intial build, I installed the battery holder in backwards cause I'm a dingus and I let out some magic smoke. I've since replaced the WEMOS and TP4056, but I'm afraid something else is causing it to have this issue. Could I need to replace the BAT43 diode?

Here is my log:
¦¦a¦q¦¦o¦¦2002ms, result 3
IP: 192.168.0.102

calling Ubidots
{"tilt":35.523,"temperature":76.4375,"battery":4.702816,"gravity":5.341125,"interval":10,"RSSI":-48}
Sender: Ubidots posting
POST /api/v1.6/devices/iSpindel01?token=BBFF-ZLwJEUVuJ4dXv3hUPNyiOIUvgSwziP HTTP/1.1
Host: things.ubidots.com
User-Agent: ESP8266
Connection: close
Content-Type: application/json
Content-Length: 100

HTTP/1.1 200 OK
Server: nginx
Date: Thu, 05 Nov 2020 04:19:10 GMT
Content-Type: application/json
Transfer-Encoding: chunked
Connection: close
Allow: GET, POST, HEAD, OPTIONS
Vary: Origin, Cookie

d1
{"battery": [{"status_code": 201}], "gravity": [{"status_code": 201}], "interval": [{"status_code": 201}], "rssi": [{"status_code": 201}], "temperature": [{"status_code": 201}], "tilt": [{"status_code": 201}]}
0


Final-sleep: 10s; RT: 3847
s$l¦¦|¦d¦|
¦

b<¦¦¦{¦c¦
b¦¦og¦lno¦¦¦
bx¦¦lrd;lp¦g¦
¦l¦¦
co¦<¦¦s¦c¦¦no¦$¦¦l`¦$`'{¦¦¦g
¦l{¦¦o¦l¦¦
¦A¦¦l`¦o¦
FW 6.3.1
2.2.2-dev(38a443e)
Worker run!
mounting FS... mounted!
reading config file
parsed config:
{"Name":"iSpindel01","Token":"BBFF-ZLwJEUVuJ4dXv3hUPNyiOIUvgSwziP","Sleep":10,"Server":"log.brewfather.net","API":0,"Port":80,"Channel":0,"URI":"","DB":"ispindel","Username":"","Password":"","Job":"ispindel","Instance":"000","Vfact":191.8,"TS":1,"OWpin":12,"POLY":"-0.00031*tilt^2+0.557*tilt-14.054","SSID":"","PSK":"","Offset":[0,0,0,0,0,0]}
offsets not available
Boot-Mode: Deep-Sleep Wake

woken from deepsleep, normal mode


Any thoughts on why it can run succesfully on USB power with the battery removed, but not on the battery alone?
 
I understand the whole faraday cage, but people use these with conicals... I guess the conicals have more gaskets for the signal to get out?

I could use a 2" sight glass in between the keg and the tri clamp fitting. That would be easier to sanitize than some coax cable. However that would make it too tall to fit in my fermentation chamber.
Maybe you can install a wifi extender close to your keg?

I have the ispindel in a refrigarator in my shed(but not in a steel keg btw) which is about 10m from the house. I installed a wifi extender in the shed to connect the ispindel with. The extender connects to the router in the house.

The wifi signal of the ispindel is not so powerful as of a wifi extender, so instead of trying to connect directly to the router in the house I used an extender, works great in my setup.
 
Understandably, I suppose there's not too many other dingus's like me that have then successfully remedied any backward installed battery holder... I'll keep fiddling and report back if anything gets her back in proper working order.
 
I've just started working with my iSpindle today, and can't seem to get it to talk to the web. I can see the portal in configuration mode. I have tried to connect it to ubidots and to brewspy to no avail. I know the tokens have been typed in correctly, and all the boxes filled in per the examples. Any thoughts?
 
I've just started working with my iSpindle today, and can't seem to get it to talk to the web. I can see the portal in configuration mode. I have tried to connect it to ubidots and to brewspy to no avail. I know the tokens have been typed in correctly, and all the boxes filled in per the examples. Any thoughts?
Does it connect to your router?
 
I'm not seeing the MAC address when I check for connected devices.

That is the main bugbear with the iSpindel, the difficulty in knowing whether its reports are getting through.

My iSpindel works fine, but I never see its MAC show up as connected in my routers list. The big problem is that the iSpindel connects so briefly, it doesn't get logged by the router. In addition, because it is such a brief connection, you cannot ping the iSpindel.

All you can do, is when initially testing it, set it for frequent reports, 60 seconds and see how many of the reports get through or fail, as a way to judge. Some software like Brewspy and Ubidots, give a value for signal strength.

Begin your tests with the iSpindel close to the router, until you have made sure it is working with the software.
 
I assume that you filled in the wifi SSID and it's password correctly in the configuration of the iSpindel?
Maybe hook it up to a serial monitor where you can see what the thing is actually doing as described here: universam1/iSpindel
 
It appears that the builder of my iSpindel installed the D1 mini flush to the board, so I can't access the USB port. I'm going to do some surgery on a USB cord to see if I can get a connection. The alternative is to remove the D1 mini, and reinstall it on a slight angle to expose more of the USB port. I can get a D1 mini from Aliexpres that has the USB port on the top, but then I'd have to flash the firmware and all that nonsense.
 
Flash trouble. The Wemos is driving me crazy. Please save me!
Back story - I built an ispindel with v1 wemos D1mini and all the familiar bits. It failed to show up when I plugged it into my PC. Assumed dead wemos (which could be my fault during build or it was a DOA) so ordered a new wemos. Have now received a v3.0.0 and attempting to flash before I commit to build.

Current problem - When flashing - progress bar goes to 100%, wemos does the flickering LED thing then resets. I press reset a few times. LED flashes about 5 times then goes dark, so assume the wemos is NOT in config mode and some code is now running. But then no "ispindel" wifi network appears on my PC or phone. Although occasional a network appears called "ESP-0Cxxxx" [hex number redacted by me] If I try to connect to it, it fails.

I read somewhere that in operation the wemos is only 'on' for a short time then sleeps - but nothing about that in all the various guides for flashing your wemos and then connecting to ubidots, so I figure that isn't the problem.

I have tried NodeMCU ESP8266Flasher and Tazmotizer - same result.
I have tried firmware 6.3.1 (current) and others at random 6.3.0 and 6.4.1 (pre-release) - same result

PuTTY gives totally random output - this is the entire log I get when I press reset on the wemos and wait for a few minutes;
It's different each time I press reset and create a log.
--- PuTTY start ----
V▒j
\▒j
▒!Vpd▒2▒=▒@▒'▒▒▒▒▒▒;▒
▒▒`ȷ;▒'▒▒D▒#▒▒▒%?▒▒▒R▒ L^▒rp"▒H<▒▒~▒< ▒▒▒▒▒▒*!▒▒Ϫ▒
---- PuTTY end -----

So am I missing a putty setting?

1609168986536.png


To debug I went to learn about wemos and installed Arundino and board libraries etc from a good resource here Wemos D1 Mini Setup | Average Maker I got the "blink" sketch to work and also was able to edit the sketch (changed off/on durations) and upload - all good, so I think the wemos is OK. And the ESP-0Cxxxx wifi shows up. Remembering that this is a bare board out of the bag.

I have done loads of research on this forum and on other sites and cant find an answer.
So I joined this forum in the hope that y'all can help me please.
 
Current problem - When flashing - progress bar goes to 100%, wemos does the flickering LED thing then resets. I press reset a few times. LED flashes about 5 times then goes dark, so assume the wemos is NOT in config mode and some code is now running. But then no "ispindel" wifi network appears on my PC or phone. Although occasional a network appears called "ESP-0Cxxxx" [hex number redacted by me] If I try to connect to it, it fails.
You need to build the iSpindel completely in order to make it work. You can flash it with the firmware first but it doesn't function until you build the whole thing.
 
@nujjer As @BreeBrew says the iSpindel won't complete the boot process until it is fully built and found all the hardware. Assuming you have fully built it you can see what's happening on the serial port, which should be set to a baud rate of 115200. Looks like you just missed off the trailing zero.


Chris
 
Last edited:
You need to build the iSpindel completely in order to make it work. You can flash it with the firmware first but it doesn't function until you build the whole thing.

Aw man!
Huge thanks @BreeBrew and @ChrisThomas - I guess that was an obvious step! I have soldered the wemos headers and plugged it into the board that I already made - it works! OMG I wasted sooooo much time 🙄
Another learning point emerged (which also means my v1 D1 might not be duff) I was able to flash the bare wemos, but once I had removed the infamous diode the PC would not recognise it when plugged into the usb. Once I had assembled everything, if I then powered the wemos with the battery it showed up as COM4 and worked fine. It is currently telling Ubidots the temperature of my kitchen.

Thanks again - standby for more stupid questions. :)
 
There is only news (Master Oogway). I may have fried my V3 wemos or gyro. All working ok on the bench pre calibration. I assembled into PET container which required matrix board filing (I have made exactly per iSpindel.de) and adding a plastic assembly to hold the battery compartment. No electronics work, only mechanical assembly. When I turned on, the LED stays solid on. Reset has no effect. After a few mins the wemos/gyro assembly was hot to the touch. I let it cool down. turned on. LED stays solid. To test I plugged USB into PC, COM4 came up but NodeMCU couldn't flash.

There isn't anything in the wemos spec webpages about solid LED. Is it dead?
I can only guess some swarf entered somewhere, but I have looked all over with a magnifying glass and all pins that should be isolated according to the circuit diagram are fine.
Per my earlier Q - I found that I could indeed flash the V1 Wemos. And configure it. In config INFO mode it shows temp every second (gyro not attached, its soldered to the v3 version). But then when I save the led comes on solid and nothing shows up in ubidots.

I realise that this might be difficult to debug when you cant see my device, but hoping that the solid LED is a symptom with a known cause.

Thanks for reading this far.
Neal

BTW I did educate myself why removing the diode stops the wemos working if there is no battery connected - it is the link from the USB +5v to the wemos VCC https://www.wemos.cc/en/latest/_static/files/sch_d1_mini_v3.0.0.pdf
 
I purchased an iSpindle on eBay and I am having loads of problems with it. At first I successfully connected it to Brewfather, but it would only log once when I turn the device on, then never log again until I reset the pins. I read somewhere that it may be an issue with my modem, so I tried connecting it to the wifi at work and it still only logs once when the pins are reset. Then I tried connecting it to Ubidots, but the device will not connect even though I entered all the information correctly in the configuration page. Then I decided to try Brewfather again, but this time I cannot connect the device to Brewfather at all. Does anyone have any idea what is going on? Any insight will be much appreciated!
 
Does anyone have a synthetic formula for battery percentage? On Ubidots, the standard battery widget shows voltage. My battery max is 4.5v and I believe 0% is 2.7v.

I've been using the standard battery widget as some form of indication but a variable that shows percentage would be convenient.
 
Does anyone have a synthetic formula for battery percentage? On Ubidots, the standard battery widget shows voltage. My battery max is 4.5v and I believe 0% is 2.7v.

I've been using the standard battery widget as some form of indication but a variable that shows percentage would be convenient.
For that you need to look at the battery datasheet, not all batterys deplet with the same voltage drop.
https://batteryuniversity.com/_img/content/18650chargeDischarge-powercell-web.jpgYou can see the drop is more or less linear, but you need to know the ebowl point.
For iSpindle the discharg is even lower than the 0.2C ploted.
 
Last edited:
For that you need to look at the battery datasheet, not all batterys deplet with the same voltage drop.
https://batteryuniversity.com/_img/content/18650chargeDischarge-powercell-web.jpgYou can see the drop is more or less linear, but you need to know the ebowl point.
For iSpindle the discharg is even lower than the 0.2C ploted.

Thanks for the response. The link says "access denied."

Once I extract my battery's data, how would I go about to determine the formula?
 
Last edited:
@nujjer What do you see on the serial port when you reset?

@ChrisThomas a bit of a mish-mash. Some looks OK (not that I would know) but lots of "Acc Test Connection ERROR!"
The main chip is mildly warm to the touch (not hot) but certainly consuming some energy. Blue LED is faintly on.

---- PuTTY start -------
FW 6.3.1
2.2.2-dev(38a443e)
Worker run!
mounting FS... mounted!
reading config file
parsed config:
{"Name":"iSpindel_Winx1","Token":"BBFF-bTqT37LNenrjtxund0gp2u8YNhFgm7","Sleep":30,"Server":"","API":0,"Port":80,"Channel":0,"URI":"","DB":"ispindel","Username":"","Password":"","Job":"ispindel","Instance":"000","Vfact":191.8,"TS":0,"OWpin":12,"POLY":"-0.00031*tilt^2+0.557*tilt-14.054","SSID":"[redacted]","PSK":"[redacted]","Offset":[0,0,0,0,0,0]}
Acc Test Connection ERROR!
offsets not available
Boot-Mode: External System
power-cycle or reset detected, config mode

going to Config Mode
Acc Test Connection ERROR!
Acc Test Connection ERROR!
*WM: Scan done
*WM: Adding parameter
*WM: name
*WM: Adding parameter
*WM: sleep
*WM: Adding parameter
*WM: vfact
*WM: Adding parameter
*WM:
*WM: Adding parameter
*WM:
*WM: Adding parameter
*WM: tempscale
*WM: Adding parameter
*WM:
*WM: Adding parameter
*WM:
*WM: Adding parameter
*WM: selAPI
*WM: Adding parameter
*WM: token
*WM: Adding parameter
*WM: server
*WM: Adding parameter
*WM: port
*WM: Adding parameter
*WM: channel
*WM: Adding parameter
*WM: uri
*WM: Adding parameter
*WM: db
*WM: Adding parameter
*WM: username
*WM: Adding parameter
*WM: password
*WM: Adding parameter
*WM: job
*WM: Adding parameter
*WM: instance
*WM: Adding parameter
*WM:
*WM: Adding parameter
*WM: POLYN
started Portal
*WM: SET AP
*WM:
*WM: Configuring access point...
*WM: iSpindel
*WM: AP IP address:
*WM: 192.168.4.1
*WM: HTTP server started
Acc Test Connection ERROR!
Acc Test Connection ERROR!
.... etc this then carries on.....
----------PuTTY end --------------
 
@nujjer Can you connect to the iSPindel in AP mode? That is, can you see and connect to a network called iSpindel, connect to that network and then open a web broswer?
 
Hi nujjer, "Acc" means accelerometer which is a gyroscope error. How do your solders look on the GY-521? Can you replace the GY-521?

First - thanks Joey Joe Joe jr, your ispindel webpages are excellent.
Second - awful. My 25W 35 yr old soldering iron is just about shot and fluctuates wildly in temperature. The solder quality is rubbish and I probably killed something.
I got a new soldering iron. I'll order new parts and have another go.
 
Hey guys. Anyway we can start a WhiteList / BlackList of suppliers (mainly Ali Express ones) who carry bad/good batches of D1, Gyros etc ? I just tested 32 D1 Minis for the DeepSleep "bug", 28 out of 32 were bad ... I would hate for this to happen to someone else ...
 
Hey guys. Anyway we can start a WhiteList / BlackList of suppliers (mainly Ali Express ones) who carry bad/good batches of D1, Gyros etc ? I just tested 32 D1 Minis for the DeepSleep "bug", 28 out of 32 were bad ... I would hate for this to happen to someone else ...

I only buy the 3.0.0 boards now and I'm going to start building my own going forward or making boards that use the esp-12s, the amount that I have also got that have issues is shocking.
 
Hey guys. Anyway we can start a WhiteList / BlackList of suppliers (mainly Ali Express ones) who carry bad/good batches of D1, Gyros etc ? I just tested 32 D1 Minis for the DeepSleep "bug", 28 out of 32 were bad ... I would hate for this to happen to someone else ...

I recently bought 20 D1s and none of them would even start in AP mode. My last batch I only had 1 bad out of 20.
 
Today I :
- Test all my Gyros
- Flash the D1 with a simple sketch that test for deep sleep
- Mount my iSpindel fully and make sure it works

That's a pain :(
 
yeah, and the Gyro (MPU-6050's) are hit and miss too, usually 50-60% bad. That's why I've gone to the SMT ispindel boards. I just need to worry about the d1 and TP4056, which I'm currently in the process of building both and having made myself.
 
I've sourced several D1 mini clones from China for various projects over the last few years and with mixed results. I agree with @gromitdj , all my recent D1 mini have come from the Lolin store, V3.0.0s and V3.1.0s and since then I've not had a duff one.

For other modules I haven't yet found an Aliexpress reliable source. I have found an eBay shop that I find very reliable and a quick shipper, ModuleMe.

Chris
 
Last edited:
I'm finding that the majority of the D1 boards I am buying are fine - but the gyros are awful. Just tested a batch of 20, and half of them give either zero tilt, or the calibration on the ispindel fails and the blue light stays on until I turn it off.
 
for the Gyro, I have no test method apart from mounting it on an iSpindel :/

For the D1, I agree, real Lolins are a good way to go. What I found out is that there are more issues with "all in one" (ESP12X type) than with "proper PCB"
 
My recommendation is to only get the D1's from the Lolin store on Aliexpress.

Lolin D1 Mini V3.1.0
Yes those are the real deal, I build 20 iSpindels with those and they all work. See also LOLIN D1 mini — WEMOS documentation

What I notices with the gyro boards is that the ones on the left with the orangy/yellowy block are working all fine, the other ones with the black block on the right 3 out of 10 worked from my last order.
1610718332302.png
 
Last edited:
I have a couple of iSpindels, that after running the calibrate function in the maintenance menu page, they now read negative gravity. Anyone know how to fix this?

Thanks
 
I have a couple of iSpindels, that after running the calibrate function in the maintenance menu page, they now read negative gravity. Anyone know how to fix this?

Thanks
If you used the calibrate function, then you need to run a "new" calibration (water, water with sugar, water with more sugar etc) to make sure your polynomial approximation function is still coherent with your iSpindel.
Once you run a calibrate function, you should check if it's at 25+/-1 degrees in Water.
 
Back
Top