Ixxat articles and blog posts

Technical articles, tips from the experts,
and much more.

Blog

CAN@net NT – boundless fields of application

by Rainer Hoja-Heldmann | Jul 11, 2017

Wherever easy and flexible access to CAN systems via Ethernet is needed or an industry-grade linking of remote CAN bus segments is necessary, IXXAT CAN@net NT 200 and CAN@net NT 420 are the means of choice. Both devices let customers benefit in multiple ways:

  • High flexibility: Several operating modes with one device
  • High performance: Up to 40.000 CAN messages per second
  • Fast boot-up: within 1 second
  • Easy configuration: via USB or Ethernet and a free of cost Windows tool

Learn more

 

The fields of application for the CAN@net NT are boundless

Generally CAN@net NT can be used wherever a controller or host shall be connected to a CAN network or where CAN networks shall communicate over long distances via Ethernet. Below you will find some examples of how CAN@net NT can be used in different environments:

  • Remote access to CAN networks via Ethernet for service issues
  • (Re-)Use existing Ethernet networks for remote monitoring of CAN-based systems
  • Combination of distributed CAN networks via Ethernet backbone
  • Get rid of EMI issues and extend the range of CAN networks

 

 "Secure" service via LAN line saves time of technician

 

With the aid of the IXXAT VCI (Virtual Communication Interface) for Windows – included in the scope of delivery – the CAN@net NT can be operated like any IXXAT CAN PC interface.

Secure service via LAN line saves time of technician

 

With the CAN@net NT, all VCI-based IXXAT tools, such as the canAnalyser, as well as customer-specific applications based on the VCI driver can be used. The VCI CAN driver offers the possibility to communicate with up to 128 CAN@net NT devices at the same time.

Especially service and maintenance of wind turbines is an arduous task. Whenever a failure in the control unit occurs, the technician has to climb up to 100 m to get to the nacelle on top of the windmill. Life becomes easy though, if the pitch control and/or other sensors of the wind turbine are connected to an Ethernet line, leading to the foundation of the windmill. Thus the technician can stay on the ground and connect its laptop to the control room via LAN line for remote analysis, configuration and more

 

(Re-)Use existing Ethernet-topology to enable long-haul CAN connectivity

 

In gateway mode the CAN@net NT can be directly accessed from e.g. Windows, Linux, VxWorks or QNX based systems as well as from embedded systems, by using a simple ASCII protocol over a standard TCP/IP socket. As CAN to Ethernet Gateway, the CAN@net NT offers easy, flexible access to four independent CAN systems (two switchable to CAN FD) via LAN or the Internet.  

 

Use existing Ethernet-topology to enable long-haul CAN connectivity

 

A customer project solved this way, was the connection of compressors and vacuum devices of a hospital via an existing Ethernet network to the main control center. Possible other use cases could be the connection of ticket machines or elevators to main control centers for service and alarming purposes.

 

Get rid of EMI issues with CAN-Ethernet-CAN bridges


Communication networks in cargo ships and oil tankers are extended over several hundred meters and are subdivided into numerous subsystems. Due to the heavy machinery signal disturbances are the order of the day.

 

Get rid of EMI issues with CAN-Ethernet-CAN bridges

 

In a customer project CAN@net NT were used to physically separate several CAN networks for the purpose of galvanic isolation and to solve possible EMI issues in parts of the network. The logical separation of CAN networks includes the following opportunities

  • Fully independent CAN networks with own master(s)
  • Filtering of messages
  • Networks can have different bitrates
  • Extending a network – no length limitation due to arbitration, only reaction time of application
  • Modify messages, IDs and Data 
 

 

Meshed CAN networks via Ethernet 

 

By using up to four CAN@net NT 420 a meshed CAN network can be implemented with each up to four independent CAN channels per device. This network allows for the exchange of CAN messages between CAN systems over long distances via TCP/IP, using (existing) Ethernet infrastruc-tures. The segmentation of CAN systems also increases the reliability and failure immunity of the entire system.

 

Meshed CAN networks via Ethernet

 

With the aid of mapping tables, the exchange of messages between all channels can be configured very flexibly. Filter and conversion rules can be applied to the CAN and CAN FD messages. As a result, the bus load in the individual networks can be reduced since only relevant messages are transmitted to the other network. The data multiplexing functionality enables the mapping of e.g. CAN FD data to several standard CAN messages.

This special use case only applies for CAN@net NT 420 devices. A mixture of CAN@net NT 420 and NT 200 devices is not possible. A possible use case is e.g. the connection of several elevator systems of big office buildings or hotel complexes which need to send their relevant data via an Ethernet network to a central control center.