Velbus died?

[steefdebruijn]

Hi,

Tried to write some data to velbus EEPROM and received errors doing so. Scanning all modules indicates Velbus is not found. Led is green, sometimes all D2,3,4 leds blink red.

Is it broke?

Steef

[ident]

Does the D9 red led remain off? If so, this looks like a problem with incorrect UCM/Velbus ID
Check the ID shunts, set to ID=2 (or 3 if ID 2 is taken up), Scan again and see if Comfigurator can find the module. Then do write to Comfort

If the UCM/Velbus is polled both D9 and D10  will blink

[steefdebruijn]

Hi,

I did not change ID settings but double-checked anyway. It is correctly set at ID 4. It has worked fine for the past couple of weeks but stopped responding after trying to write configuration to EEPROM. All other UCM\'s working fine (ZWave, Ethernet, GSM)

LED indicators:
D1 (green) is permanent ON, only flickers OFF once for a quarter of a second every ten seconds or so right after the three red\'s go OFF (see below)
D2,3,4 (red) are permanently OFF, only flash for a second every ten seconds or so.
D9 (red) is permanently OFF
D10 (green) is more or less permanently ON (somewhat flickering)
D11 (green) is OFF, but sometimes gives a very short flicker (less than a quarter of a second)
D12 (red) is OFF

Did it fry on EEPROM write?

Steef

[steefdebruijn]

Additional info:

Velbus firmware sticker is 6.011, upgraded to 7.006 couple of weeks ago.

Just reloaded firmware through UCM Firmware programming cable. Went OK but after reconnecting the UCM it is still not found by Comfort.

Steef

[ident]

I suspect something in the eeprom is causing the UCM/Velbus to reset itself every 10 seconds.
Try removing the eeprom from U2(after power off)

Alsouse another eeprom in U2 if possible

[steefdebruijn]

Additional info

Pulled the EEPROM from the board and reconnected the UCM. D4 is now flashing (for the missing EEPROM of course) but the Confort scan now says \'not polled\'. That seems to me better than \'not found\'.

After writing config to comfort rescan states Velbus UCM is polled. Version=7.006, latest=6.011.

After reinserting the EEPROM and reconnecting the UCM, it is back to the faulty behavior stated above.

Steef

[ident]

The eeprom may have gone faulty, but write to eeprom should not have caused this as that only erases data and writes into the eeprom

Try another eeprom eg the \"spare \" eeprom in the UCM/USB or ethernet in U2 used for backup, see if that fixes the problem
You can buy another eeprom from the distributor or elsewhere (24C256)

[steefdebruijn]

Hi

Thx for the info. Found an online shop selling the 24LC256 I/P.

Can i just pull the EEPROM from the Eth UCM? I have only one installed in the U2 socket. (U3 is empty)

Steef

[ident]

yes you can use the U2 from UCM for testing to verify that it works in the Velbus

[steefdebruijn]

Inserted a brand new EEPROM and the thingie was back to life. Earlier programmed responses to write to velbus (switch lamp) worked OK.

But... Changing the Velbus to Comfort tab and writing to EEPROM went OK but the thing died again on me. Exactly the same symptoms described earlier.

So the EEPROM write does some serious harm in some way.

Any ideas?

Steef