Need help? FAQ!

Yes, MAPs uses TCP and UDP so you need to allow for this traffic, if you need to do some port forwarding you can configure it in maps on the connection tab, by default MAPs uses port 23 and the gateway would remain in port 23.

The BACnet Client is normally associated with the BMS or central system as it would normally start most of the communication transactions, and the BACnet servers the devices out on the field providing the data and points for control, for example our AC gateways would be a BACnet server providing all the information about the AC and awaiting for the control messages of the Client.

For a particular devices on the PIC statements or BTL certification you can see this on the BIBBs (Bacnet interoperabilty Building Blocks) that are used for a device if most of them are end in "A" are generally Clients(the user of data) or "B" is generally the Server (provider of data). For example, a device the following BIBBS would be a server.

BIBBs Supported

Please note that you would need a client and one or multiple servers in an installation for a BACnet system to work, 2 servers on its own would not communicate to each other, the same would happen with 2 clients. If you have by mistake selected the wrong protocol translator gateway please contact us through our support portal for advis.

For the Modbus master and servers to correctly communicate you need to pair the correct registers with the appropriate function makes sure that they are set as per the following guidelines

Different Modbus clients (Masters) would support some or all, the functions are:

1 - Read coils.

2 - Read discrete inputs.

3 - Read holding registers.

4 - Read input registers.

5 - Write single coil.

6 - Write single register.

15 - Write multiple coils.

16 - Write multiple registers.

1. Make sure AC unit is compatible, for 1 to 1 interfaces check here.
2. Check for Errors on the AC unit itself.
3. Check communication errors signals for feedback on status of the communication or the AC itself.

If you are connecting to the AC trough the remote controller bus then also check:

1. Make sure that Remote Control is compatible.
2. Review Master/slave settings and power cycle the AC for the changes to take effect.
3. We can act as a master or slave on the link, but you can ONLY have ONE MASTER. please review the individual manuals of the AC remote and the gateway for more details on how to adjust.
4. If there is a remote controller on the link check that they can control the AC from the remote controller or if there are any error messages on the display.
5. Check limitation on AC system for change of mode, etc. ex. Sequence to change from one mode to the other, fan, dry, etc.

Review:

1. coms setting on the ASCII side.
2. The format on the ASCII strings.
3. test with a 3rd party tool like HyperTerminal, putty or similar.

Check that:

• There are no Wiring/power issues on the KNX side, review that your power supply is KNX certified and its guidelines on distances and loading.
• The physical address of the gateway is correct and not duplicated on the bus.
• The objects that you are seeking to control are assigned to the appropriate groups.

If using an ETS programmed gateway use diagnostics in ETS.

If is a MAPs programmed gateway you can use the hardware test on the diagnostics tab and check the KNX viewer with the debug to see the traffic on the KNX side.

Just the basic objects are displayed by default, you can adjust and modify the objects on the parameters tab of your device on ETS, as you select or modify this configuration you would modify or add different objects.

These interfaces are programmed only from MAPs then you link the groups to the devices on your KNX installation to control them or get feedback.

The main thing to have in mind as per any other KNX setup is that there is no other device using the same physical address of the gateway.

We would recommend using an application download if you are using an up to date gateway, this is quicker and can take in between 10-20 min depending on the traffic on the bus. Avoid using unloading and a full download again as this may significantly increase the loading times.

To help the speed and reliability of the communication you can isolate the device with only the power supply and programming interface to make sure that traffic on the rest of the bus does not interfere with the download, especially if you have a heavy loaded line with a lot of traffic.

If you are in a large KNX installation with line couplers or equipment that requires some communication with our gateway, it is possible that you need to use our Dummy project which can be found here:

Download the file Dummy Intesis

In there you will find a dummy device with multiple communication objects. To implement, you can follow these instructions:

1. Import the dummy project (Dummy Intesis v0.1).
2. Open the dummy project (Dummy Intesis v0.1).
3. Locate the dummy device (Dummy Intesis).
4. Copy this device (right-click with your mouse on the device and select "Copy").
5. Paste the device inside your own project (right-click with your mouse on the device and select "Paste").

After that, the only thing you need to do is to set the dummy with the signals you want to integrate

Once you are done remember to update all line couplers, so they get noticed about this "new device" and the associated signals that they have to get through the communication bus.

