Upgraded GEM, now shows errors.

Ask questions about the GEM here.
vespaman
Posts: 68
Joined: Sat Oct 08, 2011 2:48 am
Location: Sweden

Upgraded GEM, now shows errors.

Post by vespaman » Sat Apr 05, 2014 4:23 am

Since I had some time over, I decided to upgrade my GEM, since it had some old firmware.

I used network utility 5.8, Com 2.58 and Eng. 1.47.

Upgrade went well, the unit would go offline when in idle all the time, but the actual upgrade was ok. I have restarted both com and eng once they where updated, but still I get some errors; (Sys Status Err2, Sysinfo 00100010 Error)
Attachments
Why, and what does this mean?
Why, and what does this mean?
snap8.jpg (82.5 KiB) Viewed 2973 times
Teken
Posts: 2700
Joined: Wed Dec 15, 2010 4:09 pm
Location: The Bad Lands

Re: Upgraded GEM, now shows errors.

Post by Teken » Sat Apr 05, 2014 11:04 am

vespaman wrote:Since I had some time over, I decided to upgrade my GEM, since it had some old firmware.

I used network utility 5.8, Com 2.58 and Eng. 1.47.

Upgrade went well, the unit would go offline when in idle all the time, but the actual upgrade was ok. I have restarted both com and eng once they where updated, but still I get some errors; (Sys Status Err2, Sysinfo 00100010 Error)
Is your installation really a 3 phase @ 50 Hz? Also, do you have the GEM connected to anything else like a Dash Box, ISY-994 iZ?

Have you removed the internal battery coin cell and hard rebooted the GEM? If not please do so and then insert the battery and see what happens.

Also, please state what version of firmware you upgraded from. As there was a very specific sequence that had to be followed if you were below a very old firmware revision.
Teken . . .

My ongoing projects thread: http://www.brultech.com/community/viewt ... ?f=2&t=929
Buy me a cup of coffee: https://www.paypal.me/Teken https://gfinotify.com/ Discount Code: PC10
vespaman
Posts: 68
Joined: Sat Oct 08, 2011 2:48 am
Location: Sweden

Re: Upgraded GEM, now shows errors.

Post by vespaman » Sat Apr 05, 2014 11:54 am

Yes, 3 phase 50Hz!
Eng was 1.46, not sure about com, but not too old, not so old that I needed the special sequence.

I have it connected to a dashbox and a vera.

Haven't taken away the cell battery - I suspect I would have to redo the complete setup then, no? My GEM is fully populated with different phases/ct's and temp sensors, it is a substantial work to redo it all. Not sure I want to be the first one to test the backup/restore function... :oops:

I will do a hard reboot tomorrow morning,
Teken
Posts: 2700
Joined: Wed Dec 15, 2010 4:09 pm
Location: The Bad Lands

Re: Upgraded GEM, now shows errors.

Post by Teken » Sat Apr 05, 2014 12:02 pm

vespaman wrote:Yes, 3 phase 50Hz!
Eng was 1.46, not sure about com, but not too old, not so old that I needed the special sequence.

I have it connected to a dashbox and a vera.

Haven't taken away the cell battery - I suspect I would have to redo the complete setup then, no? My GEM is fully populated with different phases/ct's and temp sensors, it is a substantial work to redo it all. Not sure I want to be the first one to test the backup/restore function... :oops:

I will do a hard reboot tomorrow morning,
1. You will not lose any of your settings when you remove the coin cell.

2. Your COM 1 Flow shows disabled. Did you turn this off before?

3. Is the Dash Box / Vera still receiving packets from the GEM? Please login to the Dash Box and post up the Raw Log file. Streaming data should be coming from the GEM to the DB.

4. Also did you in fact change the GEM Network Tool back to Normal from firmware load? The baud rate should be at 115200 baud.
Teken . . .

My ongoing projects thread: http://www.brultech.com/community/viewt ... ?f=2&t=929
Buy me a cup of coffee: https://www.paypal.me/Teken https://gfinotify.com/ Discount Code: PC10
vespaman
Posts: 68
Joined: Sat Oct 08, 2011 2:48 am
Location: Sweden

Re: Upgraded GEM, now shows errors.

Post by vespaman » Sat Apr 05, 2014 12:49 pm

1. OK, so this is the clock battery? The clock was off, after fw update. But with my past clock issues, I did not reflect on that, I just set it on routine.
2. Never used Com1, It never worked, so I have Dashbox on Com2. Vera over ethernet.
3. Yes, both are.
4. Changed back to 115200, thats all. (The only thing I changed during fw update, was to 19200 as documented in the upgrade guide).

Cheers,
Micael


Edit: Actually, I think that it was the Com1 on the Dashbox that was faulty, not the GEM, when I come to think about it. ... Enabled the hand shaking, but still error is the same.
Teken
Posts: 2700
Joined: Wed Dec 15, 2010 4:09 pm
Location: The Bad Lands

