industrialNETworXnetx

Home » HAL » NXHAL-CAN

NXHAL-CAN

0
Drag and click to vote!

Facts

  • Configuration of the CAN Controller
  • Getting of Status Information of the CAN Controller
  • Sending of CAN frame transmission requests to the CAN Controller
  • Getting of Confirmations about processed transmission processes
  • Getting of CAN frame indications from the CAN Controller
Subject Data
Technical Data
  • FullCAN Controller
  • Fully Compliant with CAN Standard rev 2.0 A and rev 2.0 B
  • 2 request queues (high priority, low priority)
  • 2 indication queues (high priority, low priority)
  • 1 confirmation queue
  • Number of elements per queue is adjustable
  • Single-shot mode
  • Abort transmission possible
  • Confirmation suppression possible
  • Listen-only mode for baud rate detection and bus monitoring
  • Baudrate detection with only one CAN node possible
  • Different acceptance filters for Standard and Extended CAN frames
  • Filtering of standard frames for each Standard identifier selectable
  • Priority of standard frames for each Standard identifier selectable
  • 8 Extended identifier/Rtr combinations are able to declare as high prior
  • transmission and reception timestamp included in each confirmation/indication
  • edge detection at xMAC IO0 and xMAC IO1 (e.g. for power-failed signal in DeviceNET)
  • supported baudrates: 10/12.5/20/50/100/125/250/500/800/1000kBaud 
  • all CAN frame content except stuff bits are indicated to user to allow CRC recalculation
Limitations
  • No TTCAN (Time Triggered CAN) functionality 
  • bit timing parameters (PhaseSeg1, PhaseSeg2, IPT, SJW) are fixed and not adjustable
Version
Revision:

4.2.x.x

Date: 28.06.2010
Status: Release
Issue Tracker Blog

To download software on industrialNETworX.com you need to fill out the following fields in your profile:

  • First Name
  • Second Name
  • Email Address
  • Company
  • Industry
  • City
  • Country
  • Homepage

Description

The Hardware Abstraction Layer is a set of C-Functions which work as an
interface between the netX Software Application and the netX CAN-Controller. The
aim is to have an interface which is operating independent and downwards
compatible between all existing and future netX Network Controllers. They are
easier to use as writing or reading directly the Controller Registers.

Login

Documentation

  • There are no documenation files

Related Wikipages

  • There are no related wikipages