Intrepid Control Systems Japan K.K.
  • ホーム
  • 会社概要
    • 沿革
    • アクセス
    • 主要顧客
    • 海外支社・代理店
  • 製品紹介
    • ネットワークインターフェイス >
      • ValueCAN >
        • ValueCAN Specs
        • ValueCAN4-2
      • neoVI FIRE 2
      • neoVI FIRE/RED
      • neoVI MOTE >
        • neoVI MOTE Specs
      • RAD-Galaxy
      • RAD-Star 2
      • RAD-Moon
      • RAD-Moon2
    • データロガー >
      • RAD-Gigalog
      • neoVI FIRE 2
      • neoVI FIRE/RED
      • RAD-Galaxy
      • neoVI ION >
        • neoVI ION Specs
    • ソフト >
      • Vehicle Spy >
        • Advanced Features
        • New Features
      • Vehicle Spy ヴァージョン比較
      • Wireless neoVI
      • DetaSpy
      • EEA COM
    • 車載イーサネットツール >
      • RAD-Galaxy
      • RAD-Star 2
      • RAD-Gigastar
      • RAD-Moon
      • RAD-Moon2
      • RAD-Pluto
      • RAD-Jupiter
      • Ethernet EVB
    • 自動運転ツール >
      • Autonomous One
      • RAD-Gigalog
      • RAD-Gigastar
    • SerDesツール >
      • RAD-Gigalog
      • SerDes Media Conveter
    • 適合ツール >
      • Controller Master Probe
    • アナログ I/O >
      • RAD-IO2
    • ECUシミュレーター >
      • neoEUC12
      • neoECU AVB/TSN
    • ハードウェア比較
  • サポート/ダウンロード
    • ソフトウェア/ハードウェアのライセンス、保証、規定 >
      • ソフトウェアに関するライセンス契約
      • ソフトウェアドライバーに関するライセンス契約
      • RMA 情報
      • 最終ユーザーへのハードウェア保証
    • 製品マニュアルや仕様書
    • Vehicle Spy 3 解説ビデオ
    • 無料ダウンロード
  • オンライン見積り
  • よくあるご質問
  • 製品カタログ
  • ニュース
  • お問い合わせ
Overview
Navigation
Live Capture
Cursors
Importing
Exporting
Decoder Setup
Analysis
Automated Test
Specifications

FlexRay:
Overview
Static Frame
Dynamic Frame
Wakeup
Startup
Physical Layer
Compare to CAN and LIN

CAN Bus:
Overview
Data Frame
Extended Frame
Remote Frame
Error Frame
Bit Stuffing
Physical Layers
Single Wire CAN
Compare to LIN and FlexRay

ここをクリックすると、編集できます。
LIN Bus:
Overview
LIN Frame
LIN Header
LIN Slave Part
LIN Errors
Compare to CAN and FlexRay

Other Buses:
Overview
UART: Kline, J1708, and RS232
J1850
SPI
12C

DOWNLOAD WaveBPS Trial Edition

BUY NOW!
 



















































WaveBPS: CAN Data Frame

The CAN bus data frame does the work on CAN. The whole point of CAN is to send data between networked controllers - and that is the job of the data frame.

The data frame begins with a single SOF (start of frame) bit and is followed by the CAN Identifier. The CAN Identifier is used to identify the message and the node the message is coming from. The identifier can be either 11 bits long or 29 bits long depending on the state of some reserved bits.

Picture
The CAN Data Frame Starts with a SOF bit and then ID bits.
After the CAN Identifier, there is a data section that first begins with a data length. The CAN data frame can have 0 to 8 bytes so it uses 4 bits to encode length. The data bytes directly follow the data length.
Picture
The data bytes follow the data length (DLC) in the CAN Frame.
Following the data is the CRC. The CRC is a calculation that is made on the first part of the CAN frame by both the receiver and transmitter. If they match the receiver assumes that it received the data correctly.
Picture
The CAN CRC checks data integrity while the ack indicates reception by another node.
Following the CRC is the Ack field. This field will be set by all other nodes on the network who properly received the frame.

After the Ack bit there will be a quiet time called end of frame space followed by a minimum inter-frame space.

Picture
Picture of a CAN Data Frame
株式会社日本イントリピッドコントロールシステムズ / Intrepid Control Systems Japan, KK 電話番号 +81 (0)3-5937-1523  ファックス +81 (0)3-5937-1524
個人情報の取り扱いについて
Go to ICS main site: www.intrepidcs.com