CAN@net NT 100

The CAN@net NT 100 offers a variety of functionalities that can be flexibly deployed in any desired application.

CAN-to-Ethernet Gateway

In gateway mode, the CAN@net NT 100 can be accessed directly from, for example, Windows^®, Linux, VxWorks, and QNX-based systems and servers, as well as from embedded environments. Communication takes place via a standard TCP/IP socket and uses a standard ASCII protocol for this purpose. As a CAN Ethernet Gateway, the CAN@net NT 100 offers simple and flexible access to one CAN channel, via a LAN or via the internet.

CAN@net NT 100 - Gateway and PC interface functionality

For the interfacing, the free source code C API ixcan is available, allowing applications with CAN interfacing to be built without the need for an additional (kernel) driver.

CAN-to-Ethernet PC interface

With the included VCI driver for Windows^®, the CAN@net NT 100 can be used as a full-fledged PC interface, like all Ixxat CAN PC interfaces. With CAN@net NT, all VCI-based Ixxat instruments, such as the canAnalyser, as well as customer-specific applications based on the VCI driver, can be used. The VCI CAN driver offers the ability to communicate with up to 128 CAN@net NT devices simultaneously.

CAN-to-Ethernet-CAN Bridge

Using two CAN@net NT 100, a CAN-Ethernet-CAN bridge can be implemented that connects one CAN channel to each other. This bridge enables the exchange of CAN messages between CAN systems via TCP/IP over long distances – using an existing Ethernet-based infrastructure. The segmentation also increases the reliability and stability of the overall system.

CAN@net NT 100 - Bridge functionality

Filtering and Assigning

By using assignment tables, message reception/transmission is possible between all channels. Using filter and conversion rules, CAN or CAN FD messages can be filtered or modified. This mechanism allows for a reduction in bus load within the individual networks. For SAE J1939 applications, a special assignment table is provided, adapted to the specific parameters.

The CAN Gateway Configurator enables free routing configurations. Individual messages or message groups can be assigned from and to any CAN port. The route through the device always starts at the receiving controller (message transmitter) and ends at the transmitting controller (message receiver).
For SAE J1939 applications, a special mapping table is provided, adapted to the specific parameters.

Action Rules

In response to received messages, device or CAN bus status events, a variety of actions can be performed automatically, e.g. sending messages (CAN, MQTT), changing device settings, or switching device LEDs. Action rules are created via intuitive event and action drop-down menus within the Windows^®-based Device Configuration Tool.

Status Message

For diagnostics and troubleshooting, the CANbridge NT can send a status message via CAN if desired. For each CAN channel, it is reported whether it is Active, Error, Bus Off, or Not Available.

MQTT for cloud connection

Whether device status or CAN data, the MQTT functionality of the CAN@net NT 100 enables transmission of various information to the cloud – easily programmable using action rule lists. With free available broker services and APPs, e.g. status messages or system values can be easily transmitted to your smartphone or other devices.

Cyclic transmission

The cyclic transmission feature enables cyclic forwarding of messages. Both, messages and cycle times are defined within a central cyclic transmission table.

LUA

Additional programming of all kinds of action rules is made possible by using LUA. This is a powerful, efficient, and lightweight scripting language that is built in by default.

Configuration and firmware update

Using an easy-to-operate Windows^® configuration tool, the CAN@net NT 100 can be configured and firmware updates can be performed either locally via USB or remotely via the Ethernet interface. The tool makes it very easy to configure filter, mapping or translation rules without any programming knowledge.. With the tool, the configuration of filter, mapping or translation rules can be carried out very easily, without programming skills.

With the help 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 messages. As a result, the bus load in the individual networks can be reduced since only relevant messages are transmitted to the other network.

CAN@net NT 100 Congiguration tool

ASCII Ethernet messages