Re: Upgraded GEM, now shows errors.

Post by Teken » Sat Apr 05, 2014 6:58 pm

vespaman wrote:1. OK, so this is the clock battery? The clock was off, after fw update. But with my past clock issues, I did not reflect on that, I just set it on routine.
2. Never used Com1, It never worked, so I have Dashbox on Com2. Vera over ethernet.
3. Yes, both are.
4. Changed back to 115200, thats all. (The only thing I changed during fw update, was to 19200 as documented in the upgrade guide).

Cheers,
Micael


Edit: Actually, I think that it was the Com1 on the Dashbox that was faulty, not the GEM, when I come to think about it. ... Enabled the hand shaking, but still error is the same.
Hello Micael,

I would first use the back up feature in the GEM Network Utility Tool under advanced and save the GEM settings. Once done I would remove the coin cell in the GEM and do a hard reboot. After the GEM comes back on line.

Insert the battery back in and see if the error message goes away.
Teken . . .

My ongoing projects thread: http://www.brultech.com/community/viewt ... ?f=2&t=929
Buy me a cup of coffee: https://www.paypal.me/Teken https://gfinotify.com/ Discount Code: PC10
ben
Site Admin
Posts: 4254
Joined: Fri Jun 04, 2010 9:39 am

Re: Upgraded GEM, now shows errors.

Post by ben » Mon Apr 07, 2014 11:16 am

vespaman wrote:1. OK, so this is the clock battery? The clock was off, after fw update. But with my past clock issues, I did not reflect on that, I just set it on routine.
2. Never used Com1, It never worked, so I have Dashbox on Com2. Vera over ethernet.
3. Yes, both are.
4. Changed back to 115200, thats all. (The only thing I changed during fw update, was to 19200 as documented in the upgrade guide).

Cheers,
Micael


Edit: Actually, I think that it was the Com1 on the Dashbox that was faulty, not the GEM, when I come to think about it. ... Enabled the hand shaking, but still error is the same.
There's a flag in the newer firmware that has to be reset, and is only reset upon removing the battery and cycling power. That should clear up the error.

COM1 on the DashBox shouldn't be faulty, we test them both before sending them out. The newer DashBox firmware will show you COM statuses, if it says "Unknown device" it's likely a problem with non-matching baudrates.

Ben
Ben
Brultech Research Inc.
E: ben(at)brultech.com
vespaman
Posts: 68
Joined: Sat Oct 08, 2011 2:48 am
Location: Sweden

Re: Upgraded GEM, now shows errors.

Post by vespaman » Sun Aug 06, 2017 4:20 am

Yes, this is an old thread, I know... :D

But, it may have some relevance to a new problem..

As you may remember from other threads, I have upgraded my system with a second GEM, and I am having problem with the logging in Dashbox. The problem is that GEM number two, the new one, only logs for some time, and then it stops, and Dashbox reports that no packets are coming.
If I then enter the web setup of the the GEM through dashbox port 8001, I get the settings page, but I have to re-enter setup mode very often, since it is dropped (But I have this issue also on my original GEM, so I'm not sure it is related). If I quit, Dashbox sometimes starts logging again for a while.
So:- this is why I searched and reopened this old thread.

I never changed the original GEM from com2, since it worked, and now adding the second GEM, I of course had to plug it into com1.

My suspicion is that the COM1 port is actually bad, as per my previous observations in this thread. Or could this be a software problem with dual GEM's?
Should, or should I not have hardware handshaking enabled on the GEM's? It does not seem to make a difference, but best get it right.

The GEM continues to log over ethernet to my openhab/btmon installation, so GEM is alright from this aspect.
Teken
Posts: 2700
Joined: Wed Dec 15, 2010 4:09 pm
Location: The Bad Lands

Re: Upgraded GEM, now shows errors.

Post by Teken » Sun Aug 06, 2017 8:45 am

Hello Micael,

If you're seeing a loss of data packets called out by the Dash Box (DB) which restores itself in about 2 minutes this is a software bug that the team is working to resolve. I've been seeing this issue on my *Silver* DB for quite some time and Ben is working toward a solution.

You may also see other services lose connectivity from time to time like ISY, SEG, IFTTT, etc.
Teken . . .

My ongoing projects thread: http://www.brultech.com/community/viewt ... ?f=2&t=929
Buy me a cup of coffee: https://www.paypal.me/Teken https://gfinotify.com/ Discount Code: PC10
vespaman
Posts: 68
Joined: Sat Oct 08, 2011 2:48 am
Location: Sweden

Re: Upgraded GEM, now shows errors.

Post by vespaman » Sun Aug 06, 2017 10:07 am

Hi Teken,

No, if I understand you correctly this is not the case. The problem is that logging to Dashbox only works sporadically.
E.g. pic below, second unit has stopped.
Attachments
Screenshot_20170806_170547.png
Screenshot_20170806_170547.png (122.09 KiB) Viewed 2516 times
Post Reply