I have replaced faulty modules before, many years ago, and did not have any problems.
For some reason today I just seem to be messing it up so I would like to check how this should be done. Clearly I am making a stupid mistake somewhere…
Background: My loft is very warm in recent heatwaves. I have one VMBDMIR dimmer (out of 77 VMBDMIR altogether) which has been failing, just temporarily, on the hottest afternoons. SO, I thought I would exchange it for a spare to see if that makes any difference.
Step 1: I set the spare module in my test-rig to ID 0xFF and removed it.. this is to be my replacement “known-good” module.
Step 2: I removed module with ID 0x53 from the bus in my loft.
Step 3: I replaced it with the “known good” module
Step 4: I ran velbuslink, loaded my project, connected, then did a scan.
Step 45: It has detected the new module without ID set. So I set that ID to 0x53. and SCAN again.
OH… now it shows TWO modules with ID 0x53, both with a red ‘!’ next to it.
One of these is missing (and has all my actions attached), and the new module is now shown also with ID 0x53 and no actions yet.
If I do right-click “Remove Module” on the now-missing one then I lose all of it’s actions.
Velbuslink does not seem to know that I want to keep the actions to program to the new module.
What am I doing wrong? Short of re-doing all the actions for this new module (which would be very tedious and prone to mistakes), how can I get the new module to inherit the ID and all the actions of the one that I have removed from the bus?
