|
|
|
is it possible to create three more device types: ECM-1220,
ECM-1240, and GreenEye?
i'm sure you could use images from brultech for
the devices - if not let me know and i'll take pictures and send them.
more important are the default stream configurations. the ECM-1220
should default to having 4 streams: power and energy for 2 channels, with names p_ch1, e_ch1, p_ch2, and e_ch2.
the ECM-1240 should default to having 14 streams: p_ and e_ for ch1,
ch2, aux1, aux2, aux3, aux4, and aux5.
i'll let you know the greeneye
names in a couple of months (still sorting out the code for that one -
it has 32 channels!)
this will make it *much* easier for folks with brultech ECM devices
to get connected to SEG, especially when they use ecmread.py for the
collecting and uploading.
m
|
|
|
|
Hey!
I checeked out your script, and rekon we could easily iuse the SEG discovery process to help the dead simple setup of Brultech devices. That may be simpler than having special device types?
I've been thinking about this for a little while now, just letting you know it's still active in the development stack!
Let me know,
Sam.
|
|
|
|
|
the 'discover' option looks like the easiest way to configure everything. unfortunately i did not notice it until after i set up 8 devices with 14 streams per device. could you confirm the process?
1) create account at seg web site
2) create a site at the seg web site, obtain the site token
3) click 'my profile' tab then click 'discover' button
4) start running ecmread
does the 'discover' automatically create devices, or must the devices be configured before doing discover?
as for the device types, perhaps if there were a generic 'monitor' type for which anyone could insert his/her own image? the ecm is a monitor, not a meter, so it does not really fit any of the existing types. not a big deal, since many of the types actually work, but i've seen smaller semantic issues cause confusion for noobs...
|
|
|
|
|
Discover is the easiest way I know ;) It does some IP address binding, and if you send the token of site_unknown for a device you want to setup, it will tell you what the token is for the site, either created during the new discovery or for an existing site. Then just store the token on the ecmread end and use that for future api calls for that device.
It then creates devices, streams and other stuff based on what it sees in the data coming in (for a period of time). No need to pre-configure anything!
Then all that's needed is to label in SEG what's what after it's all done, and setup dashboards etc. However we have some templates in alpha to make this even easier too.
If you send or post here the image you would like to use and let me know the generic config then I can setup a special device for the ECM if you like? Then the discovery can be adjusted to see the specialised ch1 etc and perhaps even choose that device type on discovery.
We may need to tick tack a little to get this all rolling smoothly :D
Sam.
|
|
|
|
|
here is an image of the ecm-1240:
http://lancet.mit.edu/mwall/projects/power/ecm1...
a single ecm-1240 collects these data:
volts, p_ch1, e_ch1, a_ch1, p_ch2, e_ch2, a_ch2, p_aux1, e_aux1, p_aux2, e_aux2, p_aux3, e_aux3, p_aux4, e_aux4, p_aux5, e_aux5. the aux5 might also send a dc voltage (v_aux5). the units of aux5 might be a counter instead of w/wh (c_aux5 instead of p_aux and e_aux5).
is there something ecmread could send that would tell seg the device type to use? or do you prefer to have seg attempt to guess the device type?
|
|
|
|
I have 3 Brultech ECM-1240s feeding into SEG. When I created/discovered/whatever back in May, they were given a device type of "SEGmeter". Is that the device type I should be using now? Does changing the device type have any impact on existing feeds/data? So, should/could I change it? Or should I leave it as is?
|
|
|
|
|
Changing the device type has no real impact on an already existing device - for now at least ;)
Sam,
@samotage
|
|
|
|
Using new device and start new process on impect.
|
