Issue
How to create i2xxx and b3xxx controllers from a CSV dump file.
Environment
Continuum
i2xxx Controllers
b3xxx Controllers
Cause
In this scenario they wanted to create the beginning of a site database from CSV dump files before deploying on site.
Resolution
It seems that when creating an i2 or b3 object, the path is also required when defining the comm port. Make sure to add the path to the Port field and this should allow the controller object to be created. See the original CSV I exported below, how it was modified, and then imported back in successfully.
Original Export to CSV
InfinityInfinetCtlr
Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType
i2_850,32,Comm1,Network1\ACX11_10th,11111,i2_850,i2920
Modified Import CSV
InfinityInfinetCtlr
Name,InfinetId,Port,DeviceId,SerialNum,Alias,CntrlType
i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920,i2920
Now, this import does complain about the CntrlType in the distribution Properties window but does create the controller and sets the type correctly. If you don't want any errors you can remove the CntrType attribute and the controller object will still be created but will default to a 240 controller. See below.
Import CSV without CntrlType
InfinityInfinetCtlr
Name,InfinetId,Port,DeviceId,SerialNum,Alias
i2_920,32,Network1\ACX11_10th\Comm1,Network1\ACX11_10th,11111,i2_920
This can then be changed to whatever controller you require through the controller Device object dialog.
