- Posts: 234
- Karma: 1
- Thank you received: 18
Ian wrote: I also have something like this, but I like your orange idea better than mine. also the firmware upload is a great idea. Do you mind if I steal those ideas?
My code is already out there, and as you know I am happy for people to use it, as long as they don't just plain copy and compete...
Ian wrote: Great, thanks for that.
That Node.js tip is really neat, BTW...
judge wrote: BTW I am using the Sloeber plugin for Eclipse. What a joy it is to have a professional-grade development environment for 'Arduino' related code. Library management, code navigation, outline views, just great! I added commands to build/upload spiffs too, so it is all in one place.
judge wrote: Yes the one horse board is not cheap, but the design is open source and it includes support for battery power, which is something I want to explore.
Having headers is something essential for me at the prototyping stage. After that Inwill be looking more at the PSF-B85
judge wrote: If by 'Updater' you mean 'OTA' you can look at my NCS314 repo ( github.com/judge2005/NCS314WiFi ) for examples. One issue I never solved is the need to power cycle it after an upload. Also be aware that you need twice the amount of 'RAM' that your code takes up. It works by uploading the new code to the unused area and then switching to it. I also got OTA spiff loading going - this is just part of the regular tool chain.
vladco wrote: 3. they idea was it should do that, and i was going to use the OE (output enable) of the '595 shit register for that purpose - unfortunately i didn't pay close attention to the datasheets where its stated that when the OE is HIGH the outputs are HiZ and i am not entirely sure what the darlington array is doing when its not driven.