GEM PT setting?

[Teken]

Ben,

Setting the GEM to the default results in a very low line voltage which is not correct. I am at 191 - 3, which is still lower then the line voltage by 2-3 volts.

The correction factor to reflect the line voltage is 194 - 3 to show the POCO power coming in.

As stated these values have never been changed since install. But during the last few firmware releases these values need to be fine tuned to reflect the line voltage.

These spikes never show up on the DB, SEG, they come in from the ISY from the email monitoring set for all specific circuits being monitored.

Teken . . .


Encrypted By: Phoenix Security Solutions

[ben]

Ben,

Setting the GEM to the default results in a very low line voltage which is not correct. I am at 191 - 3, which is still lower then the line voltage by 2-3 volts.

The correction factor to reflect the line voltage is 194 - 3 to show the POCO power coming in.

As stated these values have never been changed since install. But during the last few firmware releases these values need to be fine tuned to reflect the line voltage.

These spikes never show up on the DB, SEG, they come in from the ISY from the email monitoring set for all specific circuits being monitored.

Teken . . .


Encrypted By: Phoenix Security Solutions

Did we ever ship you a BrulTech PT? Based on your thread with the pictures of your GEM, you have the jumper connected and the CUI Stack PT.

If you do have the CUI Stack PT, I'll have to get Paul to double-check the PT values as 194 - 3 are the exact settings for the BrulTech PT with the jumper connected.

Ben

[Teken]

Ben,

Setting the GEM to the default results in a very low line voltage which is not correct. I am at 191 - 3, which is still lower then the line voltage by 2-3 volts.

The correction factor to reflect the line voltage is 194 - 3 to show the POCO power coming in.

As stated these values have never been changed since install. But during the last few firmware releases these values need to be fine tuned to reflect the line voltage.

These spikes never show up on the DB, SEG, they come in from the ISY from the email monitoring set for all specific circuits being monitored.

Teken . . .


Encrypted By: Phoenix Security Solutions

Did we ever ship you a BrulTech PT? Based on your thread with the pictures of your GEM, you have the jumper connected and the CUI Stack PT.

If you do have the CUI Stack PT, I'll have to get Paul to double-check the PT values as 194 - 3 are the exact settings for the BrulTech PT with the jumper connected.

Ben

Nope, I just have the CUI Stack PT. If you believe a new BrulTech PT is the logical solution for this that's fine. I believe it might be possible that the last few COM / Engine firmware may have introduced a small bug in the PT settings.

Which is causing the measured line voltage to fluctuate or at the very least not be reflected correctly.

As always I thank you!

Teken . . .

[ben]

Nope, I just have the CUI Stack PT. If you believe a new BrulTech PT is the logical solution for this that's fine. I believe it might be possible that the last few COM / Engine firmware may have introduced a small bug in the PT settings.

Which is causing the measured line voltage to fluctuate or at the very least not be reflected correctly.

As always I thank you!

Teken . . .

Was it reading correctly at 194/3?

If it reads accurately at those settings, then use those ones.

In the meantime, I'll let Paul know about the fluctuations.

Ben

[Teken]

Ben,

The GEM was as running fine in the default 187/3 since install. It now is set to 194/3 to compensate for voltage drift.

Let me know what you find out. Also could you get the release notes on the latest COM firmware just released.

Maybe Paul has a fix already! LOL

Teken . . .


Encrypted By: Phoenix Security Solutions

[guessed]

Just gotta thank you guys for documenting these settings on the Forum here. I just ran an upgrade of my GEM (was 1.63/1.35 -> 2.58/1.47) and was trying to work out why btmon was seeing 0-values across all channels.

Turns out the PT Type had been set to 0 during the NU 5.8 FW upgrade process, and it left me scratching my head...

Reset to 187/3 and she's rockin again! #175

[ben]

Just gotta thank you guys for documenting these settings on the Forum here. I just ran an upgrade of my GEM (was 1.63/1.35 -> 2.58/1.47) and was trying to work out why btmon was seeing 0-values across all channels.

Turns out the PT Type had been set to 0 during the NU 5.8 FW upgrade process, and it left me scratching my head...

Reset to 187/3 and she's rockin again! #175

Yikes, old versions there.

Couple of things,

Make sure you popped the battery/cycled power after upgrading to avoid lockups due to a flag that's held constant when the battery is applied.

Also, make sure your "GEM Hardware Option" is set correctly.

Ben

[guessed]

Yep, followed the instructions and all [otherwise] went well. It was really on this setting PT Type setting that was whacked... and a minor problem having to reset the [new] password to get started.

The HW Setting is more interesting. I have a XBee version, but swapped out the XBee module on COM2 for a RN-XV Wifi module. It's been running happily that way for yrs, even though it's non-standard

Just doing the upgrades, as I'm prepping to get a DashBox.