[quote=“smilligan, post:17, topic:167492”]The ECM is connected via USB<>RS232. Hawking device that was recognized as :
root@MiOS_16414:/proc/tty/driver# cat usb-serial
usbserinfo:1.0 driver:v1.4
0: module:pl2303 name:“PL-2303” vendor:067b product:2303 num_ports:1 port:1 path:usb-00:03.0-1.2[/quote]
You should also see this Serial device appear in Vera/MiOS itself, under the MiOS developers Dialog, Serial Port configuration tab.
I’ve updated the UI4 Installation doc on the code.mios.com wiki area for this plugin to show examples of this (for a FTDI Serial port, but it’s similar for PL2303 stuff)
We then installed your latest plugin using the 6 files to upload.
I then created a device, and populated ONLY the fields in teh device you suggest.
We have never created a serial device or added new plugins so we are out of our element.
When we created the Brultech device, it shows up briefly (for about 5 minutes) with V and W being empty.
- Not sure HOW to tell this device to get its data from the serial interface defined above
- Not sure how to add new devices for each of the additional circuits.
By default, it’ll configure itself with a “Parent” device, along with a single Child device. If they cannot communicate with the Brultech, or if the Brultech isn’t configured for the ASCII Protocol (PnP models ship this way) then the
W and
V values will not fill in.
I’ve updated the Install instructions somewhat to show what the Serial Port config would look like. I haven’t specifically tested that situation right now, as my Brultech is hanging off a RS232-Wifi adapter, and I can directly configure an “IP Address” with the Brultech Plugin/Device.
Let me know if it doesn’t work, and I’ll try that out tomorrow night when I have a little more time (the code is common with other cases where I do that also, like the DSC Alarm, so it should be fine)
We have enabled remote support on this device (1xxxx)
Won't really work for me, since I don't work for MCV. Remote Support only works for folks that work for MCV. Everyone else has to debug remote systems using logs and so-forth, but the problems you're having are more config related at this time and we should be able to get you going on the forums directly (or, just by me documenting these parts 8)
ALSO: We have read the brief description on plugin. There is a comment:
"The Plugin doesn't yet support Ascii or Binary format data directly from the device, it only works for the Plug & Play models right now."
I assume this means you support only the HTTP mode of the ECM as established in the IA tool. Can you confirm? If so, does it matter what the start of the HTTP post looks like? Or do you simply strip all of that off and disregard?
In short, the Brultech devices support Binary (the default format) and an ASCII format that’s used when they talk to things like
http://my1240.com (as a proxy service to Google PowerMeter)
The PnP models ship configured to use the ASCII protocol, and these “commands” are sent over both the inbuilt Zigbee Module, and the RS-232 interface “simultaneously”.
For PnP models, data on the Serial port looks like:
[tt] GET /usr/bxxxxx/dev.php?sec=7983906&v=1225&c1w… HTTP/1.0[/tt]
My Plugin looks for this type of line using a pattern like:
[tt] GET /*? HTTP/?.?[/tt]
in the example above “usefulStuff” gets set to:
[tt] sec=7983906&v=1225&c1w… [/tt]
which I then process to extract the data values for each channel/CT. Technically, anything emitting that basic format will be processed for it’s values.
Until recently I haven’t had a Windows machine @Home, so I haven’t been able to run the IA Tool so I left each of my ECM-1240’s in their default “PnP” configuration (which is how I bought them).
I bought a Netbook last Weekend so I can play with the tool, and a few other “windows-specific” things that don’t otherwise play well with my Mac’s (like some Native SMS device-config tools I have, and some of the Ethernet-RS232 converters I use)
