B&B Electronics I3A12X_20B05-SOHF - Manual User Manual
Page 22

Basic Operation
then switched to the other at a later time. The result will be a mismatch in the network
ID settings between the Configurator project and the
i
3
(it is trying to communicate
with ID 253 when the device is set at 1, or communicate with ID 1 when the device is
set to 253).
Also, the comms engine of the
i
3
Configurator constantly runs in the background as
soon as the software is started. The first indicator that Comms are established is that
the ‘Traffic Lights’
will show the status of the connected
i
3
, as one of the
buttons will appear depressed.
If this does not occur then the comms settings can be verified as shown below. This
shows an Ethernet connection. Care must be taken if using a USB to Serial Adapter
that the Com port assigned to the adapters matches the one selected through these
options.
At the bottom of the Configurator screen we can see the status bar. This is showing
that we are Locally connected to the
i
3
of Network ID 11. This is the device that we
are physically connected to. But, it is showing the Target ID of 1. So, despite being
connected to ID 11; we are actually configuring/debugging/monitoring the
i
3
with an
ID of 1. It is showing us that this is an i3B model with CAN Net, but no I/O
configuration as yet (/xxxxx).
© IMO Precision Controls ltd.
23