Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
-
- Posts: 10
- Joined: Wed Feb 15, 2023 9:43 pm
Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
I would like comments about the feasibility of using a Raspberry Pi (or Arduino board) to read multiple pulse inputs (6) and send/receive messages over RS485 using the Push3 protocol; and then use the EKM Cloud to process data. I know how to read the inputs and could handle parsing the protocol, but are there anything that would prevent this from working? Essentially, I am simulating an Omnimeter Pulse Meter. Is there C-Code for a IEC 62056 meter that would be a good starting point?
-
- Posts: 10
- Joined: Wed Feb 15, 2023 9:43 pm
Re: Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
One possible issue is the Meter Number. The Dash program wanted me to enter a "valid" number, but seemed to accepted a bogus number.
Re: Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
The EKM Push3 will only read data from the Omnimeters it is assigned to. So there would not be a point to spoof an Omnimeter Pulse v.4. You would have to spoof an Omnimeter Pulse v.4 number that you already own. In short, I do not know of an easy way to do this, or a reason to do it.
-
- Posts: 10
- Joined: Wed Feb 15, 2023 9:43 pm
Re: Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
The new EKM ioStack seems to accomplish what I wanted to do. It appears to be a replacement for the Omnimeter V.4.
How is the ioStack programmed? Could the analog inputs be used as additional pulse counters?
I would be interested in building my own version of the ioStack.
Is a schematic diagram available, or an interface specification?
How is the ioStack programmed? Could the analog inputs be used as additional pulse counters?
I would be interested in building my own version of the ioStack.
Is a schematic diagram available, or an interface specification?
Re: Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
Hello,
Im glad to hear you are interested in the ioStack. In our opinion it is a cool piece of kit!
The ioStack is hot off the press, so it will take us a while to get our documentation in order. We do not plan to open source the ioStack hardware, but we do plan to share the ioStack RS485 communication protocol (similar to how we publish the Omnimeter v3 and v4 protocols here: https://documents.ekmmetering.com/api-d ... unications)
We have started working on the ioStack API Builder for Push data. Here is the ioStack API Builder for the public account ioStacks: https://api.ekmpush.com/account/iostack ... AxMDoyMDIw
Im glad to hear you are interested in the ioStack. In our opinion it is a cool piece of kit!
The ioStack is hot off the press, so it will take us a while to get our documentation in order. We do not plan to open source the ioStack hardware, but we do plan to share the ioStack RS485 communication protocol (similar to how we publish the Omnimeter v3 and v4 protocols here: https://documents.ekmmetering.com/api-d ... unications)
We have started working on the ioStack API Builder for Push data. Here is the ioStack API Builder for the public account ioStacks: https://api.ekmpush.com/account/iostack ... AxMDoyMDIw
Im not sure I understand your meaning. It is flashed with the ioStack firmware we developed via the JTAG port.How is the ioStack programmed?
There is not a reliable way to use the analog inputs as pulse counters that I am aware of at this point. Though its an interesting idea!Could the analog inputs be used as additional pulse counters?
-
- Posts: 10
- Joined: Wed Feb 15, 2023 9:43 pm
Re: Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
Thanks for the prompt reply.
1. I'm a firmware developer and would be interested in flashing my own code via JTAG.
Will the documentation be detailed enough for me to do this?
2. I've used current transformers in the past to measure power, like is done in the Omnimeter V.4,
Will the ioStack natively support this application?
3. Do you need Beta testers?
1. I'm a firmware developer and would be interested in flashing my own code via JTAG.
Will the documentation be detailed enough for me to do this?
2. I've used current transformers in the past to measure power, like is done in the Omnimeter V.4,
Will the ioStack natively support this application?
3. Do you need Beta testers?
Re: Pulse inputs to RS485 Push 3 protocol with Raspberry Pi
Hello!
1. We wont be including the documentation about how to flash over the JTAG, but if you own the ioStack, there is nothing we can do to stop you from tinkering with it. What functionality would you like to add? What improvements would you like to see? Or are you just curious to re-create the ioStack firmware yourself?
2. The ioStack has 4 analog inputs, these measure 0-5V DC signals. Our current transformers put out an AC signal which is 0-26.6mA, so any CT that puts out an AC signal will probably not be what you want to use.
3. Yes, we do need folks who are willing to test the ioStack (connected to a Push3 gateway), who have a bit of patience, who want to work with us, and who are willing to give us feedback and make suggestions, to buy one on our website here: https://www.ekmmetering.com/collections ... s/iostack
We are not aware of any major issues with the ioStack firmware, but it is not a mature product, so that is why we are saying it is in beta for now (January 2024)
1. We wont be including the documentation about how to flash over the JTAG, but if you own the ioStack, there is nothing we can do to stop you from tinkering with it. What functionality would you like to add? What improvements would you like to see? Or are you just curious to re-create the ioStack firmware yourself?
2. The ioStack has 4 analog inputs, these measure 0-5V DC signals. Our current transformers put out an AC signal which is 0-26.6mA, so any CT that puts out an AC signal will probably not be what you want to use.
3. Yes, we do need folks who are willing to test the ioStack (connected to a Push3 gateway), who have a bit of patience, who want to work with us, and who are willing to give us feedback and make suggestions, to buy one on our website here: https://www.ekmmetering.com/collections ... s/iostack
We are not aware of any major issues with the ioStack firmware, but it is not a mature product, so that is why we are saying it is in beta for now (January 2024)