Process Control System - QUADLOG

Qualdlog Controller Firmware Update

Erstellt von truemanrst am 19.08.2008 21:35 (3 Antworten)

  19.08.2008, 21:35

truemanrst Beigetreten am: 19.08.2008 Letzter Besuch: 18.09.2008 Beiträge: 2 Bewertung:  (0)	(0)  I recently upgraded a CCM+ controller to version 4.5.4 via the appropriate export / import operation via 4Mation.  The controller was initally setup as node 0 in Rack 9 Slot 1.  After the re-initilzation was completed the node assignment changed from "0" to "12".  Everything runs properly however it is now stuck as node 12.  Is there an easy way to change it back so it comes up as node 0 ?
	Top

  20.08.2008, 04:21

soikel Beigetreten am: 23.05.2006 Letzter Besuch: 13.06.2013 Beiträge: 13 Bewertung:  (4)

(2)  Controllers get their node address from eith an MBX module or a PC attached directly to the local mbus (via an mbi card).  If you have an MBX there is a node switch behind the front bezel of the module. All controllers on the same local mbus as the MBX will use the node address of the MBX. But I suspect in your case it was from a PC that had it's mbi set to N12.  Any PC on the local mbus has the potential to set the controller's node address, and the user has no real control over which PC does it.  Best thing to do is to be sure ALL PC's that have an mbi card on the local mbus have their node addr set to the desired node addr of the controller.  The setting on PC's can be found in the Control panel APACS applet.  Also note there is a node switch setting on the controller's transition board that must be set properly.  The switch setting will inc/dec the base node setting of the controiller, depending on whether the base setting is even or odd. Also if you have multiple PC's on a local mbus then it is recommended to assign all the same node, but space their RACK adresses out by two.  Example" PC1=N0R1S11, PC2=N0R3S11, PC3 N0R5S11, etc. Technical Support can steer you to the manuals that cover the xtion bd setting, and they have a write up that explains the insight behind the rack spacing. All that being said - it will take a reboot for your controller to obtain a new node address.

Top

  20.08.2008, 16:49

truemanrst Beigetreten am: 19.08.2008 Letzter Besuch: 18.09.2008 Beiträge: 2 Bewertung:  (0)

(0)  Thanks for the information regarding this issue, very helpful.  I do have a couple of observations to add in case anyone else runs across this problem.  While I was able to reset the computer to node 0 it was not straight forward.  First attempt via the control panel (APACS) resulted in a hung computer.  So I thought that some running services were interferring with the reconfiguration.  I stopped all relavent services and tried again.  Same result, a hung computer.  The only way that I could resolve the node addressing was to completely removed the APACS software and re-install it all again.  After rebooting the computer and confirming that the node assignment was set to zero I powered up the ModuleRac.  However, the controllers still came up as node 12.  Only after pulling the controllers out, removing the batteries, reinserting them did they show up on the module tree as node 0.  Bottom line, backup your online configuration if needed before attempting a node change.

Top

  18.09.2008, 05:11

Amerbaig Beigetreten am: 08.07.2008 Letzter Besuch: 18.03.2012 Beiträge: 12 Bewertung:  (2)

(0)  Hello All, To avoid that(Hung PC When NRS Addr. is Changed) all you have to do is the folowing 1- Right Click My Computer 2-Mange 3-Device Manger 4-Expand Network Adapter 5- Select MBI Card Adapter 6- Right Click on MBI Adapter, Disable it 7- Now Double Click the MBI Adapter, Change the NRS Address, Apply 8-Enable the MBI Adapter 9-Verify the Address Change by Double-Clicking, Then Advanced, Look into NRS values Hope this helps you out in future

Top