Duplicating FP Resource Comm

[Niel Craig]

I have configured a set of FP modules (FP1600, 1 x FP-DI-330, 4 x FP-RLY-420, 1 x FP-RTD-122, 1 x FP-AO-200, 1 x FP-TC-120) - enabled watchdogs, renamed all the channels and modules, etc, etc and need to set up another 5 identical sets of modules - only difference being a different resource name and IP address.

I have duplicated the comm resource, renamed it and changed the IP address and can communicate with the other FP devices, however I've noticed that while the comm resource has a new name, all the modules under the new comm resource still have the original comm resource name associated with them. Is this correct or have I missed something. Is it possible/necessary to have this the same as the comm resource the module is under?


Thanks,

Niel.

[Aaron_G]

Niel,

This is a cosmetic issue with duplicating resources/items in FieldPoint Explorer. It does not negatively effect the functionality in any way. FieldPoint R&D is aware of it and will address it in a future release.

As a side note, there is an additional step you must take to download the configuration into the network modules when you duplicate a configuration. For each bank (other than the first which was already configured), you must right-click on each I/O module and choose Edit This Device, then you should click on Channel Configuration, at this point a dialog box should appear letting you know that the current configuration of the module and the file (IAK) configuration are not the same. Choose the File configuration in order to download the in
formation into the network module.

Regards,
Aaron

[Niel Craig]

Aaron, Steve,

Thanks for your responses. That clears up my question. I had noticed the flag regarding file and module configs while working on my problem and assumed that the file cfg was the correct choice but hadn't twigged that it had to be done for all the modules. So thanks for that pointer also.

Best regards,

Niel.

[steven@ni]

Niel,

This is a known issue with the current version of Fieldpoint Explorer. This issue is currently being addressed and should be fixed in a future version of the fieldpoint configuration utility.

For your purposes, you may have to go in and configure each duplicate bank manually. I apologize for the inconvenience that this may cause, but please know that we are aware of this issue and are trying to resolve it.