Surely it is not just me - this feature on occasions becomes a nightmare.
If you are setting up or diagnosing a system there are multiple things that just do not work first time.
- on many occasions when performing a \'scan for modules\' items get re-name and re-arranged- other times the scan dos not pick up the correct device number on the first pass
Its been like it for years but I just now think everybody that uses comfort just accepts it - surely t can be improved its terrible!
Can someone PLEASE just try some simple tests........
Take a working system with several UCM\'s Try adding another UCM and scan or removing no 2 UCM and scan - you will see what I mean.
I deleted UCM #3 and did a scan for all modules and it picked it up as UCM#3 again, no renumbering. It just got the default names as per normal.
I did picked up another issue that I think @Support might need to look at. My system has both Modbus and Cbus UCM\'s and they connect to \'busy\' networks, meaning I receive constant counter updates. When trying to do a Module Scan when they are connected it times out every time. When I unplug the Modbus LAN cable and the Cbus interface then the constant counter updates stop and the scan returns without any issues.
OK that good
Do you have a UCM1
We ALWAYS leave this slot spare so that an engineer can call in and plug straight in?
Also following the theme of items having to be in order what happens if you (temporarily) re-assign the UCM to 4 ?
Also have you done a update defaults on LH tab ?
Quote:Can someone PLEASE just try some simple tests........ Take a working system with several UCM\'s Try adding another UCM and scan or removing no 2 UCM and scan - you will see what I mean.
A simple test
delete UCM 2 and do a scan, the missing UCMs will remain but in red with status Not Polled. After 10 seconds Comfigurator pops up a box
[color=\"#ff0000\"]\"Possible Communications Lost or Duplicate ID for UCM/GSM ID#2. Please check the Module ID \" [/color] ie it reports the UCM #23 is a UCM/GSM in this case
Comfigurator does not remove UCMs unless you delete the UCM from Modules.
If you add the UCM #2, Comfigurator will immediately report
[color=\"#ff0000\"]
[/color][color=\"#ff0000\"]\"UCM/GSM4 ID#2 Communications Restored\"
[/color]
After a scan the UCM ID2 in Modules will now appear in Black with status \"polled\" The name and ID is unchanged
In my case UCM#1 Name was changed to UCM010 instead of UCM01. but the ID remains at 1.
Comfigurator always scans for the correct ID and displays the ID - it does not[color=\"#ff0000\"] renumber[/color] the ID
If you change the Module ID eg from 2 to 3 and rescan, then Comfigurator will identify the new module ID eg 3, and it will assign a new[color=\"#ff0000\"] Name[/color] eg UCM03.. You will lose the previous name that you assigned when it was ID2 eg Cbus, because the name was only assigned by Comfigurator and not saved in the UCM
Quote:I did picked up another issue that I think @Support might need to look at. My system has both Modbus and Cbus UCM\'s and they connect to \'busy\' networks, meaning I receive constant counter updates. When trying to do a Module Scan when they are connected it times out every time. When I unplug the Modbus LAN cable and the Cbus interface then the constant counter updates stop and the scan returns without any issues.
Thankls for the feedback.
We may be able to stop these counter and sensor reports while scanning so it does not affect the scanninbg
[user=41]Home[/user] wrote: Quote:OK that good
Do you have a UCM1
We ALWAYS leave this slot spare so that an engineer can call in and plug straight in?
Also following the theme of items having to be in order what happens if you (temporarily) re-assign the UCM to 4 ?
Also have you done a update defaults on LH tab ?
Yes, 1 through 5 populated with Wifi, Cbus2, GSM2, Eth03 and Modbus. All updates done as per Cytech recommendations. This is my Production system so would not like to mess around too much with UCM id\'s. One thing to note, if I remember that far back, my UCM\'s use hardcoded id\'s and not the software method of setting id\'s so there is no way an id can change no matter what.
By hardcoded ids, you mean the DIP switches to set the ID? Anyway you are correct scanning for modules cannot renumber the IDs. The UCM names may be changed but IDs cannot renumbered