EKM Metering

One thing about Dash: the library files are under the name "EKM Dash Libs" (the spelling is critial, the dlopen() calls require that name-with-spaces, and dash executable should be in the same directory. Moreover, though the executable name is "EMK Dash" with a space, which is pr...

Ubuntu 14.04. 32bit . Has just 4GB Ram, so there was no good reason
to run x64 And I've been unable to find bigger RAM that (regardless
of specification and MOBO matching what original ram says)
passes memtest on this motherboard. So: 32bit pointer, 32bit long int.

On starting Dash and trying to run the free trial I get 'unhandled NilObjectException'. The Protocol.pdf is a sketch, isn't it. Not a definition. The forum article you mention does have some useful info. Thanks. Seems like the most productive approach would be to get dash running, but I have no idea...

I successfully read A and B data, but I'm not understanding the sequence of operations for setting some things in the Pulse v.4. Writing in C on Linux. My rash assumptions were as follows. Not working so...what are the corrrect sequences? I don't send the Pulse v.4 12 byte meter addresss here, (what...

Yet another bug in my code trying to help me debug was confusing me. Now I am seeing correct-seeming response to Request Type A. Really simple socket coding. But the sleep() requirement was a small surprise and it was appalling how many mistakes I made in such a small test application. So: Now I can...

Adding a sleep(1) between write() and read() has improved things.
Now getting the initial hex 02. !

Getting a Malformed Packet on the initial byte ( a hex 02 ) of the response to a request type A sometimes. As reported by wireshark. The byte disappears from what my code sees. The next frame from wireshark after the 19 bytes ofa request type A I just sent is: 5 0.009522000 192.168.88.6 192.168.88.2...

The Dash software gets App.Event_Open Delegate.Invoke Application._CallFunctionWithExceptionHandling REALbasic._RunFrameworkInitialization from 'An unhandled NilObjectException has occurred". Ubuntu 14.04. So I went directly to writing my own code and watching the ethernet bytes. Still ironing ...

Uart settings ok, I think. Doing the read repeatedly till all 255 returned is looking ok. Should have thought of that right away. The write bytes: Hex ascii. non printable as . 2f3f3030 30333030 30303132 33373030 /?00030000123700 210d0a !.. It is not clear, in what I've found on the developer page, ...

The only pdf I can find on iserial is for the v.2 device, and that doc is rather out of date as I have a new v.4 iserial: the web page served by the device has lots of things not mentioned for v.2. Is there a more recent pdf? I'm writing a to iserial using C and watching the Lan with wireshark. Turn...