ICC XLTR--1000

[Jcamacho]

Hello I am looking to use an XLTR-1000 to interface with a set of Ebm- Papst Fan . The fan 's interface is modbus and I need to get it talking on bacnet can anyone provide any input on this .

Thanks,

[jschulze]

Hello,

I am the product specialist at ICC for the XLTR-1000. We actually have a new product called the Mirius that we recommend for new applications, although the XLTR-1000 is and will continue to be available. The Mirius includes a variety of enhancements such as:

• Galvanic isolation (3 isolation planes separate power and each serial port)
• Supports 9 – 24V AC or DC power
• Over 3.5 times the object memory and twice the database size compared to the XLTR-1000
• Multi-Interface port (Port B) allows jumper selection of RS-485, RS-232, or TTL UART physical layers
• Supports digital, analog, and pulse I/O (two dedicated channels + two channels shared with serial communication)
• Supports configuration locking, allowing an OEM or system integrator to access the configuration on the device while restricting an end user’s access to just the necessary Network Configuration Parameters (baud rate, station number etc.)
• Supports configuring multiple protocols on Port A. The NPU or port B communications can be used to dynamically select the active protocol.
• Supports 64 bytes of persistent user data allowing information such as serial numbers, calibration data, etc. to be stored and persist across reboots and power loss
• The Mirius is physically smaller (less than half the size of the XLTR-1000) and includes built-in DIN rail mounting
• OEM customizable – both the Mirius and the NPU software can be rebranded and customized by the OEM for redistribution to their customers
• BTL listed for both BACnet MS/TP client and server roles

The Mirius also carries forward the most popular additional features of the XLTR-1000, such as database logic, USB virtual COM port support, and various tools including support for BACnet network analysis via Wireshark.

The Mirius was conceived with the intention of supporting relabeling for OEMs and system integrators, and therefore supports an optional two-level configuration process. The configuration of protocol object mappings is still done (by the OEM) using the ICC Configuration Studio and is part of the static configuration of the Mirius. The other level of configuration comes from the dynamic Network Configuration Parameters, which allow an end user to configure settings for the gateway’s Port A network port such as address, baud rate, parity, device instance, etc. that typically are not known until the actual integration of the device onto the end network. To configure these settings (and only these settings), the OEM can provide the end user with a self-branded version of our light-weight Network Parameter Utility (NPU) USB software. Alternatively, these network-specific parameters can be configured via communications on the Mirius’ Port B serial port, allowing these settings to be modified by an end user through the OEM’s own product.

If you need assistance configuring the Mirius or XLTR-1000 for your application, please submit a support ticket on our website (iccdesigns.com) and I can answer any specific questions you may have and provide you with an example configuration to help get you started.

[sammybear]

I saw the Mirius at the AHRExpo, I was quite impressed. We plan to try to use it in our current project (a 16 story hospital addition) as we have a lot of Modbus devices that we need to switch to bacnet/mstp.