Skip to content

Import Modbus monitoring configurations into a Boss’nX component

Boss’nXAdministratorInstaller

Boss’nX on a computer: Import from monitoring window of the component editor

The Import from monitoring window of the Boss’nX component editor reuses Modbus configurations already prepared in monitoring and creates read-only datapoints in one go: address, function code, type, scale factor and swaps are copied. It does not discover the device’s registers.

This path is for an administrator or installer, on a computer. For a command, use the manual configuration of a Modbus datapoint.

  • Your role has Manage components and you are working in the relevant supervision.
  • The Modbus gateway is declared and attached to the general gateway intended for the component.
  • Configurations exist for this Modbus gateway in Data logging → Modbus registers, where you can also create or correct the ones the import offers.
  1. Open Components in your bar or through Menu → Components, then the Edit component pencil, or Add component. See the common form.
  2. Check the general Gateway intended for the component. The import keeps the Modbus gateways attached to it, then their monitoring configurations. Do not change the gateway of an existing component without checking its other datapoints.
  3. Under the datapoints, choose Import → Modbus, accompanied by monitoring. The Import from monitoring window opens; wait for Loading configurations… to finish.
  1. Find the Modbus gateway you want in the groups. Check its name, address and port, then Name, Address, Function code, Type and Unit ID on the rows.
  2. If needed, filter the list with Search by name or address….
  3. Check the configurations to reuse. Select all selects only the visible and allowed rows.
  4. Review the total counter: choices already made stay selected when you change or clear the search.
IndicationMeaning and next step
Not importableThe function code is a write code; it cannot be reused as a feedback in this import. Read codes 1 to 4 can be imported. For a command, configure the datapoint manually.
Already used — …A datapoint of the component already uses this combination of Modbus gateway, Unit ID, function code and address. The row is unavailable; check the datapoint indicated before creating another use.

The selection is limited to 250 configurations per import. If you can no longer check a row that is neither used nor not importable, check the number selected, then uncheck rows or proceed in several imports.

  1. Click Import N points, or Import 1 point. The datapoints appear in the form. Their Label reuses the name of each configuration; Feedback is enabled, Cmd and Alarm are not.
  2. Check the Modbus gateway, Unit ID, the register, the read code, the type, the scale factor and the swaps that were carried over. The length of the datapoint’s value is determined by its Data type.
  3. Complete the displayed unit, the polling, the presentation and the tags according to your needs. The import does not automatically enable Save to history. Follow the Modbus datapoint settings.
  4. Leave the last field, then click Create or Save. The Import button does not save the component.

To back out: Cancel or the cross closes the window without adding the selection. After adding to the form, remove a datapoint added by mistake with its trash can before saving. Back discards the component’s pending changes; it does not cancel a save already made.

Each time the window is reopened, the list is reloaded and the selection starts again from zero. Datapoints already added stay in the form: check them before selecting the same configurations again.

  • After returning to the original page, reopen the component and check the settings that were kept.
  • To test a reading and interpret its result, see Modbus troubleshooting.
  • The imported datapoint is a copy of the settings at the time of the import: a later change to the monitoring configuration does not update it automatically. If the installation’s settings change, review and correct the relevant datapoint.
Message or situationWhat to do
Select a gateway firstChoose the general Gateway intended for the component. The Modbus gateway choice of an individual datapoint does not define the context of this import.
No Modbus gateway on this gatewayCheck the declared Modbus gateways and their association, as described in declare a Modbus gateway. Do not add a duplicate just to make the menu accessible.
No monitoring configuration on the Modbus gateways of this gateway.Monitoring configurations must be prepared for the gateways concerned. The window offers a link to create configurations: finish or discard your pending changes before leaving the form.
The list disappears after a searchClear the filter text and check the gateway groups: the search only hides the rows that do not match.
Could not load the monitoring list.Use Retry. A loading failure is different from an empty list: check your connection and the supervision. Do not change the registers to get around this message.
Uncertain save after Create or SaveFollow the common form before trying again.

Write to support@can-nx.com if Could not load the monitoring list. persists, or if you do not know how to prepare the right monitoring configuration. Give the component, the gateway and the tests already done.

French labels: Composants, Menu, Passerelle, Import → Modbus monitoring, Import depuis le monitoring, Rechercher par nom ou adresse…, Tout sélectionner, Non importable, Déjà utilisé — …, Importer N points, Annuler, Re.Etat, Créer / Enregistrer / Retour, Impossible de charger la liste du monitoring., Réessayer, Aucune configuration monitoring sur les passerelles de cette gateway.