COM 3.16 / ENG 1.49 Release Notes

[Teken]

Hello All,

I installed COM 3.16 / ENG 1.49 when it was released last week. The GEM is running like a champ and did not see any obvious UI changes or options.

So, what's under the hood that has been changed?

I am currently tracking any power / temperature spikes which does not seem to have occurred as of late. I still receive e-mail alerts from the ISY Series Controller that the system has detected a negative energy value from my fridge from time to time.

I have placed Brultech / UDI on the mailing list so you can monitor the frequency of this issue along with the voltage issue. One of the things I also did was add in the Dash Box via state variables to the e-mail alert for comparisons.

I believe doing this has provided some insight but what it is I really can't say. If I use the ISY's default alert this will always provide me the negative values I have seen. When the Dash Box sends out the same information the actual (current wattage) is not in a negative state which in the big picture is good!

Maybe this will help the two companies narrow down where and why this issue persists. I will upload a screen shot and high light the information for more clarity.

[ben]

I'll have to get Paul to get me the release notes, I think there was some changes to the temp sampling to prevent invalid reads from the temp sensors.

[Teken]

I'll have to get Paul to get me the release notes, I think there was some changes to the temp sampling to prevent invalid reads from the temp sensors.

That would be great as he reached out to me indicating a 10K resistor placed in parallel would resolve why one of the existing sensors could not be enrolled again.

When I installed the Autelis Bridge there were a few extra 1 wire sensors on hand. When I tried to add one of the new ones to the GEM it freaked out and took the entire 1 wire network down.

Later on I tried to add back the (old existing) sensor to the GEM but had the same problem? This is when Paul indicated a 10K resistor would solve this issue?

Looking forward to his reply as I have another 20 sensors enroute!

[ben]

I'll have to get Paul to get me the release notes, I think there was some changes to the temp sampling to prevent invalid reads from the temp sensors.

That would be great as he reached out to me indicating a 10K resistor placed in parallel would resolve why one of the existing sensors could not be enrolled again.

When I installed the Autelis Bridge there were a few extra 1 wire sensors on hand. When I tried to add one of the new ones to the GEM it freaked out and took the entire 1 wire network down.

Later on I tried to add back the (old existing) sensor to the GEM but had the same problem? This is when Paul indicated a 10K resistor would solve this issue?

Looking forward to his reply as I have another 20 sensors enroute!

Sent this to him in an email.

[Teken]

Just circling back to see about the release notes.

[cvachon79]

Just circling back to see about the release notes.

Were these ever posted anywhere? I looked in the firmware section and did not see any comments in the "change log".

[Teken]

There were no release notes provided.


Encrypted By: Phoenix Security Solutions

[ben]

The patches since 3.12 are mostly fixing one or two bugs here and there and internal stuff to do with the small GEM revision we made (WiFi/Ethernet on-board instead of external connector).

Most of the stuff only affects a small portion of users (besides the amp display bug).

ver 3.12
- Fixed problem with ^^^RQSRTL requesting realtime status.

3.16
- Removed VA in setup page live data
- Added "Com1" and Com2 to Pri and secondary packet format label in setup page
- Made change to help prevent GEM from being stuck in web setup mode.

3.17
- Fixed problem with CHxx and CHE commands.

3.18
- Display of amps fixed in live data section of setup website.

3.19
- Fixed problem where sending SYSPKT4 would set PKT to 5 if the leading zero was not included.
- Fixed same problem as above but for PKF which is the secondary packet format.
- Fixed RQSPKT which did not work.

[Teken]

The patches since 3.12 are mostly fixing one or two bugs here and there and internal stuff to do with the small GEM revision we made (WiFi/Ethernet on-board instead of external connector).

Most of the stuff only affects a small portion of users (besides the amp display bug).

ver 3.12
- Fixed problem with ^^^RQSRTL requesting realtime status.

3.16
- Removed VA in setup page live data
- Added "Com1" and Com2 to Pri and secondary packet format label in setup page
- Made change to help prevent GEM from being stuck in web setup mode.

3.17
- Fixed problem with CHxx and CHE commands.

3.18
- Display of amps fixed in live data section of setup website.

3.19
- Fixed problem where sending SYSPKT4 would set PKT to 5 if the leading zero was not included.
- Fixed same problem as above but for PKF which is the secondary packet format.
- Fixed RQSPKT which did not work.

Ben,

Thanks for the break down for the COM firmware releases. Is there any information pertaining to the Engine updates?

[ben]

It's just stuff to do with the new revision most likely. Nothing that'll make much sense to the end user.