Hmm, You may be more correct on that than you realize.
The espressif website says the esp8266 draws 120 mA when the output is at +13 bBm, which is the lowest value shown on the chart. (170 mA at +17 dBm) If the output could be turned down a bit more, that might help – at the expense of operating range.
Yeh, I thought the esp8266 might be 120mA or there abouts, I’m sure I’ve read that somewhere here with ref to the emonESP. I doubt I would personally go that route, it was just an example. However, I do now wonder IF there were several slaves daisychained (including the 5v terms) if you would effectively have No of slaves x 100mA on tap for powering the master? Depends how isolated those outputs are I guess?
Not sure what you mean there, by “the device” are you referring to the monitor? That’s limited to 100mA. Or are you refering to a “master” device with it’s own supply? I was suggesting using the esp8266 AS the master and powered via the slave(s).
My point was that if the slave(s) can power a simple master and communicate with the outside world (eg post to emoncms or emonhub) this is a totally self-sufficient monitoring solution, no additional AC adapters required (9v AC or 5v DC), no additional CT’s, no sockets to be installed for those plug-in adapters and no additional hardware to plug a USB adapter into or power supply for that device. But, although there may be a cost/space saving due to low component count, it is not something that a casual “DIYer” could easily install, because of the lack of plug-in adapters.
That was my thinking, I have no Modbus devices at home, so even if this turns out to be useless as a monitor, I will have something to develop Modbus applications with and test hardware/adapters etc for not a lot of money.
Not necessarily unity. When I put mine into calibration mode, it expects 230V, 2A with a 60° phase shift as recommended by the energy IC manufacturer. Any introduced phase error becomes much easier to spot once the two sine waves are offset from each other.
Hi Chaveiro, I will try to help a bit. I have a topic which I am going to post a few instructions on as I also want help similar to you and in return I hope someone can help me. Here is the link: Modbus RTU (RS485) Instructions
It’s very basic. Doesn’t do anything but read the registers and print their contents.
As written, it needs minimalmodbus and Advanced Python Scheduler v2.12
You dont have to use APS. I use it to read my other meters every 5 seconds, so I left it in the script.
Any loop construct will work.
I set my camera to 12 MP in the hopes of being able to enlarge the picture to read the characters on the chip, but no joy. The markings are very faint. I had it in full sunlight, but still no help. Bummer.
PB and I thought the same thing, i.e even if it’s junk, at that price it’s a throw-away item.
So far, it seems to be fairly accurate. I have a 40 W incandescent lamp as a load with 10 turns wrapped
through the CT window and it’s reading 429.1 W, 3.57 A, 120.2 V.
So internally consistent at least. Do you have a trusted meter you can compare those numbers with?
I guess I could buy one and stick it on the calibrator to give it a good run for its money, but I doubt my calibrator’s V output would have enough ousht to drive its power supply. I needed a separate V input on my monitor for that reason. One V input to power the unit, and 3V inputs to measure. Once installed, you can daisy chain the first off any of the other three but when calibrating, just having the power supply attached to the calibrator’s V output distorts the signal (as do many 9VAC wall-warts).
That too would need an isolated STLINK programmer. Actually, that entire hack project is very dangerous (they do mention it in the fine print). They’re wiring up external hardware to the live side of the barrier so all of the display hardware is live.
Now, speaking of STM32s… what’s been happening out there in OEM / STM32 land?