Wifi boat data monitor - what's left to measure!

  • Thread starter Thread starter GHA
  • Start date Start date
Thanks, looks like it should do the trick :encouragement:

Was that coming off the 'W' terminal? Heard that should work.

Whatever is triggering the rev counter on the dash, I just used a crocodile clip there to test it, it worked straight away, so happy. Considering there's only + - and this going to the counter, it's W if you call it so :p

V
 
Hi GHA

Any simple concise guides to using easyeda with jlcpcb assembly?

Specifically how do i find / choose their supported parts?
 
Hi GHA

Any simple concise guides to using easyeda with jlcpcb assembly?

Specifically how do i find / choose their supported parts?

The easyeda library doesn't seem to link very well so I search on this page >
https://jlcpcb.com/client/index.html#/parts
G1aWLi9.png


Then search in the easeda library with the LCSC Part # >

htzohmn.png


To order a board with surface mounted components to be assambled you need to export a BOM file, Gerber file & pick and place file from easyeda then import these to jlcpcb. Tutorials online, quite easy. Then hit order and wait :)
 
Being controversial I’d like to suggest the most important thing of all for us yachtie owners; the heart rate and pressure of the prospective purchaser…

This will enable us (when we’re selling) to see what’s going on in the head of the person who is in the act of making an offer for our pride and joy.

1 - A bit raised = potential offer.
2 - Significantly higher = cheeky low offer is imminent.
3 - No change = don’t give a stuff about the boat.

This information will need to be presented in real time as a moving chart inside a wearable tech display (Google glass?) to be useful.
 
Being controversial I’d like to suggest the most important thing of all for us yachtie owners; the heart rate and pressure of the prospective purchaser…

This will enable us (when we’re selling) to see what’s going on in the head of the person who is in the act of making an offer for our pride and joy.

1 - A bit raised = potential offer.
2 - Significantly higher = cheeky low offer is imminent.
3 - No change = don’t give a stuff about the boat.

This information will need to be presented in real time as a moving chart inside a wearable tech display (Google glass?) to be useful.

GHA is your man for that, he's into wireless kit.
I'd be only able to help if a prospective buyer was happy dragging about the boat a loop of cables to my teensy - highly unlikely :rolleyes:
 
GHA is your man for that, he's into wireless kit.
I'd be only able to help if a prospective buyer was happy dragging about the boat a loop of cables to my teensy - highly unlikely :rolleyes:

Get him to stick an ESP32 & BME280 humidity/pressure/temperature sensor in his pocket - maybe hot and sweaty would show up :)
Amazing what you can get for under 3 quid :)

fIAqRk5.png
 
Maybe the fridge online is going a bit far.... ;)

dp8Rel5.png

Does that allow you to trick the fridge compressor to come on with the S8050?

If you added a voltage sensor you could work out if you had excess power (ie charge voltage of 13V+) and aim for a lower fridge temp
 
Does that allow you to trick the fridge compressor to come on with the S8050?

If you added a voltage sensor you could work out if you had excess power (ie charge voltage of 13V+) and aim for a lower fridge temp
Yes, it logs temperature from 3 thermometers, one on the cold plate, 1 next to the compressor and 1 at the bottom of the fridge which switches compressor on at 6deg, off at 4deg. Been working like that flawlessly for years on an arduino.
http://www.ybw.com/forums/showthrea...thermostat-probs&highlight=android+thermostat

Good idea about cranking up a bit when there's spare power - the ammeter has an accurate voltmeter as well plus battery current & voltage & solar data available as signalk as well so shouldn't be too hard to calculate when there's power spare, even if just on a timer for later on in the afternoon when the batteries are towards fully charged from solar.
It logs duty cycle as well so thinking is let it go a little warmer when the duty cycle gets over 50%.

It's possible to control the compressor speed between 2000RPM & 3500RPM as well so might as well fit 3 control transistors with different resistors so at least have the option to varispeed a bit. And might as well throw in another couple of transistor switches to control fans, only costs a few pennies :cool:
pPNMo8v.png

https://www.coastalclimatecontrol.c...on/256-speed-fast-is-fine-is-slow-better.html
https://forum.allaboutcircuits.com/threads/danfoss-compressor-speed-controller.118993/
 
Anyone used micropython for esp programming? Thinking of moving that way...
Though maybe nobody on here even knows what it is ;)

I do.

I really like Python. However lots of the micropython libs are not as mature, probably due to comparative ages, which caused me issues and I moved away.

Lots of the ardunio stuff is pretty stable. May not be ideal (eg. One wire libs delay lots ... and as one wire can be slow this is not great if doing more than one thing (like reading the Revs off an alternator). But stable.

Maybe I got burnt doing GPS/GNS, gets iky quick (e.g. very accurate GNS Fixes down to the last meter).

Also, if doing anything lowpower (as in sleep the CPU) then ESPs are a little pants, as the CPU effectively reboots each time it "wakes" which means doing anything with state a pain.

If KISS and the sensors are simple, no low power requirement, then microPython is probably okay, if not a decent approach as python is ace!
 
I do.

I really like Python. However lots of the micropython libs are not as mature, probably due to comparative ages, which caused me issues and I moved away.

Lots of the ardunio stuff is pretty stable. May not be ideal (eg. One wire libs delay lots ... and as one wire can be slow this is not great if doing more than one thing (like reading the Revs off an alternator). But stable.

Maybe I got burnt doing GPS/GNS, gets iky quick (e.g. very accurate GNS Fixes down to the last meter).

Also, if doing anything lowpower (as in sleep the CPU) then ESPs are a little pants, as the CPU effectively reboots each time it "wakes" which means doing anything with state a pain.

If KISS and the sensors are simple, no low power requirement, then microPython is probably okay, if not a decent approach as python is ace!

Thanks, interesting. Think I'll give it a good hit anyway, struggling with making a 'my sensors' library in c++ . It's all slow sensor stuff anyway, agree with the ESP32 deepsleep, either language looks like it more of a start again from the top in a while and not a delay in a loop. Turning off the wifi most of the time might get the power down, not exactly monsterous to begin with.
Quite amazing what you can get and do with a few quids worth of ebay bits though! :cool:
 
Go for it YMMV

Yes it is amazing that a fee £ will get you a Board, combined with lots of open source code, blogs and youtube and you have a useful Gizmo!
 
Top