In Gateway Mode, the CAN@net NT 100 exchanges standardised ASCII messages via TCP. The message format used is fully documented and available for download. Using the examples provided, TCP Stream Handling can be used to exchange messages between the CAN@net NT 100 and a device with an Ethernet connection.

C-API ixcan

The Ixxat C-API ixcan is a programming interface for C applications that allows software to communicate directly with the Ixxat CAN@net NT 100 gateways. The API translates C function calls into ASCII commands according to the ASCII Gateway Mode of the CAN@net NT. This allows developers to send, receive, and process CAN messages without having to fully implement the underlying ASCII protocol themselves. C-API ixcan can be easily implemented in any application or Operating System without the need for an additional (kernel) Device Driver. The API is not compatible with the Ixxat VCI driver.
The Ixxat C-API ixcan is intended for specialized technicians familiar with ASCII, CAN, CAN FD, and programming in C.

LUA SDK

The CAN@net NT 100 comes standard with Ixxat Lua ADK (Application Development Kit). This is based on the standard Lua 5.3.5 distribution, a fully featured implementation of Lua 5.3 and optimised for CAN@net NT. Lua scripts can be used to implement additional functionality for processing or responding to CAN messages.

Ixxat canAnalyser 3 Mini

For simple testing purposes and start-up canAnalyser Mini - a free CAN bus monitor - is installed with the VCI. This monitor can be used to display CAN messages with time stamp, message identifiers and data using the CAN@net NT 100. A logging function enables the data received to be recorded directly to hard disk. CAN messages are transmitted via a list wherein CAN messages are entered. Installed interfaces are displayed with the available CAN controllers, the current bus load and the controller status.
canAnalyser Mini also support CAN-FD and LIN in combination with interfaces supporting these protocols.

Ixxat canAnalyser Mini

Ixxat CAN Interface Driver

Two different drivers are available for the software interfacing of the CAN@net NT 100: the universal driver "(Virtual Communication Interface" (VCI) for Windows^® and the “Embedded Communication Interface” (ECI) for Linux, INtime, RTX, VxWorks and QNX. The drivers can operate all CAN channels and all CAN interfaces - even different types - within one PC.

These powerful driver packages support all CAN boards, regardless of their PC interface, with a uniform programming interface (API). This means that applications based on VCI-API can be used with all Ixxat CAN boards without modifying the application program. The drivers support multi CAN-channels and/or multiple boards – even different types – to arrange the desired amount of channels.

Features and benefits

• Common application programming interface (API) for all supported operating systems and interfaces
• Simultaneous support of multiple CAN channels and interface boards
• Standard  (11 bit, CAN 2.0A), extended protocol (29 bit, CAN 2.0B) and CAN-FD¹
• Support of protocol-switching on interfaces with low-speed CAN¹ or LIN¹
• Slim communication interface while supporting all required mechanisms for an easy operation of the interface
• Detection and display of error frames on the bus
• Measurement and display of the bus load (only with active CAN cards)
• Possible operation in "Listen only mode"
¹ For interfaces that support these protocols

VCI Driver

Ixxat VCI API

The VCI API (Application Programming Interface) is a powerful software library that enables developers to easily communicate with industrial network interfaces, particularly within CAN- and/or LIN-based systems. This API forms an abstraction layer between applications and hardware, allowing developers to avoid working directly with device-specific drivers and instead utilize a uniform and standardized interface.

VCI Driver Model and common API

With the VCI API, applications can send and receive CAN messages in both standard and extended formats. Additionally, the API enables the detection, configuration, and management of connected Ixxat devices. Developers can choose between event-driven communication or polling mechanisms, depending on their application requirements. Thanks to built-in buffering and filtering capabilities, data can be processed efficiently, which is particularly important in real-time environments.

The API is primarily available for programming languages ​​such as C and C++, with additional support for .NET languages via wrappers. This makes the VCI API widely applicable within both low-level and high-level development environments.

