... I have hooked up an O2+ on a mini-dock to my charger doctor to observe the results.
When running with radio enabled, I see 0.10 to 0.12A
After issuing a reboot, the shutdown processes execute, the radio and LED are turned off and the current consumption drops to 0.00A / 0.01A - so between 0 and 15mA I would guess (charger doctor isn't any more accurate than that).
So there is still some current draw, until I flip the power switch on the mini-dock at which point it is constantly showing 0.00A.
So the electronic power off is not really off, just a close facsimile of off.
It's very nice indeed. So I have to repeat my previous halt / poweroff / reboot experiments.
I think you can do this with your custom-made 'LEDE firmware (17.01)' instead of the official b160.
Could you share with us that FW?
@Yvan-Gagnon I've mentioned this a couple times in response to other posts and do not remember if one of those posts was yours, if so, I apologize for bringing it up again, but, it is possible to gain access to all the pins by using a female header with long pins. just insert the female header into each header of the mini dock and then insert [carefully] the omega2+ into the long pin female headers. this will leave all pins exposed that you can then use various methods to attach wires from your project to the appropriate pins. granted it is a "garage style" method and care must be taken to not damage the long pin headers, however it worked for any project i saw hooked up this way at a local hackerspace.
For each and every point you listed there is a mass of documentation available.
You should be able to install openssl on the Omega2+ (from LEDE repos or directly Omega repos), which gives you the means to generate what every certificate you like. You haven't mentioned what kind of certificate you need, with what cryptographic parameters (RSA/ECC, curves, modulo length, hash algorithm, ciphersuites and key exchanges to be supported,...). Actually you don't even have to install and use openssl on the Omega2+, you can generate the keys and certificates off-site.
For web server (and uhttpd-mod-tls) documentation see
With the proprietary driver the Omega2 ships with - sadly, yes, the AP is always on.
But with the open source mt76 driver, disabling the AP is no problem.
And note that mt76 has matured a lot since this thread started a year ago! As a true open source project, there are people working steadily to improve it. There are updates every few weeks to make it better. For my needs, mt76 has become stable enough already many months ago. And it is a much cleaner setup, using standard cfg80211. I like it way better than these sad proprietary chunks of code tied to a specific kernel version and thus blocking all other progress!
@Miguel-Miranda no, I just used a free GPIO to enable rs485 drivers from my highlevel software. That's far from optimal of course, because I have to estimate how much time my outgoing data will need and time the GPIO accordingly. But for my application (Swiss railway split-flap displays) this was good enough.
Of course, that's something that probably could be done better at the driver level. I haven't dug very deep, however I'm not sure the UART hardware could provide the needed all-data-is-sent-IRQ. The way MediaTek integrated the UARTs is a bit sad, because they did not provide a way to multiplex the native UART handshake signals to pins.
It would be nice if proper HW handshaking could be done entirely in software, though. I'm open to proposals how that could work ;-)
FYI even when I do /overlay and make a 2GB swap file, the version of node does crash on some instances like installing "azure-iot-device-amqp" the nodejs run time has its own buffer that needs to be increased, though from the error they posted I dont think its this issue.
Another thing about npm installs is that in some cases you need python or some other dependency like git and npm builds the module on the onion, that takes a lot of resources. For my application I use 81% file storage and have 4.7mb left but I have these modules installed:
@David-Lochlin je suis d'accord, dommage sa petite taille été un super avantage mais bon les développeurs on tellement passé de temps a vouloir le vendre a tout prix en dénigrant les autres produits du même genre qu'ils ont oublié de finir leurs propre produit.
I had a similar problem, the battery would not charge at all. It worked fine until I drained the battery completely, after that the power dock would no longer charge the battery. Just as a quick experiment I connected the battery to one of my adafruit feather boards and let it charge the battery for 15 minutes, after this it worked fine again and was charged by the power dock.