M-Bus protocol states that up to 250 slave devices can be connected in one loop. Our gateway you can connect up to 120 meters or less (according to your license).

Up to 1000m.

Star and Bus are compatible with M-Bus, but we always recommend using Bus topology.

The time format is the Epoch time (Unix Time stamp), you can use a convertor like this https://www.unixtimestamp.com/index.php

• 01-Mar-1981 04:05:06 :352263906
• 07-Jun-1994 18:17:16 :771005836
• 22-Feb-2021 07:12:03 : 1613974323

Check that:

1. That you are using an RS485 cable especially important the longer the bus.
2. Make sure that the Bus is all daisy chained
3. Baud rate needs to be the same for all devices on the bus
4. Check end of line resistors, the longer the bus the more important.
5. Polarity, try swapping A and B.
6. MAC address needs to be unique on the bus.
7. Test with a 3^rd party tool like YABE together with an USB-RS485 convertor.

1. Troubleshoot as any network device, check subnet mask, IP address, ping, etc.
2. Test with a direct connection, from the PC to the gateway.
3. If problems writing to an output type of object check priority.
4. Check that device and object instances are not duplicated.
5. Test with a 3^rd party tool like YABE.

The BACnet Client is normally associated with the BMS or central system as it would normally start most of the communication transactions, and the BACnet servers the devices out on the field providing the data and points for control, for example our AC gateways would be a BACnet server providing all the information about the AC and awaiting for the control messages of the Client.

For a particular devices on the PIC statements or BTL certification you can see this on the BIBBs (Bacnet interoperabilty Building Blocks) that are used for a device if most of them are end in "A" are generally Clients(the user of data) or "B" is generally the Server (provider of data). For example, a device the following BIBBS would be a server.

BIBBs Supported

Please note that you would need a client and one or multiple servers in an installation for a BACnet system to work, 2 servers on its own would not communicate to each other, the same would happen with 2 clients. If you have by mistake selected the wrong protocol translator gateway please contact us through our support portal for advis.

BACnet discovery uses two services - one is called ‘Who-Is’ and the other ‘I-Am’. They rely on the use of broadcasts messages.

Routers join IP networks together so that messages from one network can be sent to another. Most routers do not forward broadcast messages, and this means discovery can't discover devices on another network.

To solve this problem, BACnet provides a technology called BBMD - BACnet/IP Broadcast Management Device.

When trying to reduce traffic this also can be managed with the use of virtual networks combined with BBMD to reduce the traffic within networks.

Some of our protocol translators include this feature so they can take the role of a BBMD in the network, see the user manual of your specific gateway for details.

To discover the MSTP side please make sure that set the BACnet client in MSTP in the configuration tab.

LON network requires commissioning while the neuron ID only requires obtaining this number

Use pin service button to get the neuron ID of the devices, you can see this in the MAPs diagnostic tab/LON viewer, remember to enable Coms and Debug.

Check that:

1. That you are using an RS485 cable especially important the longer the bus.
2. Make sure that the Bus is all daisy chained
3. Baud rate, parity, etc. needs to be the same for all devices on the bus
4. Check end of line resistors, the longer the bus the more important.
5. Polarity, try swapping A and B
6. Test with a 3^rd party tool like Modbus Poll, Modscan together with an USB-RS485 convertor

1. Troubleshoot as any network device, check subnet mask, IP address, ping, etc.
2. Test with a direct connection, from the PC to the gateway.
3. Check that the function and register match correctly.
4. Test with a 3^rd party tool like Modbus poll, Modscan, etc.

For the Modbus master and servers to correctly communicate you need to pair the correct registers with the appropriate function makes sure that they are set as per the following guidelines

Different Modbus clients (Masters) would support some or all, the functions are:

1 - Read coils.

2 - Read discrete inputs.

3 - Read holding registers.

4 - Read input registers.

5 - Write single coil.

6 - Write single register.

15 - Write multiple coils.

16 - Write multiple registers.

Please note that CRC is used only on Modbus RTU as TCP does use other methods for data integrity

This option is for signals such as a clear filter alarm or other types of alarms that need to notify the field device to take action, and it would receive the desire value and immediately after come back to 0, just so the next time it gets a change is already at 0 and a change is detected and then notify the field device protocol. If your BMS has already this dynamic build in the operation then use a normal read/write signals as you see fit.