• Is there a CAN terminating resistor built into the CAN@net NT 100?

  This CAN interface does not have a built-in CAN terminating resistor, nor is there an option to add one. However, we can offer the Termination adapter CAN/ CAN FD as an accessory. It simply plugs in between the D-sub 9 connector and the cable.

• How do I choose the right CAN gateway?

  Choosing the right CAN gateway depends, among other things, on the desired CAN protocol, the intended application, the desired bus speed and electrical isolation, data processing requirements, the length of the network, the acceptable processing delay, any available installation space, the intended use, and, of course, the available budget.

  Twincomm is a center of expertise for CAN and has over 30 years of experience with CAN. Please contact us and we’ll provide practical advice to help you make the right choice.

• Which Ixxat CAN analysis software is best suited to my use case?

  The canAnalyser is a versatile analysis tool for the development, testing and servicing of CAN, CAN FD and LIN based systems. The software package is based on a modular concept and available in three versions - Mini, Lite, and Standard - with a different set of functions and modules.
  The Mini version is included free of charge with the VCI driver. It is ideal for quick diagnostics or hardware testing, for example. The Lite and Standard versions are both comprehensive, professional software packages designed for development, debugging, simulation, or testing of CAN, CAN FD and/or LIN-networks.

  Each version of the canAnalyser 3 is intended for typical use case. The table below provides a handy overview of all the differences.

  Functions	Module	canAnalyser3 Mini	canAnalyser 3 Lite	canAnalyser 3 Standard
  Measurement configuration
  Supported bus controllers		1	1	64
  Number of function modules per bus controller (multi-start)		1	1 per function
  Transmission
  Transmitting messages in layer 2 format via broadcasting lists (one-off/cyclic)	Transmit	Max 5
  Transmitting signals based on underlayed databases	Signal/Transmit
  Transmitting sequences in layer 2 format using simple commands for control	Sequencer
  Reception and display
  Display received messages - Scroll view - Overwrite mode	Receive
  Filtering during reception	Receive
  Signal reception and interpreted online display based on databases (overwrite/scroll)	Signal		Max 5
  Graphical display of received signals over the time axis	Signal		Max 5
  Display of statistical values (e.g. bus load, number of error frames)	Signal
  Logging of value range overflows	Signal
  Graphical display of frequency distribution of received messages	Histogram
  Recording/Playback
  Recording on hard disk - Maximum size	Trace	1 GB
  Filter and trigger functions during recording	Trace
  Recording on hard disk for later analysis, including filter and trigger functions	Trace
  Playback of recordings on the buses and/or modules for analyzing	Replay
  Adaptation and Extension
  Development of measurement/analysis functions using C# and Visual-Basic .NET scripts	Scripting/Host
  Open interface for expansion by customer-specific modules (.NET modules)	customized
  Protocol Interpreter
  Display of CANopen messages according to CANopen specification	CANopen
  Display of SAE J1939 messages according to SAE J1939 specification	J1939

• Does this gateway support CANopen or J1939?

  Yes, the CAN@net NT 100 works with all CAN messages, including CANopen and J1939

  However, the CAN messages are not interpreted as CANopen or J1939. In filter and mapping tables, or action rules, for example, the messages are treated as standard CAN messages. enquire about the configuration options.

• Can I order on account?

  Yes, that's definitely possible! Most customers place their orders through a Purchase Order.
  First request a quote and then send the purchase order (PO) by email, simply from your own purchasing system. For first time buyers, we may ask additional questions in order to perform a credit check. Please contact us if you require our company details for registration in the purchasing system.
  
  For security reasons, customers located in, or wishing to ship to, countries outside the Benelux must always pay in advance.

• Why are all prices available upon request?

  The online webshop is still under construction. As soon as it is available, all prices will naturally be visible.

  However, everything is of course available, and we would be happy to inform you about prices and delivery times. Please contact us or give us a call. We have over 30 years of experience with CAN. We are happy to help you and offer you immediate practical advice or support.