Voltage - How is it monitored and sampled

[Teken]

How is the voltage on the GEM configured to detect the line voltage? How frequently does it sample the line voltage and what is level of accuracy of this process?

IE. Can the GEM detect a drop in voltage for under 10 seconds?

[ben]

How is the voltage on the GEM configured to detect the line voltage? How frequently does it sample the line voltage and what is level of accuracy of this process?

IE. Can the GEM detect a drop in voltage for under 10 seconds?

It's not too easy to find, but you can download the GEM spec sheet here (http://brultech.com/home/store/attachme ... tachment=1).

Voltage sampling is at 20.8 kHz, the wall transformer PT is typically within 1-2%. We'll eventually have a 1% PT, for now you can use one from Magnelabs if you want something more accurate (http://www.magnelab.com/products/curren ... 33v-output).

The voltage is updated every second.

Ben

[Teken]

How is the voltage on the GEM configured to detect the line voltage? How frequently does it sample the line voltage and what is level of accuracy of this process?

IE. Can the GEM detect a drop in voltage for under 10 seconds?

It's not too easy to find, but you can download the GEM spec sheet here (http://brultech.com/home/store/attachme ... tachment=1).

Voltage sampling is at 20.8 kHz, the wall transformer PT is typically within 1-2%. We'll eventually have a 1% PT, for now you can use one from Magnelabs if you want something more accurate (http://www.magnelab.com/products/curren ... 33v-output).

The voltage is updated every second.

Ben

Is there any instance where the voltage monitored by the GEM will not be reflected in the Dash Box line graph.

[ben]

Is there any instance where the voltage monitored by the GEM will not be reflected in the Dash Box line graph.

Are you looking at the real-time values or minute values?

The minute values is the average of all voltage samples within that minute.

The only time they'll be really comparable is if when the packet comes into the DashBox, you also catch the packet from the GEM. Then the real-time voltage on the DashBox should be the same as the voltage sent from the GEM.

Ben

[Teken]

Is there any instance where the voltage monitored by the GEM will not be reflected in the Dash Box line graph.

Are you looking at the real-time values or minute values?

The minute values is the average of all voltage samples within that minute.

The only time they'll be really comparable is if when the packet comes into the DashBox, you also catch the packet from the GEM. Then the real-time voltage on the DashBox should be the same as the voltage sent from the GEM.

Ben

Ben,

I was looking at the minute values and thought it would present every second in that minute. If its possible to introduce a feature where a person can record every second and display it when zooming in that would be extremely helpful for me.

Perhaps a toggle feature to enable this or at the very least have an option where if the user enables the feature it could capture readings for a 5-10 minute period to keep processing time down on the Dash Box.

[ben]

I was looking at the minute values and thought it would present every second in that minute. If its possible to introduce a feature where a person can record every second and display it when zooming in that would be extremely helpful for me.

Perhaps a toggle feature to enable this or at the very least have an option where if the user enables the feature it could capture readings for a 5-10 minute period to keep processing time down on the Dash Box.

You would have to up the send interval on the GEM to send every second.

I wouldn't want the DashBox doing any logging every second due to the hardware involved, but let me see what happens if I set it to every second. If that works well, you could either use ecmread.py or I could modify our standalone dashboard to accept packets every second.

You can set the GEM to send every 5 seconds and I could extend the real-time data a bit longer, it's stored in memory to avoid excessive writes to the storage.

Ben

[Teken]

I was looking at the minute values and thought it would present every second in that minute. If its possible to introduce a feature where a person can record every second and display it when zooming in that would be extremely helpful for me.

Perhaps a toggle feature to enable this or at the very least have an option where if the user enables the feature it could capture readings for a 5-10 minute period to keep processing time down on the Dash Box.

You would have to up the send interval on the GEM to send every second.

I wouldn't want the DashBox doing any logging every second due to the hardware involved, but let me see what happens if I set it to every second. If that works well, you could either use ecmread.py or I could modify our standalone dashboard to accept packets every second.

You can set the GEM to send every 5 seconds and I could extend the real-time data a bit longer, it's stored in memory to avoid excessive writes to the storage.

Ben

Ben,

I don't think setting the GEM to send every second would be a good idea. As previous history has shown there is too much traffic / conflict where the GEM / Dash Box / ISY became over loaded with in coming streaming data.

I believe my GEM is set to send to the Dash Box / ISY at 8 second interval. Any help in this area would be greatly appreciated. I fully realize that the Dash Box and GEM were never really intended to perform this specific task.

But, in the big picture believe features such as this sets your product offering far apart from other Energy Monitoring devices.

At a very high level: My intent is to use your products in the most extreme and esoteric ways that normally would be deferred to a industrial tool. Thus far the GEM / DB has met and surpassed a lot of the tools I use at work only because of the wealth of user friendly tools and data retrieval.

[ben]

I don't think setting the GEM to send every second would be a good idea. As previous history has shown there is too much traffic / conflict where the GEM / Dash Box / ISY became over loaded with in coming streaming data.

The lowest the GEM can send binary packets at right now is every 3 seconds, but we could try every second. The DashBox/ISY will probably become overwhelmed though. I'm going to run every 5 seconds over the weekend and see the results. I've also increased real-time data from 2KB to 2MB.

I believe my GEM is set to send to the Dash Box / ISY at 8 second interval. Any help in this area would be greatly appreciated. I fully realize that the Dash Box and GEM were never really intended to perform this specific task.

The DashBox wasn't designed with that in mind, but the GEM was designed to report at fast intervals like our other monitors.

But, in the big picture believe features such as this sets your product offering far apart from other Energy Monitoring devices.

At a very high level: My intent is to use your products in the most extreme and esoteric ways that normally would be deferred to a industrial tool. Thus far the GEM / DB has met and surpassed a lot of the tools I use at work only because of the wealth of user friendly tools and data retrieval.

That's good to hear, things will keep constantly improving also.

Ben

[Teken]

Ben,

I really appreciate all the insight and continued support and development for the Dash Box / Green Eye Monitor. Is there any reason the system can't be programmed to simply capture (sample) the line voltage then send it out in (bursts / chunks) like the normal packets sent via the SEG?

How you do this magic really is above my skill set but wanted to bounce that idea out. Maybe the way I am thinking about this is quite different in how its actually done via software / hardware.