Dashbox issues

[tmrobert8]

ben,

Just for your information - this weekend I had a short (<30 second) power outage and one of the gems fell offline with the dashbox (exactly as described in this thread).

The gem in question showed a primary/secondary of 4/disabled and the dashbox saw it was online but no packets. Followed the recommendations in this thread and this is how I fixed it..
I changed it to 5/5 - still no packets
Changed it to 5/dsiabled - got packets
Changed it to 4/disabled - still got packets

Seems like the gem or the dashbox got confused after the power outage. I had to change up the formats for them to sync again..

[ben]

ben,

Just for your information - this weekend I had a short (<30 second) power outage and one of the gems fell offline with the dashbox (exactly as described in this thread).

The gem in question showed a primary/secondary of 4/disabled and the dashbox saw it was online but no packets. Followed the recommendations in this thread and this is how I fixed it..
I changed it to 5/5 - still no packets
Changed it to 5/dsiabled - got packets
Changed it to 4/disabled - still got packets

Seems like the gem or the dashbox got confused after the power outage. I had to change up the formats for them to sync again..

What DashBox F/W are you on? Check Settings->System->Change Baudrates and see if it says Unknown Device.

[tmrobert8]

4.2.4c15d4e
Both say 115200 and detected.

The other gem did the same thing last night - doing the above got the packets flowing again..

[ben]

4.2.4c15d4e
Both say 115200 and detected.

The other gem did the same thing last night - doing the above got the packets flowing again..

Load up https://www.brultech.com/software/files ... 2_4c16.img on the DashBox.

What COM F/W is on the GEMs?

[tmrobert8]

Updated and both com F/W are 5.39

[tmrobert8]

BTW - happened again sometime last night (no power outage this time). Dashbox couldn't see packets from 019 - I did the from 4/disabled->5/5->5/disabled->4/disabled trick and it came back online

[ben]

BTW - happened again sometime last night (no power outage this time). Dashbox couldn't see packets from 019 - I did the from 4/disabled->5/5->5/disabled->4/disabled trick and it came back online

I somewhat remember a weird version of 5.39 that could cause issues, let's try updating the COM F/W on the GEM.

- Download/install the GEM Network Utility. https://brultech.com/software/files/dow ... _8.01_.exe
- Download COM 5.39. https://brultech.com/software/files/getsoft/3/1
- Unplug the STS from the DashBox so no random information gets sent while programming.
- Connect to 019 via your Ethernet module.
- Click Get GEM Info, it'll ensure you can talk and send you to the Firmware tab.
- Click Select Firmware, select 5.39 above.
- Click Start.

If you get stuck email (ben(at)brultech.com) me immediately. I only check here a few times a day.

[tmrobert8]

Hate to say it - but its happening again. This time it's the 018 one and my little trick (above) doesn't seem to work - the dashbox just reports no packets. The 018 is on 5.39, I've double checked the baud rates, etc.

The weird thing is that if I go to system->logs on dashbox - I can definitely see the packets from 018 (see below - that's definitely from a few moments ago) but the main energy monitors window still says no packets...

Time OK, logging packet
01121018 Processing record..
01121018 Processed Net..
01121018 Processed Channels..
01121018 Processed Temp..
01121018 Processed Pulse..
01121018 Processed Volts..
01121018 Granular Updated..
01121018 Granular Finished..


Packet logging... SN=01121018&SC=13763209&V=1223&c1=827816185,0,0.2&c2=18221524,0,0.2&c3=0,0,0.22&c4=1960960067,0,1.64&c5=261406737,0,0.2&c6=711527343,0,0.22&c7=1,0,0.22&c8=780489764,0,0.32&c9=5468159599,0,1.54&c10=1144176745,0,2.34&c11=563,0,0.2&c12=1468314616,0,0.26&c13=182068302,0,0.22&c14=2552922447,0,1.14&c15=82397,0,0.2&c16=45522504,0,0.2&c17=7507795,0,0.18&c18=3274945076,0,0.28&c19=1228091921,0,1.18&c20=356972953,0,0.24&c21=1074887382,0,0.2&c22=5222003161,0,0.42&c23=109773294,0,0.28&c24=1385899474,0,0.64&c25=2285726061,0,0.18&c26=1,0,0.22&c27=1918530430,0,0.22&c28=0,0,0.22&c29=0,0,0.22&c30=1,0,0.22&c31=6028861060,0,2.2&c32=23059548176,0,5.66&PL=0,0,0,0&T=4096.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0&Resp=&D=2023-7-5&TI=8:30:53&com=1
Done logging 2023-07-05 08:26:46 AM at 2023-07-05 08:26:47 AM

[tmrobert8]

FYI - just updated dashbox to 4.2.4c17a and everything is online again - no idea...

[tmrobert8]

Ben

Been awhile but I still have one or the other dropping out occasionally. Up to now, I've been able to resolve by playing around with packet options until it goes green on both. However, now I can't seem to get #18 to come up at all in dashbox. I've upgraded to the latest dashbox (18d), double checked baud rates and have played around with formats - #18 refuses to be processed.

The system log [see below] still shows packets being received and logged by dashbox - but the rest of it doesn't see anything (status shows no packets). Copy from the log (can't tell if the packet is valid or not):

Time OK, logging packet
01121018 Processing record..
01121018 Processed Net..
01121018 Processed Channels..
01121018 Processed Temp..
01121018 Processed Pulse..
01121018 Processed Volts..
01121018 Granular Updated..
01121018 Granular Finished..


Packet logging... SN=01121018&SC=602372&V=1235&c1=1438791454,0,0.0&c2=23929247,0,0.0&c3=10,0,0.0&c4=3466544076,0,1.64&c5=453038731,0,0.0&c6=1000931955,0,0.22&c7=12,0,0.0&c8=1269045289,0,0.18&c9=8376116325,0,1.22&c10=2481412109,0,0.22&c11=15515,0,0.0&c12=2257824544,0,0.82&c13=304947592,0,0.08&c14=4150800441,0,0.48&c15=150389,0,0.0&c16=92295943,0,0.0&c17=17590880,0,0.0&c18=5929175274,0,0.18&c19=2064928992,0,1.22&c20=603108705,0,0.12&c21=1840335716,0,1.06&c22=8934020820,0,0.36&c23=188031096,0,0.32&c24=2340067332,0,0.28&c25=5223857296,0,0.0&c26=565199195,0,0.4&c27=1918530438,0,0.0&c28=0,0,0.0&c29=0,0,0.0&c30=1,0,0.0&c31=12185337095,0,2.56&c32=41859125440,0,3.42&PL=0,0,0,0&T=4096.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0&Resp=&D=20208-0-0&TI=0:0:0&com=1
Done logging 2024-02-26 09:18:46 AM at 2024-02-26 09:18:46 AM