Weird - Bridge firmware a little confused

Bridge can't decide whether it is firmware 4.4 or 4.6!

From two different and consecutive Toolkit (version 1.11.2) scans. Note the time stamps...

Code:

20101116-230359 753 //IRIS/254 d81a4190-d385-102d-8aea-ed419f793b1a Net Sync: address=253 type=BRIDGE2N version=4.4.00 serial=100499.3228 catalog=5500NB
20101116-230457 753 //IRIS/254 d81a4190-d385-102d-8aea-ed419f793b1a Net Sync: address=253 type=BRIDGE2N version=4.6.00 serial=100499.3228 catalog=5500NB

When it scans in toolkit as a 4.4, immediately after the scan if the unit's dialog is opened, the firmware fixes itself to 4.6. If the database unit's dialog is opened, a message is displayed asking whether to change the database firmware to 4.4.

Can't work this out.

This is the near side of the bridge, and only it seems to be affected. The far side scans reliably as 4.6.

The only recent major change to the network is a change of the bridge from an older version 4.4 bridge to a newer 4.6 bridge. Not sure if that is related, but sounds suss. Toolkit and C-Gate has been restarted many times. The only thing I have not tried is to totally power down the system and restart. It's dark, so I might try that tomorrow.

Another change today was weirdness with a Thermostat's messaging that was resolved by disconnecting and reconnecting it (thanks Newman).

Aside from the version report, everything appears to be working brilliantly.

Here's a partial log from an initial toolkit startup showing the near and far sides of the bridge reporting different firmware...

Code:

20101116-231711 753 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 Net Sync: address=60 type=KEYBL5 version=2.1.00 serial=100400.2760 catalog=5085DL
20101116-231712 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=21 type=SENPILL version=2.0.00 serial=100406.1876 catalog=5753PEIRL
20101116-231712 753 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 Net Sync: address=61 type=KEYB4 version=2.2.00 serial=100566.966 catalog=5084NL
20101116-231713 753 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 Net Sync: address=253 [B]type=BRIDGE2N version=4.4.00[/B] serial=100499.3228 catalog=5500NB
20101116-231713 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=22 type=SENPIRSS version=1.2.67 serial=100057.1080 catalog=5751
20101116-231713 730 //IRIS/254/56/99 4f30c6f0-d3a9-102d-b9a1-ae543e78e836 new level=20 sourceunit=2 ramptime=0
20101116-231713 730 //IRIS/254/56/98 4f309fe0-d3a9-102d-b9a0-ae543e78e836 new level=0 sourceunit=2 ramptime=0
20101116-231714 756 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 SyncState=bridge
20101116-231714 753 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 Net Sync: synchronising bridges
20101116-231714 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=23 type=SENPIROA version=1.2.67 serial=100333.475 catalog=5750WPL
20101116-231715 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=24 type=SENPIROA version=1.2.67 serial=100532.2596 catalog=5750WPL
20101116-231716 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=30 type=SENTEMP version=1.00 serial={none} catalog=5031TS
20101116-231716 756 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 SyncState=units
20101116-231716 753 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 Net Sync: synchronizing unit 1 of 30 at address 0
20101116-231716 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=254 [B]type=BRIDGE2F version=4.6.00[/B] serial=100499.3229 catalog=5500NB
20101116-231716 753 //IRIS/254 4f1e7770-d3a9-102d-b929-ae543e78e836 Net Sync: address 0 type PCLOCAL4 version 4.6.00 catalog 5500PC

 

When you open the network UI for the bridge (ignore the DB view for the moment) what firmware version number shows in Toolkit? Do this for both sides of the bridge and report back.

 

At the far side of the bridge, UI says 4.6 for the unit (not database). Opening the unit configuration dialog also reports 4.6.

At the near side of the bridge, here's what I see...

Step 1 - View from the main units screen:



Step 2 - Things change when I open the unit configuration dialog (note how the firmware number changes in the main screen behind the dialog when opened.

 

sounds like a database issue.

Bridge firmware version is stored in ROM, and can't be changed.
The only way this could happen in a bridge is if one bit of ROM (there is only one bit difference between 4.4 and 4.6) was intermittent, but chances that only one bit out of a total of 131072 bits is intermittent is a bit slim.
Just about any other bit errors in ROM would result in non-functional bridge firmware.

 

When C-Gate does a Net Sync, and we see...

Code:

20101117-110011 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: Units at: 1, 2, 3, 4, 10, 11, 12, 13, 14, 15, 19, 20, 21, 22, 23, 24, 30, 254
20101117-110011 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: Unit errors at:
20101117-110012 756 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 SyncState=tvs
20101117-110013 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=1 type=DIMDN8 version=1.6.00 serial=100347.2823 catalog=L5508D1A
(snip)
20101117-110029 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=30 type=SENTEMP version=1.00 serial={none} catalog=5031TS
20101117-110029 753 //IRIS/253 4f50ab00-d3a9-102d-ba72-ae543e78e836 Net Sync: address=254 type=BRIDGE2F version=4.6.00 serial=100499.3229 catalog=5500NB

Are the firmware versions being read from the database, or from the unit? If it's from the unit directly, then this is where I also see version 4.4 being reported for the near side of the bridge (most often, but occasionally it is 4.6). If the database is involved, then maybe there is some form of corruption introduced when I changed from the old version 4.4 bridge. If that is a possibility, then I guess I could try and completely remove the bridge from the database and re-add by copying configuration from the physical unit. Won't do that yet in case someone wants some of the install files for any reason....

 

I understand the logic of it all, but it's falling down in my case...

Initial scan shows phantom, but then subsequent scans shown in the C-Gate log do not update this phantom to 4.6. It stays as 4.4 for the long haul, scan after scan after scan, and Ocassionally (very ocasionally) scans as 4.6. (these are not toolkit initiated scans - when I do that, it may scan as 4.6, or may not...)

But when opening the toolkit physical unit dialog it will instantly set itself to 4.6.

Looking at my C-Gate log this morning, the unit appears to be doing its periodic scans as version 4.4 on the near side. Once it has done that, when I open the database unit dialog in Toolkit for the near side, I get prompted that the firmware is a mis-match, and would I like to update the database firware to the physical unit firmware. Sounds like a bug in Toolkit, or a bug in the unit itself.

Happens quite often, otherwise I wouldn't have posted.

Cheers,
S.

 

To add a little more information, Daniel.

I changed out the current version 4.6 bridge to another, identical 4.6 bridge, and the same behaviour is being observed. So highly likely this is a software and not a firmware issue. Unless all 4.6 bridges work this way .

I also completely removed all database and records for the bridges afterwards, and re-added these from the unit programming. Restarted Toolkit/C-Gate, and same result. Far is 4.6, near is 4.4 on initial scan in C-Gate. A subsequent scan initiated from Toolkit came up near side 4.6. The second scan immediately after in Toolkit came up near side 4.4. The third scan came up near side 4.6. And a fourth scan immediately after came up near side 4.4. Fifth 4.4. Sixth 4.4. Then I got bored...

Let me know if you want me to collect any more information. I will have the above sequence of events recorded in a level 7 log file.

Cheers,
S.

 

It's nothing to do with the bridge itself, it's the way Toolkit/C-Gate are handling the version numbers.