Intrepid Control Systems Korea
Intrepid Control Systems
            한국 지사 연락처
         ​+82)031-698-3460
  • 홈
  • 회사소개
  • 제품소개
    • 소프트웨어 >
      • Vehicle Spy >
        • Vehicle Spy Enterprise
        • Vehicle Spy Professional
        • Vehicle Spy 고급기능
        • Vehicle Spy 버전별 비교표
      • Wireless neoVI
      • WaveBPS
    • 차량 이더넷 제품 >
      • Automotive Ethernet 완벽 가이드
      • RAD Galaxy
      • RAD Star 2
      • RAD-SuperMoon (1000BASE-T1)
      • RAD Moon (100BASE-T1)
      • Ethernet EVB
    • 차량 네트워크 어댑터 >
      • neoVI FIRE 2
      • neoVI PLASMA
      • neoVI ION
      • neoVI FIRE/RED
      • ValueCAN 4 >
        • ValueCAN4-2 (2 CAN FD)
      • neoVI FLEX
    • 차량 데이터로거 >
      • neoVI FIRE 2
      • neoVI PLASMA
      • neoVI ION
      • neoVI FIRE/RED
    • 기타 액세서리 >
      • neoECU 시리즈 >
        • neoECU 10
        • neoECU 20
      • neoVI MOTE
      • neoRAD I/O
      • Oscilloscopes
    • ICS 차량 네트워크 인터페이스 비교표
  • 자료 / 다운로드
    • Warranty, License, and Policies >
      • Software License Agreement
      • Hardware Driver License Agreement
      • RMA Policy
      • Hardware Warranty
      • Return Policy
    • 사용자 매뉴얼 및 실습 자료 >
      • Vehicle Spy >
        • Vehicle Spy Documentation
        • Vehicle Spy Quick Start Guide
        • Vehicle Spy Guide: Using Ethernet
        • Vehicle Spy 예제
        • ASAP2 Editor Documentation
      • neoVI Hardware (General) >
        • neoVI Hardware Documentation
        • neoVI icsneo40 DLL Documentation
        • Linux API Documentation
      • neoVI FIRE 2 >
        • neoVI FIRE2 사용자 매뉴얼
      • neoVI PLASMA >
        • neoVI PLASMA Documentation
      • neoECUs >
        • neoECU10 & neoECU20 Documentation
      • Ethernet Products >
        • Ethernet EVB 실습 매뉴얼
        • Ethernet EVB 사용자 매뉴얼
        • RAD Moon 사용자 매뉴얼
        • RAD Star 사용자 매뉴얼
    • Vehicle Spy 3 사용법 동영상 가이드
    • 무료 프로그램, 자료, 다운로드
  • 온라인견적
  • 블로그 / 뉴스
  • 교육
  • 위치 및 연락처
  • Vspy Training Resources
  • 개인정보처리방침
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: "wbps" Double Precision Floating Point Type

After the number of channels described in the parent topic. The floating point format includes a 4 byte integer describing the offset to the data (Table 1). You can use the offset to set the file position to the start of the data. Using the offset, the number of raw data samples in the file can be calculated with this equation. (You probably want to cast each item in the equation to an __int64 considering the files sizes can be very large) NumberOfDataValues = (SizeOfFile() - m_iOffsetToTheData) / (sizeof(double) * (1+m_iNumberOfChannels))
Table 1 - Offset to the Data

Type

Header

Unsigned int (32 bits) m_iOffsetToTheData
At the offset there is one double precision float (8 byte value) describing the time, and then one double precision float for each channel at that time. This repeats for every data sample. The time is in microsecond units while the channel data is in volts. For reading the wbps format the above information is the minimum needed to use the format. For writing the format you must have the following information as well. After the offset integer are two parameters that describe the trigger (Table 2). First is a unsigned integer that indicates whether there is a trigger location present in the file. This will be either 0 meaning no trigger or 1 meaning a trigger is present. Following the trigger is a double precision parameter indicating where in microseconds the trigger exists (this must be present if a trigger is valid or not).
Table 2 - Trigger Information in File

Type

Header

Unsigned int (32 bits) m_iHasTriggerLocation
Double Precision Floating Point (8 bytes) m_dTriggerLocationInMicroseconds
Following the trigger is information about the decoders used when the file is saved. The decoder is stored as a convenience in the wbps file so when it is loaded it will be properly displayed (very useful when sharing waveforms). The file format for the decoders will not be described here. For readers of the file format this data can simply be ignored. For writers of this format, you can write a signed integer equal to -1 for each channel and WaveBPS will simply ignore the decoder section when it reads the file (Table 3).
Table 3 - Decoder Ignore Sequence (repeat for each channel)

Type

Header

Signed int (32 bits) iDecoderType (set to -1)
홈
회사 소개
제품 소개
개인정보처리방침


자료 / 다운로드
위치 및 연락처
온라인 견적
블로그 / 뉴스
ICS 메인 사이트:
www.intrepidcs.com (USA)



ICS 글로벌 사이트:
www.intrepidcs.com.cn (China)
www.intrepidcs.jp (Japan)
www.intrepidcs.com (Germany)
www.intrepidcs.com (India)
www.intrepidcs.com (Australia)
인트레피드컨트롤씨스템즈코리아 유한회사 / Intrepid Control Systems Korea, LLC. © 2016  |  대표이사 박경일
Intrepid Control Systems Korea, LLC. is a subsidiary of Intrepid Control Systems, Inc.
외국인투자법인 등록번호: 제 36209 호
사업자 등록번호: 144-81-15345
대표번호 +82 31 698 3460 팩스 +82 31 698 3461
Last Modified 2016/6/23 23:02:15 KST