Nhận viết luận văn đại học, thạc sĩ trọn gói, chất lượng, LH ZALO=>0909232620
Tham khảo dịch vụ, bảng giá tại: https://vietbaitotnghiep.com/dich-vu-viet-thue-luan-van
Download luận án tiến sĩ ngành kĩ thuật điều khiển với đề tài: Nghiên cứu các bài toán thiết kế các luật điều khiển cho rô bốt di động kiểu bánh xe, cho các bạn làm luận án tham khảo
Tài liệu này không chỉ hướng dẫn các lệnh mà còn tập trung vào phần thực hành, với những lý thuyết liên quan đến công nghệ kim loại tấm bạn sẽ dễ dàng tính được các kích thước tiêu chuẩn và áp dụng vào bài thực hành.
Giáo trình được viết với sự hỗ trợ của các tài liệu nước ngoài, đa phần là giáo trình chính hãng của autodesk, được chúng tôi chọn lọc sao cho phù hợp với điều kiện kỹ thuật của Việt Nam, được diễn giải sao cho từ người chưa biết gì cũng có thể học được. Và quan trọng hơn hết là các bài thực hành khá đầy đủ, chỉ cần làm theo tất cả các nội dung trong tài liệu là bạn có thể nắm hết được các kiến thức về kim loại tấm nói chung và của modul sheet metal trên inventor nói riêng.
Do đây là một modul riêng nên số trang không nhiều như phần lý thuyết chung, tất nhiên đã hướng dẫn hết các tính năng của modul kim loại tấm trên inventor, một cách chi tiết, đúng trọng tâm và không lan man.
Nhận viết luận văn đại học, thạc sĩ trọn gói, chất lượng, LH ZALO=>0909232620
Tham khảo dịch vụ, bảng giá tại: https://vietbaitotnghiep.com/dich-vu-viet-thue-luan-van
Download luận án tiến sĩ ngành kĩ thuật điều khiển với đề tài: Nghiên cứu các bài toán thiết kế các luật điều khiển cho rô bốt di động kiểu bánh xe, cho các bạn làm luận án tham khảo
Tài liệu này không chỉ hướng dẫn các lệnh mà còn tập trung vào phần thực hành, với những lý thuyết liên quan đến công nghệ kim loại tấm bạn sẽ dễ dàng tính được các kích thước tiêu chuẩn và áp dụng vào bài thực hành.
Giáo trình được viết với sự hỗ trợ của các tài liệu nước ngoài, đa phần là giáo trình chính hãng của autodesk, được chúng tôi chọn lọc sao cho phù hợp với điều kiện kỹ thuật của Việt Nam, được diễn giải sao cho từ người chưa biết gì cũng có thể học được. Và quan trọng hơn hết là các bài thực hành khá đầy đủ, chỉ cần làm theo tất cả các nội dung trong tài liệu là bạn có thể nắm hết được các kiến thức về kim loại tấm nói chung và của modul sheet metal trên inventor nói riêng.
Do đây là một modul riêng nên số trang không nhiều như phần lý thuyết chung, tất nhiên đã hướng dẫn hết các tính năng của modul kim loại tấm trên inventor, một cách chi tiết, đúng trọng tâm và không lan man.
Nhận viết luận văn Đại học , thạc sĩ - Zalo: 0917.193.864
Tham khảo bảng giá dịch vụ viết bài tại: vietbaocaothuctap.net
Download luận văn đồ án tốt nghiệp với đề tài: Tổng quan về mobile robot, cho các bạn có thể tham khảo
Đồ án tốt nghiệp điện tử viễn thông Điều khiển đèn giao thông điểm cao
- sdt/ ZALO 093 189 2701
Viết thuê Đồ án tốt nghiệp điện tử viễn thông, Bài mẫu Đồ án tốt nghiệp ngành điện tử viễn thông, Khóa luận tốt nghiệp ngành điện tử viễn thông, Đề tài đồ án tốt nghiệp ngành điện tử viễn thông
http://vietthuewriter.com/category/do-an-tot-nghiep-nganh-dien-tu-vien-thong/
Nhận viết luận văn đại học, thạc sĩ trọn gói, chất lượng, LH ZALO=>0909232620
Tham khảo dịch vụ, bảng giá tại: https://baocaothuctap.net
Download luận văn đồ án tốt nghiệp với đề tài: Nhận dạng, phân loại, xử lý ảnh biển số xe bằng phần mềm, cho các bạn làm luận văn tham khảo
eplan is a application electronic .you can you it to draw,make ,symboy and any thing else. and that is induction for you to use it .try to do and you can use it so simple.
Nhận viết luận văn Đại học , thạc sĩ - Zalo: 0917.193.864
Tham khảo bảng giá dịch vụ viết bài tại: vietbaocaothuctap.net
Download luận văn đồ án tốt nghiệp với đề tài: Tổng quan về mobile robot, cho các bạn có thể tham khảo
Đồ án tốt nghiệp điện tử viễn thông Điều khiển đèn giao thông điểm cao
- sdt/ ZALO 093 189 2701
Viết thuê Đồ án tốt nghiệp điện tử viễn thông, Bài mẫu Đồ án tốt nghiệp ngành điện tử viễn thông, Khóa luận tốt nghiệp ngành điện tử viễn thông, Đề tài đồ án tốt nghiệp ngành điện tử viễn thông
http://vietthuewriter.com/category/do-an-tot-nghiep-nganh-dien-tu-vien-thong/
Nhận viết luận văn đại học, thạc sĩ trọn gói, chất lượng, LH ZALO=>0909232620
Tham khảo dịch vụ, bảng giá tại: https://baocaothuctap.net
Download luận văn đồ án tốt nghiệp với đề tài: Nhận dạng, phân loại, xử lý ảnh biển số xe bằng phần mềm, cho các bạn làm luận văn tham khảo
eplan is a application electronic .you can you it to draw,make ,symboy and any thing else. and that is induction for you to use it .try to do and you can use it so simple.
인터맥프린터 Intermec PF2i PF4i 열전사감열 바코드프린터 산업용프린터 매뉴얼HION IT
컴팩트한 PF2i, PF4i 미드 레인지 바코드프린터는 인터맥의 스마트하고 강하고 안전한 산업용 프린터 제품입니다.
Intermec SmartSystems ™ 및 Wavelink Avalanche ™를 통해 PF2i의 통합 장치관리 및 진단 기능은 가동 중단 시간을 줄이고 설치를 단순화합니다
견고한 All-Metal PF2i 바코드프린터는 다운 타임을 줄이고 유지 보수 비용을 최소화하는 기능을 통합합니다.
작은 크기에도 불구하고 PF2i는 풀 사이즈 라벨 롤 (최대 8.4 in / 213 mm)을 사용하여 용지 교체 횟수를 줄입니다.
QuickMount ™ 프린트 헤드 디자인 덕분에 프린트 헤드를 빠르고 쉽게 교체 할 수 있습니다.
최고 수준의 보안 무선 연결 (WPA2)을 포함한 여러 보안 인터페이스 옵션을 사용할 수 있습니다.
업계 유일의 프린터인 WiFi- 및 CCX-Certification과 함께 사용할 수있는 인터맥 산업용 프린터는 무선 네트워크 무결성을 유지하고 구성 시간을 단축시킵니다.
모든 프린터는 이더넷 연결 및 출현하는 네트워크 프로토콜 IPv6과 함께 제공되므로 장기간의 엔터프라이즈 확장성을 보장합니다.
기타 연결 옵션 - 표준 RS232 및 USB 포트, 옵션 병렬, 이중 직렬 또는 산업용 인터페이스는 통합 유연성을 추가로 제공합니다.
Strong, all-metal construction and superior throughput for harsh industrial environments
Compact size fits space- constrained applications
Smart Printing capabilities support stand-alone printer applications, eliminating PC expense and complexity
All-in-one, user-selectable printer languages Fingerprint/Direct Protocol (DP), IPL, ZSim and DSim in every printer
Secure wireless connectivity : CCX and WiFi® certified with WPA2
Integrated Ethernet, USB host and device, and serial interface standard
Internet Protocol v6 (IPv6) support
PHYSICAL CHARACTERISTICS
Length : 397 mm (15.6 in)
Height : 178 mm (7 in)
Height (big top) : 205 mm (8.1 in)
Width : 194 mm (7.6 in)
Weight : 5.5 kg (12 lbs.)
PRINT SPECIFICATIONS
Max. Width: 56 mm (2.2 in)
Max. Length: 4095 mm (161.2 in)
Print Speed : 100 ? 200 mm/s (4 - 8 ips) variable
Print Resolution : 8 dots/mm (203 dpi)
MEDIA
Type : Labels & Tags
Max/ Min Width : 60/25.4 mm (2.36/1 in)
Thickness : 3.0 to 7.5 mil
Configuration : Roll-fed or fanfold
Sensing : Gap, notch, black mark, continuous
Label Roll Max Diameter (long door): 152.4 mm (6 in)
Label Roll Max Diameter (short door): 213 mm (8.38 in)
Label Roll Core: 38-76mm (1.5-3 in)
Type : Ribbons
Roll Max Diameter : 65 mm (2.56 in), approx. 225m
Core ID : 25.4 mm (1”)
Type : Wax, mid-range, resin
INTERFACE
Standard :
Ethernet 10/100 Mbps
RS-232, up to 115.2 kB/s
Supported Serial Protocols :
Fingerprint/Direct Protocol : XON/XOFF, ENQ/ACK, DTR, RTS/CTS
IPL: XON/XOFF, Intermec Std. Protocol
USB 2.0
Optional :
Parallel IEEE 1284
Industrial Interface (8 digital in/out, 4 analog relays, 1 RS232/422/485 port)
Dual Serial ports RS-232, RS-422, RS-485 and 20mA Current Loop
Wireless:
IEEE 802.11 b/g
Wi-Fi Certified, CCX (Cisco®) version 3 Certified
WEP, WPA, WPA2, 802.11x (EAP- TTLS, LEAP, PEAP, FAST), 802.11i
Multiple industrial antenna options for maximized coverage
Supported Protocols :
TCP/IP-suite (TCP, UDP, ICMP, IGMP, etc.), LPR/LPD, FTP, BOOTP, DHCP, HTTP, SNMPv3, SMTP.SNMP-MIB II supported (over UDP/IP), private enterprise MIB included Supports IPv4 and IPv6
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
Learn about IBM Flex System Interoperability Guide. This IBM Redpaper publication is a reference to compatibility and interoperability of components inside and connected to IBM PureFlex System and IBM Flex System solutions. For more information on Pure Systems, visit http://ibm.co/J7Zb1v.
Visit http://on.fb.me/LT4gdu to 'Like' the official Facebook page of IBM India Smarter Computing.
인터맥프린터 Intermec PM4i 열전사감열 RFID 바코드프린터 산업용프린터 매뉴얼HION IT
다기능 PM4i는 최신 RFID 기술과 함께 Intermec의 바코드프린터에서 사용자들이 기대해왔던 신뢰성 및 견고성과 함께 뛰어난 성능을 제공합니다.
기업들은 PM4i를 통해 RFID 어플리케이션을 구동시켜 RFID 스마트 라벨을 생성기킬 수 있습니다.
PM4i는 가변 주파수 RFID Tag 를 사용함으로써 전세계에서 사용할 수 있는 라벨 인코딩과 인쇄를 동시에 할 수 있으며, 이를 통해 지역 표준에 따라 달라지는 여러 주파수 Tag 를 읽을 수 있습니다.
PM4i 는 완벽한 프린터 독립성 어플리케이션에 대한 사용자 정의 프로그램을 실행하는 "스마트 클라이언트"의 역할도 할 수 있습니다.
PM4i 프린터는 PC 필요없이 추가적인 하드웨어(예, 스캐너, 다른 프린터, 컨베이어)를 작동시킬 수 있고, 네트워크 호스트로부터 정보에 접근할 수 있으며, 기능 추가를 위한 어플리케이션으로도 변경시킬 수 있습니다.
통합 EasyLAN 이더넷, USB, 직렬 연결은 PM4i와의 기본 인터페이스 입니다.
사용자는 추가적인 EasyLAN 무선 및 산업용 인터페이스 보드를 선택할 수 있습니다.
EasyLAN 무선 인터페이스는 통합 표준 802.11b 무선 통신을 사용합니다.
네트워크를 통해 이 무선 통신은 중계된 정보의 128-bit WEP 암호화를 제공합니다.
Intermec의 유선 및 무선 기술은 보안 인쇄와 모든 환경에 대한 네트워크 인프라를 보장합니다.
PM4i 바코드프린터는 공급망 전체에 걸쳐 신속하고 정확한 데이터 수집을 위해 모든 물품들이 RFID를 통해 라벨이 주어지고, 추적된다는 것을 보장하며, 제조업, 창고업 및 물류업 용도에 적합하도록 설계되었습니다.
향후 RFID 표준으로서의 UHF Gen 2를 지원
향후 RFID 표준 발전을 지원하기위한 고유 제품기능으로 고객 투자보호
주파수 가변 UHF Tag를 인코딩하는 최초의 RFID 프린터
바코드, 판독 가능한 택스트, 그래픽을 동시인쇄
독립형 프린터 어플리케이션 지원
통합 EastLAN 이더넷, USB, 직렬 인터페이스 표준
EasyLAN 무선 인터페이스(옵션)
DESCRIPTION
Direct thermal and thermal transfer label, ticket and tag printer. Also available with RFID.
PHYSICAL CHARACTERISTICS
LxHxW : 543 x 261 x 298mm (21.38 x10.28 x 11.73 in)
Weight : 13.5 kg (29.76 lbs.)
PRINT SPECIFICATIONS
Max. Width : 104 mm (4.09 in) at 203 dpi and 406dpi; 105.7 mm (4.16 in) at 300 dpi.
Max. Length : 4095 mm (161.2 in) at 203 dpi; 2730 mm (107.5 in) at 300 dpi. 1016 mm (40 in) at 406 dpi.
RFID STANDARD & FREQUENCIES
Supports ISO 18000-6B and 18000-6C / EPC Class 1 Generation 2, 865-928 MHz radio configured to comply with local UHF FID regulations including FCC and ETSI. Contact local representative for availability in particular regions.
PRINT SPEED
100 - 200 mm/s (4 - 8 ips) variable (203 dpi)
100 - 150 mm/s (4 - 6 ips) variable (300/406 dpi)
PRINT RESOLUTION
8 dots/mm (203 dpi)
11.8 dots/mm (300 dpi)
16 dots/mm (406 dpi)
MEDIA
Type : Labels and Tags
Max/Min Width : 114.3 /25.4 mm (4.5 /1 in)
Thickness : 2.5 to 8.7 mil
Configuration : Roll-fed or fanfold
Sensing : Gap, notch, black mark, continuous
Label Roll Max Diamete r: 213 mm (8.38 in)
Label Roll Core : 38-76mm (1.5-3 in)
Type : Ribbons
Roll Max Diameter : 82 mm (3.2 in), approx. 450m
Core ID : 25.4 mm (1 in)
Type : Wax, mid-range, resin
MEMORY
Standard : 16MB Flash memory, 32MB SDRAM, 1 Compact Flash slot
Available : 1GB CompactFlash memory, multi-GB USB memory device (FAT16/FAT32 USB drivers supported)
POWER SUPPLY
AC Voltage : 90 to 265 VAC, 45 to 65Hz
PFC Regulation : IEC 61000-3-2
Power Consumption : Standby 15W; Peak 300W
OPERATING ENVIRONMENT
Ambient Operating Temperature : +5°C to +40°C (+41°F to +104°F)
Storage Temperature : -20°C to +70°C (-4°F to +152°F)
Humidity : 20 to 80% non-condensing
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
허니웰프린터 Honeywell PC42t 열전사감열 데스크탑 바코드프린터 매뉴얼HION IT
허니웰 PC42t 는 4인치 인쇄폭을 지원하는 열전사 산업용 데스크탑 바코드프린터로 중소기업을 위한 스마트 솔루션 입니다.
PC42t 바코드프린터는 12.7 mm (1/2 in) 또는 25.4 mm (1 in) 리본 코어와 110 mm (4.3 in)의 넓은 용지를 지원하며, 25.4 mm 구성은 경쟁 제품의 4배 이상인 300m (984ft) 까지의 리본 길이와 호환됩니다.
PC42t는 데스크탑 바코드프린터는 최대 4개의 포트가 내장되어 있으며 표준으로 USB 장치 및 USB 호스트, 옵션 직렬 또는 직렬 + 이더넷, 사용자가 설치할 수있는 USB, 병렬 케이블을 통해 PC42t는 거의 모든 환경에 쉽게 연결합니다.
Honeywell의 유명한 DP (Direct Protocol)와 함께 ZPL-II 및 EPL 에뮬레이션을 지원합니다.
An economical solution for light-duty thermal printing applications.
Supports a wide range of media, including 12.7 mm (1/2 in) or 25.4 mm (1 in) ribbon cores (depending on the model).
Industry-standard connectivity includes USB host and device, and options for Ethernet, parallel and serial communications.
Easy to use, with a quick-opening design for media replenishment.
Supports ESim (EPL), ZSim (ZPL-II) and Direct Protocol (DP) print languages for maximum compatibility.
PHYSICAL
Dimensions (LxWxH) : 297 mm x 226 mm x 177 mm (11.7 in x 8.9 in x 7.0 in)
Weight : 2.5 kg (5.5 lbs)
MEDIA
Max. Media Diameter : 127.0 mm (5.0 in)
Media Core Sizes : 25.4 mm (1.0 in), 38.1 mm (1.5 in)
Media Width : 25.4 mm (1.0 in) to 110 mm (4.3 in)
Min. Label Length : 9.6 mm (0.3 in)
RIBBON
Ribbon Support : Coated Side Out
Max. Ribbon Diameter : 68.0 mm (2.7 in)
Ribbon Core Sizes : 12.7 mm (0.5 in), 25.4 mm (1.0 in)
Ribbon Width: 25.4 mm (1.0 in) to 109.2 mm (4.3 in)
Max. Ribbon Length : 25.4 mm (1.0 in) core: 300.0 m (984.0 ft), 12.7 mm (0.5 in) core: 75.0 m (246.0 ft)
PRINTING
Print Resolution : 8.0 dpmm (203 dpi)
Max. Print Speed : 101.6 mm/s (4.0 ips)
Max. Print Width : 104.1 mm (4.1 in)
COMMUNICATIONS
Standard Interfaces : USB Device, USB Host
Options – Factory Installed : Internal Ethernet, serial port
Options – User Installable : Parallel adapter cable
Protocols – Network : TCP/IP-suite (TCP, UDP, ICMP, IGMP), DHCP, BOOTP, LPR, FTP, web page and Telnet 9100, IPv4
Protocols – Serial Flow Control : XON/XOFF, RTS/CTS
USER INTERFACE
Display : 1 Feed Button and LED Display
Web Page Languages : English and Simplified Chinese (Default), Spanish, Portuguese, Russian, Korean, Japanese, Thai
GRAPHICS & BAR CODES
Native Graphic Formats : 1-bit BMP, GIF, PCX, PNG
Barcode Symbologies : All major 1D and 2D symbologies are supported, including Aztec, Code 16K, Code 49, Data Matrix, Dot Code, EAN-8, EAN-13, EAN, UCC 128, Grid Matrix, HIBC 39, HIBC 128, MaxiCode, MSI (modified Plessey), PDF417, Micro PDF417, Planet, Plessey, Postnet, QR-Code, RSS-14 (variations)
ENVIRONMENTAL
Operating Temperature : +5°C to +40°C (+41°F to +104°F) 10 to 80% RH non-condensing
Storage Temperature : -40°C to +60°C (-40°F to +140°F) @ 10 to 90% RH
ELECTRICAL
Input : 100-240V AC @ 50-60 Hz, 1.5 A
Output : 24V DC, 2.5 A
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
Learn about Program Directory for IBM Ported Tools for z/OS. This program directory is intended for the system programmers who are responsible for program
installation and maintenance. It contains information about the material and procedures associated with
the installation of IBM Ported Tools for z/OS. For more information on IBM System z, visit http://ibm.co/PNo9Cb.
Visit the official Scribd Channel of IBM India Smarter Computing at http://bit.ly/VwO86R to get access to more documents.
인터맥프린터 Intermec PX4i PX6i 열전사감열 RFID 산업용 바코드프린터 매뉴얼HION IT
인터맥, EasyCoder PX (PX4i, PX6i) 시리즈 바코드프린터는 까다로운 산업환경에 맞게 설계된 견고한 금속의 고성능 프린터로, 24시간 작동을 지원합니다.
개방된 모듈식 디자인은 프린터가 쉽게 적응, 유지보수 및 서비스를 제공받을 수 있도록 합니다.
인터맥 PX 시리즈, PX4i 및 PX6i 산업용 바코드 프린터는 각각 4인치 또는 6인치의 최대 인쇄폭 기능이 특징입니다.
제조업 환경에서의 간편한 통합을 위해 설계된 PX 시리즈 산업용 프린터는 사실상 어떠한 위치라도 장착할 수 있습니다.
다기능성 폼 팩터가 라벨 자동부착기 같은 주변장치와의 연결을 용이하게 합니다.
인터맥 EasyCoder PX 시리즈 프린터는 사용자 정의 프로그램을 실행, 독립적으로 작동할 수 있어서 PC가 필요하지 않습니다.
최대 7개의 유선 및 무선 연결 인터페이스를 통해 스캐너, 스케일, 기타 프린터 및 컨베이어를 포함한 생산라인 기계장치에서 작동할 수 있을 뿐만 아니라 네트워크 호스트에서 정보에 직접 액세스할 수 있습니다.
최대의 성능 및 인쇄품질- 분당 최대 115개까지 6인치 길이의 컴플라이언스 라벨 인쇄
견고한 금속 구조로 열악한 산업환경에서도 24시간 / 7일 인쇄제공
변화하는 호스팅 환경 및 응요운야에 쉽게 적응
자동화된 라벨 부착 응용분야의 통합을 위한 모듈화 디자인
PC 비용을 들이지 않는 독립형 프린터 응용지원
IPL 또는 Fingerprinter/DP 프린터 명령 언어 선택
203, 300 또는 400 dpi 인쇄 해상도의 선택 사항을 제공하는 교체 가능한 프린트 헤드
PHYSICAL CHARACTERISTICS
LxHxW : 482 x 238 x 275 mm (19.0 x 9.4 x 10.8 in)
Weight : 12.85 kg (28.4 lbs)
PRINT SPECIFICATIONS
Max. Print Width : 112 (DT)/110 (TT) mm (4.4/4.3 in)
Max. Length :
4095 mm (161 in) at 203 dpi
2775 mm (109 in) at 300 dpi
1016 mm (40 in) at 406 dpi
RFID STANDARD & FREQUENCIES
Supports ISO 18000-6B and 18000-6C / EPC
Generation 2
865-928 MHz radio configured to comply with local UHF RFID regulations including FCC and ETSI.
Contact local representative for availability in particular region.
PRINT SPEED
100 - 300 mm/s (4 - 12 ips) for 203/300dpi
100 - 250 mm/s (4 - 10 ips) for 406 dpi
MEDIA
Labels & Tags :
Max/Min Width : 120/ 25.4mm (4.72/ 1 in)
Thickness : 2.4 to 10.0 mil
Configuration : Roll-fed or fanfold
Sensing : Gap, notch, black mark, continuous
Label Roll Max Diameter : 213 mm (8.38 in)
Label Roll Core : 38-76mm (1.5-3 in)
Ribbons :
Roll Max Diameter : 80 mm (3.15in), approx. 450m
Core ID : 25.4 mm (1”)
Type : Wax, mid-range, resin
INTERFACE
Standard :
Ethernet 10/100 Mbps
RS-232, up to 115.2 kB/s
Supported Serial Protocols :
Fingerprint/Direct Protocol : XON/ XOFF, ENQ/ACK, DTR, RTS/CTS
IPL: XON/XOFF, Intermec Std. Protocol
USB 2.0
Optional :
Parallel IEEE 1284
Industrial Interface (8 digital in/out, 4 analog relays, 1 RS232/422/485 port)
Dual Serial ports RS-232, RS-422, RS-485 and 20mA Current Loop, Applicator Interface
Wireless :
IEEE 802.11 b/g
Wi-Fi Certified, Cisco® Compatible (CCX) version 3 Certified
WEP, WPA, WPA2, 802.11x (EAPTTLS, LEAP, PEAP, FAST), 802.11i
Multiple industrial antenna options for maximized coverage
Supported Protocols : TCP/IP-suite (TCP, UDP, ICMP, IGMP, etc.), LPR/LPD, FTP, BOOTP, DHCP, HTTP, SNMPv3, SMTP.SNMP-MIB II supported (over UDP/IP), private enterprise MIB included. Supports IPv4 and IPv6
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
This is the user manual of Actron CP9680.
>> READ MORE: https://www.obdadvisor.com/actron-scanners/
Here is a detailed review of the scan tool based on my own experience, including:
- Compatibility
- Features and Functions
- Pros and Cons
Check it out to get the REVIEW and some NOTES about using the scanner.
인터맥산업용PC Intermec CV61 12.1인치 차량탑재용 산업용패널PC 매뉴얼HION IT
인터맥 CV61은 차량탑재 (지게차 또는 자동차) 모바일 컴퓨터 중에 하나입니다.
강력한 64 비트 1.8GHz 인텔 ® 아톰 프로세서가 적용된 CV61은 Windows 7 Professional 또는 Windows XP 운영 체제 중에서 선택할 수 있습니다.
또한 CV61은 메모리를 많이 차지하는 ERP 및 창고관리시스템 (WMS) 을 지원하기 위해 최대 3GB RAM을 제공합니다.
드롭 인 교체가 쉽고 경제적입니다.
현재 인터맥 CV60 차량 탑재 컴퓨터를 사용중인 경우 CV61은 가장 빠르고 쉬운 마이그레이션 경로를 제공합니다.
CV60 마운팅, 케이블 링, 키보드, 트레이, 스캐너 및 프린터와 호환되도록 설계된 CV61은 비용과 설치 시간을 절약 해줍니다.
내장 된 9-60 VDC 전원 공급 장치는 설치 비용을 낮추고 지게차 배터리가 고장 나더라도 백업을 제공합니다. 옵션으로 제공되는 외부 고전압 및성에 제거 장치 전력 변환기는 물론 기존 CV60 전력 변환기와 함께 사용할 수있는 어댑터 케이블도 제공됩니다.
또한 IT 관리자는 사용자 관리, 보안, 안티 바이러스, 방화벽, 그룹 정책 및 소프트웨어 업데이트를위한 표준 엔터프라이즈 PC 관리 도구를 지원하므로 CV61을 사용하기가 쉽습니다. CV61 옵션 인 Intermec Client Pack 터미널 에뮬레이션 및 산업용 브라우저 소프트웨어는 창고관리시스템 (WMS) 에 빠르고 안정적이며 안전한 연결을 제공합니다. 또한 Intermec 개발자 툴킷을 사용하면 다중 장치 환경에서 응용 프로그램 소프트웨어를 마이그레이션하는 데 드는 시간을 절약 할 수 있습니다.
CV61은 편안하고 친숙하며 쉽게 습득 할 수 있습니다. 매우 밝은 12.1 인치 터치 스크린 디스플레이는 희미하게 빛나는 창고 환경과 햇빛이 비치는 야외에서 쉽게 읽을 수 있습니다. 터치 스크린과 견고한 외부 백라이트 키보드는 장갑을 낀 손으로 쉽게 데이터를 입력 할 수 있도록 설계되었습니다.
안정적인 성능
CV61은 네트워크 보안, 관리 시스템 및 회사 표준과 통합되도록 설계되었습니다.
포괄적 인 네트워크 옵션으로는 시스코® CCXv4 인증을 갖춘 802.11 a / b / g / n과 낮은 신호 레벨을 경험할 수있는 지역에서도 동급 최고의 무선 범위, 로밍 안정성 및 보안을위한 통합 EDR 2.1 Class 1.5 블루투스®가 포함됩니다. 간헐적인 연결. 또한 CV61은 Intermec의 Vocollect VoiceCatalyst ™로 핸즈프리 음성 작업의 정확성, 생산성 및 안전성을 제공합니다.
극한의 온도에 견디도록 제작 된 CV61은 -20 ° C ~ + 50 ° C (-4 ° F ~ + 122 ° F)에서 작동하며 냉장 보관 및 냉동실 환경을 위해 옵션으로 제공되는 터치 스크린 디프 로스터 (-30 ° C까지 -22F).
IP66 등급은 방진 및 압력 세척 기능을 통해 하드웨어를 보호하며 사용자가 교체 할 수있는 SSD (Solid State Disk) 스토리지는 가혹하고 진동이 심한 환경에서도 데이터 무결성을 유지합니다.
CV61과 호환되는 Intermec SR61 제품군의 산업용 핸드헬드 바코드 스캐너를 사용하여 작업배정, 위치확인, 로트추적을 하거나 예외적인 관리를 할 수 있습니다. 온도 변화, 낙하, 먼지 및 날씨와 같은 거친 현실을 견딜 수 있도록 설계되었습니다. 여분의 장거리 스캐닝을위한 옵션이있어 작업자가 지게차의 자리를 떠나지 않고 멀리서도 스캔 할 수 있으며 테더형 또는 블루투스 모델 중 하나에서 사용할 수 있습니다.
PHYSICAL CHARACTERISTICS
Dimensions : 높이: 27.4cm (10.8”) x 폭: 34.3cm (13.5”) x 깊이: 8.4cm (3.3”)
Weight : 5.2 kg (11.5 lbs)
Display : 12.1”, XGA 1024x768, LED backlit
PERFORMANCE CHARACTERISTICS
CPU : Intel® Atom 64-bit D425 1.8GHz
Operating System : Choice of Microsoft Windows® 7 Professional or Windows XP Professional
Memory :
Standard 1GB DDR2 for Windows XP
tandard 2GB DDR2 for Windows 7
User-upgradeable up to 3GB memory total
WIRELESS COMMUNICATIONS
Wireless LAN : 802.11a/b/g/n
Security : WIFI Certified; WPA and WPA2 Security
Authentication : 802.1x
Cisco Compatibility : CCXv4 Certified
Antenna : Dual internal MIMO antennas or optional external primary antenna with auto-sensing feature
Bluetooth : Integrated Bluetooth 2.0+EDR, Class 1.5 (30m range)
INTERFACE
2 USB 2.0 ports with locking breakout cable, 2 RS-232 COM ports with +5V power, CAN-BUS port,
Mic/ Headset port, Stereo Speaker output, DC power input, WiFi primary antenna port with auto-sensing,
RJ45 10/100 Ethernet port, Legacy PS/2 keyboard input
>하이온아이티
주소 : 서울 금천구 가산디지털2로 165, 1304호 (백상스타타워2차)
대표번호 : 02-2038-0018 / 이메일 : hion@hionit.com
홈페이지 : http://hionsmart.com
Python is an amazing language with a strong and friendly community of programmers. However, there is a
lack of documentation on what to learn after getting the basics of Python down your throat. Through this
book I aim to solve this problem. I would give you bits of information about some interesting topics which
you can further explore.
The topics which are discussed in the book open up your mind toward some nice comers of Python language.
This book is an outcome of my desire to have something like this when I was beginning to learn Python.
If you are beginner, intermediate or even an advanced programmer there is something for you in this book.
Please note that this book is not a tutorial and does not teach you Python. The topics are note explained in
depth, instead only the minimum required information is given.
I love Python. Pandas New Era Excel!
Microsoft Excel is the industry leading spreadsheet software program, a powerful data visualization and
analysis tool but it is not suitable for processing large amounts of data so I am sharing some common things a
lot of people do in excel but using python’s pandas package, for example vlookup, filtering data or pivot table.
Pandas is a Python package providing fast, flexible, and expressive data structures designed to make working
with “relational” or “labeled” data both easy and intuitive. It aims to be the fundamental high-level building
block for doing practical, real-world data analysis in Python.
This book is a continuous work in progress. If you find anything which you can further improve (I know you
will find a lot of stuff) then kindly submit a pull request!
I am sure you are as excited as I am so let’s start!
Similar to OBD365-FAQ BMW INPA, EDIABAS, and Tool set (20)
"Trans Failsafe Prog" on your BMW X5 indicates potential transmission issues requiring immediate action. This safety feature activates in response to abnormalities like low fluid levels, leaks, faulty sensors, electrical or mechanical failures, and overheating.
𝘼𝙣𝙩𝙞𝙦𝙪𝙚 𝙋𝙡𝙖𝙨𝙩𝙞𝙘 𝙏𝙧𝙖𝙙𝙚𝙧𝙨 𝙞𝙨 𝙫𝙚𝙧𝙮 𝙛𝙖𝙢𝙤𝙪𝙨 𝙛𝙤𝙧 𝙢𝙖𝙣𝙪𝙛𝙖𝙘𝙩𝙪𝙧𝙞𝙣𝙜 𝙩𝙝𝙚𝙞𝙧 𝙥𝙧𝙤𝙙𝙪𝙘𝙩𝙨. 𝙒𝙚 𝙝𝙖𝙫𝙚 𝙖𝙡𝙡 𝙩𝙝𝙚 𝙥𝙡𝙖𝙨𝙩𝙞𝙘 𝙜𝙧𝙖𝙣𝙪𝙡𝙚𝙨 𝙪𝙨𝙚𝙙 𝙞𝙣 𝙖𝙪𝙩𝙤𝙢𝙤𝙩𝙞𝙫𝙚 𝙖𝙣𝙙 𝙖𝙪𝙩𝙤 𝙥𝙖𝙧𝙩𝙨 𝙖𝙣𝙙 𝙖𝙡𝙡 𝙩𝙝𝙚 𝙛𝙖𝙢𝙤𝙪𝙨 𝙘𝙤𝙢𝙥𝙖𝙣𝙞𝙚𝙨 𝙗𝙪𝙮 𝙩𝙝𝙚 𝙜𝙧𝙖𝙣𝙪𝙡𝙚𝙨 𝙛𝙧𝙤𝙢 𝙪𝙨.
Over the 10 years, we have gained a strong foothold in the market due to our range's high quality, competitive prices, and time-lined delivery schedules.
What Are The Immediate Steps To Take When The VW Temperature Light Starts Fla...Import Motorworks
Learn how to respond when the red temperature light flashes in your VW with this presentation. From checking coolant levels to seeking professional help, follow these steps promptly to prevent engine damage and ensure safety on the road.
Why Is Your BMW X3 Hood Not Responding To Release CommandsDart Auto
Experiencing difficulty opening your BMW X3's hood? This guide explores potential issues like mechanical obstruction, hood release mechanism failure, electrical problems, and emergency release malfunctions. Troubleshooting tips include basic checks, clearing obstructions, applying pressure, and using the emergency release.
What Could Cause The Headlights On Your Porsche 911 To Stop WorkingLancer Service
Discover why your Porsche 911 headlights might flicker out unexpectedly. From aging bulbs to electrical gremlins and moisture mishaps, we're delving into the reasons behind the blackout. Stay tuned to illuminate the road ahead and ensure your lights shine bright for safer journeys.
Fleet management these days is next to impossible without connected vehicle solutions. Why? Well, fleet trackers and accompanying connected vehicle management solutions tend to offer quite a few hard-to-ignore benefits to fleet managers and businesses alike. Let’s check them out!
What Does the PARKTRONIC Inoperative, See Owner's Manual Message Mean for You...Autohaus Service and Sales
Learn what "PARKTRONIC Inoperative, See Owner's Manual" means for your Mercedes-Benz. This message indicates a malfunction in the parking assistance system, potentially due to sensor issues or electrical faults. Prompt attention is crucial to ensure safety and functionality. Follow steps outlined for diagnosis and repair in the owner's manual.
The Octavia range embodies the design trend of the Škoda brand: a fusion of
aesthetics, safety and practicality. Whether you see the car as a whole or step
closer and explore its unique features, the Octavia range radiates with the
harmony of functionality and emotion
Things to remember while upgrading the brakes of your carjennifermiller8137
Upgrading the brakes of your car? Keep these things in mind before doing so. Additionally, start using an OBD 2 GPS tracker so that you never miss a vehicle maintenance appointment. On top of this, a car GPS tracker will also let you master good driving habits that will let you increase the operational life of your car’s brakes.
5 Warning Signs Your BMW's Intelligent Battery Sensor Needs AttentionBertini's German Motors
IBS monitors and manages your BMW’s battery performance. If it malfunctions, you will have to deal with an array of electrical issues in your vehicle. Recognize warning signs like dimming headlights, frequent battery replacements, and electrical malfunctions to address potential IBS issues promptly.
In this presentation, we have discussed a very important feature of BMW X5 cars… the Comfort Access. Things that can significantly limit its functionality. And things that you can try to restore the functionality of such a convenient feature of your vehicle.
Why Isn't Your BMW X5's Comfort Access Functioning Properly Find Out Here
OBD365-FAQ BMW INPA, EDIABAS, and Tool set
1. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 1 of 32
Frequently Asked Questions
about EDIABAS,
INPA and the Tool Set
Version 1.09
Date: 29.09.2006
Prepared by: Andreas Schandl
Responsible: Rüdiger Gall, TI-430
File: FAQ_GB.doc
Size: 32 pages
2. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 2 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Table of Contents
1 EDIABAS Error Messages .............................................................................................. 4
1.1 Driver Error................................................................................................................... 4
1.2 DirectNt.sys can’t be opened........................................................................................ 4
1.3 IFH-0002: Interface isn’t connected or doesn’t respond................................................ 4
1.4 IFH-0003: Data transmission HOST/Interface failed..................................................... 4
1.5 IFH-0010: Data transmission to control unit disturbed .................................................. 5
1.6 IFH-0013: Command not implemented......................................................................... 5
1.7 Error: EBAS32.EXE not found or illegal version! .......................................................... 5
1.8 EDIABAS error: Error (95) SYS-0005: OBJECT FILE NOT FOUND ............................ 6
1.9 Createfile_error: OPEN CONNECTION; IFH 0018- INITIALIZATION ERROR ............. 6
1.10 Battery and Ignition not recognised .............................................................................. 6
1.11 Warning when starting OBD Setup............................................................................... 7
1.12 ERROR C1015: Too Many String Variables in Job....................................................... 8
1.13 Failure: EDIABAS Fehler 159, NET-0009: TIMEOUT................................................... 8
1.14 Failure: The name of the file or folder can’t be changed............................................... 9
2 Error Message INPA...................................................................................................... 10
2.1 APLDLL or API32.DLL can’t be found. ....................................................................... 10
2.2 Error Message 0020: Incorrect or Missing Driver. The programme will be aborted!.... 12
2.3 SYS-00002: ECU variation description file not found.................................................. 12
2.4 INPA Error: Error at Compiling Abort! .................................................................... 13
2.5 IFH-0018: Inizialisation Error – INPA doesn’t work but Toolset yet............................. 14
2.6 IFH-0027: IFH not found The Programm was aborted! .......................................... 14
2.7 INPA Error: Opening Inpa – Transmission error returned a_0x2 ................................ 15
2.8 INPA Error: Only a white screen appears when you run INPALOAD.EXE.................. 15
2.9 INPA Error: DTM is no longer supported .................................................................... 16
2.10 INPA Error: Bridge16.exe can’t be initialised .............................................................. 16
2.11 Error when opening the error file abort:.................................................................. 17
2.12 Compiler: File: INPADEUTSCH***.OUT not found! ................................................. 17
3 Tool Set Error Messages .............................................................................................. 18
3.1 EDIABAS error 100: SYS-0010: INITIALIZATION ERROR ........................................ 18
3.2 EDIABAS Error 126 (only up to Ediabas V6.4.x)......................................................... 18
3.3 IFH-0006: Command not accepted and IFH-0018: Initialization Error and IFH-0038:
Interface Command not implemented......................................................................... 18
3.4 IFH-0006: Command not accepted............................................................................. 19
3.5 IFH-0009: ECU isn’t connected or doesn’t respond.................................................... 20
3.6 SYS-0002: ECU OBJECT FILE NOT FOUND............................................................ 20
3.7 SYS-0005: Controller description file not found. The programme will be aborted! ...... 20
3.8 ToolSet Error: Runtime error ’372’.............................................................................. 21
3.9 Tool Set Error: Run-time error ’5’ – Invalid Procedure Call ......................................... 21
3.10 Tool Set Problem: If an SGBD is opened, then only the hourglass appears and the
SGBD is not loaded.................................................................................................... 21
3.11 EDIABAS error 20: IFH-0010: Data transmission to control unit disturbed ................. 21
3.12 EDIABAS Error 134: API-0014: Result not found ....................................................... 22
3.13 It takes too long to load an SGBD in the Tool Set ...................................................... 22
3.14 Black Windows in the Tool Set ................................................................................... 22
4 General Questions........................................................................................................ 23
3. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 3 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
4.1 Installation of EDIABAS and INPA.............................................................................. 23
4.2 xBD-Export of SGBDs, Group SGBDs, INPA scripts and INPA configuration files using
the ECCO Web Client ................................................................................................ 23
4.3 How can I find out if the serial interface COM1 has been taken?................................ 25
4.4 How do I start INPA?.................................................................................................. 26
4.5 How can I switch between OBD and ADS interfaces? ................................................ 26
4.6 In which directory structure is OBD.ini saved?............................................................ 27
4.7 How can I find out what interface I installed with INPA? ............................................. 27
4.8 How do I find out what EDIABAS package is installed?.............................................. 27
4.9 How can I uninstall EDIABAS or INPA?...................................................................... 27
4.10 How can tell if the EDIABAS server is running as a 16-bit or a 32-bit application? ..... 27
4.11 What is the difference between EDIABASbinToolSet.exe and
EDIABAbinTool32.exe?........................................................................................... 28
4.12 What is an SGBD and what is its connection to EDIABAS? ....................................... 28
4.13 Where are the individual SGBD names and their meanings given in plain English?... 28
4.14 What is a Job? ........................................................................................................... 28
4.15 What do SGBDs with the name _xxx mean?.............................................................. 29
4.16 What is the group file used for?.................................................................................. 29
4.17 Diagnostics Index ....................................................................................................... 29
4.18 Variation Index ........................................................................................................... 29
4.19 What is the meaning of the file EDIABAS.ini? ............................................................ 29
4.20 How is the simulation file connected to the trace file?................................................. 31
4.21 Why have an XBD Generator?................................................................................... 31
4.22 What are the prerequisites for remote access via TCP/IP? ........................................ 31
4.23 What is the VC Tool and when is it used? .................................................................. 32
4.24 What is the KVP Editor?............................................................................................. 32
4. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 4 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
1 EDIABAS Error Messages
1.1 Driver Error
Message comes along with an ADS or OBD connector.
This error occurs if another program or device has taken the COM1 port of your PC.
If you want to work with EDIABAS or INPA, please make sure that the COM1 port is not
taken.
1.2 DirectNt.sys can’t be opened
This error only occurs with an NT computer if the ADS driver hasn't been installed.
The instructions for installing the ADS driver can be found in the “Installation Guide/Update
Guide” ADS_DOKU.pdf in the directory C:EDIABASHardwareADS or on the Intranet page
http://www5.muc/ti4-web/ti-430/german/themen/Diagnose.htm.
1.3 IFH-0002: Interface isn’t connected or doesn’t respond
Reason: In the Ediabas.ini file, the interface is set to STD:FUNK. However, you have
connected an ADS or OBD connector.
Solution: Modify the interface setting in Ediabas.ini.
1.4 IFH-0003: Data transmission HOST/Interface failed
Reason 1: In the Ediabas.ini file, the interface is set to STD:OBD. However, you have
connected an ADS connector.
Solution 1: Modify the interface setting.
Reason 2: The data transmission failed when sending (e.g. short circuit in the line).
Solution 2: Get rid of the short circuit, for example.
Reason 3: Connector not connected or no power supplied.
Solution 3: Check whether the connector is connected and is supplied with power.
Reason 4: The device manager has been used to disable the FIFO buffer for COM1.
Solution 4: In the device manager (Windows XP: Enter “Start” “Control Panel”
“System” “Hardware” “Device Manager” Ports (COM & LPT)), and then
select COM1 from the ports. Then under the “Port Settings” tab, select
“Advanced”. There must be a check-mark by “Use FIFO buffers” and “8” must be
selected for the receive buffer and transmit puffer.
5. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 5 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
1.5 IFH-0010: Data transmission to control unit disturbed
This problem can occur with XP computers with the OBD interface.
Reason: With Windows XP, it is not possible to automatically set the receive and transmit
buffers using OBDSetup.exe, like in Windows NT.
Solution: Set the receive and transmit buffers to 8 as shown in the following:
Use Start My Computer Control Panel System Hardware Device
Manager Ports (COM & LPT) and then click with the right mouse button to call
up the properties of the COM port that is being used. Under the Port Settings tab,
set the Data bits of the receive and transmit buffers to 8.
1.6 IFH-0013: Command not implemented
Reason: The error was caused by another programme that accessed the COM1 interface.
Usually, the “HotSync” programme is installed on the computer for the organiser.
Solution: Check the programmes that are started automatically when Windows is started.
1.7 Error: EBAS32.EXE not found or illegal version!
This error occurs if the path variable is set with the path C:EDIABASBIN in the system and
user variables (Start My Computer Control Panel System Advanced and then in
the "Environment“ tab).
6. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 6 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
1.8 EDIABAS error: Error (95) SYS-0005: OBJECT FILE NOT FOUND
Reason 1: No SGBD in C:EDIABASECU
Solution 1: Copy the SGBD into the Ecu directory.
Reason 2: No group file in C:EDIABASECU (for group call)
Solution 2: Copy the group file to C:EDIABASECU
Reason 3: No path definition C:EDIABASBIN
Solution 3: Set the system variable (see 2.1)
Reason 4: Incorrect path definition in EDIABAS.INI
Solution 4: Set the EcuPath path in Ediabas.ini to C:EDIABASECU
Reason 5: The SGBD name contains reserved characters or is too long. Only 8 characters
are allowed (a-z, A-Z, 0-9, "_").
1.9 Createfile_error: OPEN CONNECTION; IFH 0018- INITIALIZATION
ERROR
ADS Interface:
The following error appears when Ediabas is started: Createfile_error: OPEN
CONNECTION
OBD Interface:
The following error appears when Ediabas is started: Error 28: IFH 0018- INITIALIZATION
ERROR. (Also see Section 3.3)
Reason: Ediabas is attempting to access port COM1. However, the port doesn't exist, or it
has been taken by another programme (e.g. HotSync from Palm, infrared).
Solution: Install a COM1 interface or free it.
1.10 Battery and Ignition not recognised
Reason: With a Dell Latitude D600 laptop, pin 9 has no function and it is therefore not
able to correctly recognise the battery status.
Solution 1: Use OBD via USB, see C:EDIABASBININI.PDF Chapter 2.2 for this.
Solution 2: The laptop is connected to the docking station.
Solution 3: Workaround for the OBD driver as of February 2004: A file “OBD.ini” must be
created in the directory C:WINDOWS for Windows XP, or alternatively
C:WINNT for Windows NT, with the following entry. This is because with
UBATT=OFF, the battery status is not determined via hardware, but is
permanently set to “Battery voltage available”. Also see OBD_DOKU.pdf in the
EdiabasHardwareOBD directory.
Entry in OBD.ini:
[OBD]
7. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 7 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
UBATT=OFF
1.11 Warning when starting OBD Setup
A warning occurs when starting C:EDIABASHARDWAREOBDOBDSetup.exe. After You
want to start Tool Set or INPA You will get the following error message:
Reason: The value of the variable DWORD (here RxFIFO) can not be set by
OBDSetup.exe.
Solution: You have to set the value of the DWORT in the registry. You have to open the
Regedit by using Start Ausführen… enter regedit OK. Choose the
following path in the regedit: HKEY_LOCAL_MACHINE System
CurrentControlSet click on Services. On the right side of the window You can
cklick on the name of the DWORd value which is defective (here RxFIFO). Enter
the value 8 with the base hexadecimal. Click Ok an close the regedit. Now You
can start the Tool Set or INPA without an error.
If You have warnings for other DWORDs when startig OBDSetup.exe, You will
have to set the value of the coloum „Expected“ for the wrong value in the registry.
8. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 8 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
1.12 ERROR C1015: Too Many String Variables in Job
Reason: In a job only a maximum of 6 string-variables is acceptable.
Solution: You have to reduce the number of variables.
1.13 Failure: EDIABAS Fehler 159, NET-0009: TIMEOUT
9. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 9 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The configuration for the remotehost is false.
Solution 1: Set the corresponding networkname for the remotehost in the configuration file
EDIABAS.INI.
Reason 2: The inface-cable on the OPPS is not correct.
Solution 2: You need a special OPPS-Cable for the connection with the CAN-BUS. (since
type series L6)
Reason 3: In the remotecontrol the OPPS-interface is used by default (since EDIABAS 7.0).
The remotecontrol between two PC’s is not possible with this configuration.
Solution 3: Close all diagnosticapplications and EDIABAS-Processes that are running and
open the file “remote_mit_pc.bat” in the directory C:EDIABASbin.
1.14 Failure: The name of the file or folder can t be changed
Reason: EDIABAS or another component of EDIABAS is still open.
Solution: You have to shut down the diagnosticapplication and EDIABAS. If necessary, the
fileexplorer and the editors which access the EDIABAS-Directory have to close
as well.
10. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 10 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
2 Error Message INPA
2.1 APLDLL or API32.DLL can’t be found.
When calling INPA under Windows NT, the following error messages appear:
Reason 1: The path C:EDIABASBIN has not been set in the ‘Path’ system variable.
Solution with Windows NT:
Set the system variable: Please log into your system as the administrator with administrator
rights. Use Start My Computer Control Panel to call the “System” menu. In the
“Environment” tab, double click the system variable ‘Path’.
11. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 11 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Go to the end of the field value. There, enter a semicolon and then enter the path
C:EDIABASBIN. Click “Set” and “OK”.
Solution with Windows XP:
Set the system variable: Please log into your system as the administrator with administrator
rights. Use Start Control Panel to call the “System” menu. Under “Advanced” and the
“Environment” tab, double click the system variable ‘Path’.
Go to the end of the variables field value. There, enter a semicolon and then enter the path
C:EDIABASBIN.
Click “OK”.
Completely restart your computer!!! (Don’t login under a new name or the like.) It should no
longer be a problem to call INPA.
Reason 2: Ediabas is not installed, only INPA is.
Solution 2: Install Ediabas.
When calling INPA under Windows 95, 98, the following error message appears:
12. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 12 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason: The path C:EDIABASBIN has not been set in the ‘Path’ system variable.
Solution: Set the system variable:
Open the file Autoexec.bat in the directory C: by clicking it with the right mouse key with the
shift key pressed, and then select “Open with”. The best thing is to use the Notepad to
display the file.
Now, at “path”, enter the path c:ediabasbin.
Save the change and close the file.
Completely restart your computer!!! (Don’t login under a new name or the like.)
2.2 Error Message 0020: Incorrect or Missing Driver. The programme will
be aborted!
Conditions:
You have access to smuc0900sg. You are linked to this drive and would like to start an
INPA script.
Reason 1: Missing Ediabas.ini file in C:Winnt.
Reason 2: You are not connected to the controller.
For developers: Simulation is not switched on in the Ediabas.ini file.
Solution: Copy the Ediabas.ini file from C:EdiabasBin to C:Winnt.
2.3 SYS-00002: ECU variation description file not found.
The error occurs when starting an INPA script.
13. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 13 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The *.prg SGBD is not located in the path C:EdiabasEcu.
Solution 1: Copy the *.prg SGBD into the ECU directory.
Reason 2: The external table T_GRTB.prg doesn’t exist in the directory C:EDIABASECU
or it is obsolete.
Solution 2: Copy the file into the ECU directory or update the external table using the ECCO
Web Client.
2.4 INPA Error: Error at Compiling Abort!
The following error message appears when starting an INPA script.
Reason 1: An INPA script with the ending IPO was started by the programme INPA.EXE
instead of by the programme INPALOAD.EXE.
Solution 1: Only start INPA scripts that end with IPO with INPALOAD.EXE.
Reason 2: The selected INPA script doesn’t exist in the C:INPASGDAT directory.
Solution 2: Update the INPA scripts using the ECCO Web Client.
Reason 3: INPA Version 5.0.1: The INPA script *.IPO can’t be started with a double-click in
the directory C:INPASGDAT*.IPO.
Solution 3: Update to Version 5.0.2.
Reason 4: INPA Version 5.0.1: The desktop link of an INPA script doesn’t work.
Solution 4: The target path must be expanded to include the INPALOAD path. To do this,
click the desktop link once with the right mouse button and go to ‘Properties’.
Expand the target path to include C:INPABININPALOAD.exe for Windows NT
(see Fig.) and C:EC-AppsINPABININPALOAD.exe for Windows XP.
14. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 14 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Grund 5: The file startger.ipo of the german installation and the file startus.ipo of the
english installation don’t exist in the directory INPACFGDAT.
Lösung 5: Install INPA once again.
2.5 IFH-0018: Inizialisation Error – INPA doesn’t work but Toolset yet
The error occurs if a SGBD is running by INPA or CASCADE. If the same SGBD is loaded in
the Toolset it will not occure an inizialisation error.
Reason 1: The communications port COM1 doesn’ exist, but COM3 yet. The Toolset is
working without the inizialisation error, because the file OBD.ini exists in the
directory C:Ediabasbin. But the file OBD.ini has to exist in the direcory
C:Windows.
Solution 1: Copy the file OBD.ini in the directory C:Windows or create a new one. (Creation
of OBD.ini q.v. 3.3).
Grund 2: q.v. 3.3
Lösung 2: q.v. 3.3
2.6 IFH-0027: IFH not found The Programm was aborted!
The error occurs when starting INPA.
15. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 15 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The setting for the interface in the configuration file Ediabas.ini doesn’t exist.
Solution 1: Please do the settings for the interface e.g.:
Interface = STD:OBD
Reason 2: The setting for the interface in the configuration file Ediabas.ini is
Interface=STD:OMITEC, but the OMITEC driver isn’t installed correctly.
Solution 2: Install the OMITEC driver with the instructions
InstructionforOMITECInstallation.pdf via the GIS server.
Reason 3: The setting for the interface in the configuration file Ediabas.ini is
Interface=OMITEC, but the correct setting is Interface=STD:OMITEC.
Solution 3: Please do the settings for the interface Interface=STD:OMITEC.
Reason 4: The old OMITEC driver wasn’t uninstalled correctly.
Solution 4: Please uninstall the old OMITEC driver with the instructions
InstructionforOMITECInstallation.pdf via the GIS server.
2.7 INPA Error: Opening Inpa – Transmission error returned a_0x2
Reason: During the installation of Ediabas/Inpa, the configuration “Without configuration”
was selected.
Solution: When running the installation programme, select a configuration, e.g. “BMW
Plant 1.1 Munich”.
2.8 INPA Error: Only a white screen appears when you run INPALOAD.EXE.
16. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 16 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: The api.dll or api32.dll file has been manually copied into the WINDOWS
directory with Windows XP and into the WINNT directory with Windows NT.
Solution 1: Delete the file api.dll or alternatively api32.dll from the WINDOWS or alternatively
the WINNT directory. The file may only exist in the directory EDIBASBIN.
Reason 2: You have installed the 32-bit version of INPA (as of Version 5.0.1) and have not
performed an update of the INPA scripts.
Solution 2: Update the INPA scripts using the ECCO Web Client.
2.9 INPA Error: DTM is no longer supported
Reason: This error message appears if INPA.INI has been copied from Version 4.7.7 to
Version 5.x.x.
Solution: Since it can’t be excluded that even more files from the old version have been
mixed with the new ones, the old ones must be deleted, or alternatively
reinstalled (see Chapter 5). Reinstall INPA using the Global Information Service
(GIS) https://gis.bmw.com.
2.10 INPA Error: Bridge16.exe can’t be initialised
17. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 17 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Reason 1: A 16-bit INPA script has been started with the 32-bit version of INPA (as
of Version 5.0.1).
Solution 1a): Update the INPA scripts using the ECCO Web Client.
Solution 1b): Convert the INPA script to the standard ‘includes’ for the 32-bit version.
To do this, contact the respective person responsible for INPA at TI-43x
(see smuc0900sgrefReferenzReferenz.inp)
Reason 2: A 16-bit DLL has been found, which means the developer of the INPA
script is using a 16-bit DLL.
Solution 2: The developer of the INPA script must convert the DLL to 32-bit.
2.11 Error when opening the error file abort:
Reason: This error occurs with Windows XP because the user doesn’t have the correct
rights to change files in the directory C:INPABin.
Solution: The user needs “Power user” rights or the user needs the appropriate write rights
to the “INPA” directory.
2.12 Compiler: File: INPADEUTSCH***.OUT not found!
Reason: The path C:EDIABASBIN has not been set in the ‘Path’ system variable.
Solution: Set the path C:EDIABASBIN in the ‘Path’ system variable. (q.v. chapter 2.1).
18. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 18 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
3 Tool Set Error Messages
3.1 EDIABAS error 100: SYS-0010: INITIALIZATION ERROR
Reason: This message comes when an SGBD has an automatic concept switch between
multiple diagnostics logs and is not connected to the controller.
Solution: Connect the controller.
3.2 EDIABAS Error 126 (only up to Ediabas V6.4.x)
Reason: This error message appears if you start the Tool Set while an INPA script is
running. This is also true the other way round. The reason for this is that only one
programme can access EDIABAS at a time.
Solution: Therefore, before you start the ToolSet, you must exit INPA!!!
3.3 IFH-0006: Command not accepted and IFH-0018: Initialization Error and
IFH-0038: Interface Command not implemented
Errors IFH-0006 and IFH-0018 occur if any SGBD is loaded in the Tool Set. Error IFH-0038
is generated when loading the utility file into the Tool Set.
Reason 1: The error was caused by another programme that accessed the COM1
interface. This programme could be “HotSync” for Palm or “ActiveSync”
for lpack.
Solution 1: Check the programmes that are started automatically when Windows is
started (see Chapter 4.1).
Reason 2: The COM1 interface is taken by a serial printer.
Solution 2: Uninstall the printer.
Reason 3: The infrared interface is active.
Solution 3: Deactivate the infrared interface.
Reason 4: There is no COM1 interface (COM3 instead, for example)
Solution 4a): Install the COM1 interface.
Solution 4b): Create a file with the name OBD.ini and make the following entry to set
the existing serial interface (COM3, for example):
19. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 19 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
[OBD]
Port = Com3
The file OBD.ini must be saved in the directory C:WINDOWS for
Windows XP or in directory C:WINNT for Windows NT up to the Ediabas
Package 1.3 and as of Ediabas Package 1.4 in directory
C:EDIABASBIN. The current version of the Ediabas Package can be
seen in the files C:EDIABASversion.txt or C:EDIABASpackage.pdf.
Reason 5: Only for IBM notebooks: The COM1 interface is reserved for the docking
station; the COM3 interface is installed instead.
Solution 5a): see solution 4b:
Solution 5b): Set the COM3 port to COM1: In the device manager (Windows XP:
Select “Start” “Control Panel” “System” “Hardware” and then
select COM3 from the ports under the menu item “Device Manager”.
Then use the right mouse button “Properties” “Port Settings”
“Advanced” to reach the “Advanced Settings for COM3”. Set COM1 in the
COM Port Number. The message that COM1 is already taken can be
ignored in this case.
Reason 6: The old OMITEC driver wasn’t uninstalled correctly.
Solution 6: Please uninstall the old OMITEC driver with the instructions
InstructionforOMITECInstallation.pdf via the GIS server.
3.4 IFH-0006: Command not accepted
This error occurs if a SGBD is loaded in the Tool Set when the OBD connector is being used.
Reason 1: ODB has actually been set as the interface in Ediabas.ini, but the Tool Set uses
the multi-instance with another interface, e.g. K-Line. The setting for the multi-
instance and the interfaces used here is made in the file Tool32.ini in the
directory C:Windows (for Windows XP) or alternatively C:Winnt (for Windows
NT). Then, the entries in Tool32.ini, or alternatively the interface apply and not
the ones in Ediabas.ini. The use of multi-instance in the Tool Set is identified in
the title bar, for example with “Tool32:1”, for single multi-instance.
Solution 2: Enter the interface that is being used in Tool32.ini or disable multi-instance with
the entry “No”.
Reason 2: A SGBD is loaded in the Tool Set when the diagnosis protocol UDS is being
used. For UDS-SGBDs You have to use the interface OMITEC but in the
EDIABAS.ini the setting fort he interface ist „STD:OBD“.
Solution 2: Change the setting for thr interface to „interface = STD:OMITEC“ in the
EDIABAS.ini file. The OMITEC connector has to be stressed by the voltage (blue
blinking). If the connector can’t be stressed by the voltage and You want to load
the SGBD yet, You will use the simulation mode. You can activate the simulation
mode e.g. with the menue „configuration -> EDIABAS“. Notice, if you want to use
the simulation mode, a simulation file for the interface will have to exist in the
simulation path.
20. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 20 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
3.5 IFH-0009: ECU isn’t connected or doesn’t respond
Reason 1: In the Ediabas.ini file, the interface is set to STD:ADS. However, you have
connected an OBD connector.
Solution 1: Modify the interface setting.
Reason 2: The ignition is switched off.
Solution 2: Switch the ignition on.
Reason 3: The device manager has been used to disable the FIFO buffer for COM1.
Solution 3: In the device manager (Windows XP: Enter “Start” “Control Panel”
“System” “Hardware” “Device Manager” Ports (COM & LPT)), and select
COM1 from the ports and under the “Port Settings” tab, select “Advanced”. There
must be a check-mark by “Use FIFO buffers” and the highest possible setting
must be selected for the receive buffer.
3.6 SYS-0002: ECU OBJECT FILE NOT FOUND
Reason 1: If the external table T_GRTB.prg doesn’t exist in the directory C:EDIABASECU
the error message will be displayed when You execute the job
IDENT_FUNKTIONAL of a functional SGBD.
Solution 1: You have to download the external table using the ECCO Web Export and copy it
in the directory C:EDIABASECU.
Reason 2: The SGBD, which You want to start doesn’t exist in the directory
C:EDIABASECU or is an old one.
Solution 2: You have to download the SGBD using the ECCO Web Client and copy it in the
directory C:EDIABASECU.
3.7 SYS-0005: Controller description file not found. The programme will be
aborted!
Reason 1: The SGBD is not located in the path C:EdiabasEcu.
Solution 1: Copy the SGBD into the Ecu directory.
Reason 2: This error occurs if the EcuPath in Ediabas.ini (C:EdiabasBin) isn’t set to
C:EDIABASECU.
Solution 2: Set the correct path.
21. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 21 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
3.8 ToolSet Error: Runtime error ’372’
The following error message appears.
Reason: The old version msflxgrd.ocx exists under c:winntsystem32.
Solution: msflxgrd.ocx under c:Ediabasbin must be registered. To do this, select “Start”
“Run…” and execute regsvr32 :ediabasbinmsflxgrd.ocx in the window and
confirm with “OK“.
The following must be entered for Windows XP: “regsvr32 c:ediabasbin
msflxgrd.ocx“
3.9 Tool Set Error: Run-time error ’5’ – Invalid Procedure Call
Reason: The Tool Set was started twice in a very short period of time.
Solution: Close all Tool Set processes that are running and start the Tool Set again with
only one double-click.
3.10 Tool Set Problem: If an SGBD is opened, then only the hourglass
appears and the SGBD is not loaded.
Reason: An old version Richtx32.ocx exists under c:winntsystem32.
Solution: Richtx32.ocx under c:Ediabasbin must be registered. To do this, select “Start”
“Run…” and execute “regsvr32 :ediabasbinrichtx32.ocx“ in the window and
confirm with „OK“.
The following must be entered for Windows XP: „regsvr32 c:ediabasbin
richtx32.ocx“
3.11 EDIABAS error 20: IFH-0010: Data transmission to control unit
disturbed
Reason 1: When using the EDIC card, the error message is issued when executing the
IDENT job.
Solution 1: Changes must be made in the file “XEDICC.ini” in the "...EdiabasBin" directory.
There, the parameters set for high-speed must be commented out and the
parameters for low-speed must be enabled:
; highspeed:
;Interface=1;
;Presc=0x01;
;SJW=0x01;
;TSEG1=0x08;
;TSEG2=0x07;
22. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 22 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
; lowspeed:
Interface=2;
Presc=0x0A;
SJW=0x02;
TSEG1=0x05;
TSEG2=0x02;
Reason 2: A SGBD is loaded in the Tool Set when the diagnosis protocol UDS is being
used. You use the interface OMITEC but the connector isn’t stressed by the
voltage (no blue blinking).
Solution 2: Connect the OMITEC wit the vehicle. The OMITEC connector has to be stressed
by the voltage (blue blinking). If the connector can’t be stressed by the voltage
and You want to load the SGBD yet, You will use the simulation mode. You can
activate the simulation mode e.g. with the menue „configuration -> EDIABAS“.
Notice, if you want to use the simulation mode, a simulation file for the interface
will have to exist in the simulation path.
3.12 EDIABAS Error 134: API-0014: Result not found
The error occurs if a SGBD is loaded in the Tool Set when the diagnosis protocol UDS is
being used and the Job FS_LESEN is being executed.
Reason: You use the setting “read error like INPA”, but the Toolset can’t support the
function yet for UDS-SGBDs.
Solution: Please remove the setting “read error like INPA” in the menue “configuration ->
Toolset”.
3.13 It takes too long to load an SGBD in the Tool Set
Loading motor or transmission SGBDs takes an above average amount of time.
Reason: Large SGBDs often contain many and extensive tables and their information has
to be loaded.
Solution: Under the Configuration menu item in the Tool Set and then Tool Set, the
checkmark by the selection of table information must be removed.
3.14 Black Windows in the Tool Set
After loading a SGBD one or more windows of the Tool Set are black windows.
Reason: The registration of the richtextbox is invalid.
Solution: You have to register the richtextbox. Execute the batch file REGSVR32.BAT in
the directory C:Ediabasbin.
23. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 23 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
4 General Questions
4.1 Installation of EDIABAS and INPA
The Installation of EDIABA, INPA and NFS have to be done webbased via the Global
Information Service (GIS). You can reach the GIS homepage with the following link:
https://gis.bmw.com/.
In the forum „BMW Standard Tools Werk“ You can find the installation data of EDIABAS,
INPA and NFS. The path ist shown below:
BMW Standard Tools Werk
Standard Tools / Tool Installation Werk
EDIABAS
INPA
NFS
For acces rights for the GIS forum „BMW Standard Tool Werk“ send an mail to
Referenz@bmw.de stating the name the Q/QX number an the reason. We can give access
rights for this forum only for colleagues from the T departements. Colleagues from other
departments and supplieres can get the installation via the GIS forum „BMW Standard Tools
Entwicklung“. You can apply for access rights using the following link:
https://gis.bmw.com/gis/d/toolsantrag.htm.
Please pay attention to the intallation instructions which You can get in the same directories
of the installation data. After the intallation You have to download the SGBDs, INPA scripts,
Group SGBDs, INPA configuration files and external tables using the ECCO Web Client.
Which data You have to download is described in the following chapter 4.2.
4.2 xBD-Export of SGBDs, Group SGBDs, INPA scripts and INPA
configuration files using the ECCO Web Client
The update of SGBDs, group SGBDs, external tables, INPA scripts and INPA configuration
files can be done webbased using the ECCO Web Client.
You can apply for acces rigths for ECCO at the user service center (Tel. 089-382-55555)
stating Your valid Q/QT/QX number.
You can reach the homepage of the ECCO Web Clients with the following link:
http://www6.muc/ppea. After login You have to select the link xBD Export in the navigation
bar and You can see the search screen. You have the possibility to search for a single file or
search for all files assigned to a certain type serie or search for a several release periods.
24. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 24 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
If You have installed EDIABAS You will need following files:
• SGBD_Revisionen
• GRP_SGBD_Revisionen
• ExterneTabelle_Revisionen
If You have installed INPA You will need following files:
• SGBD_Revisionen
• GRP_SGBD_Revisionen
• ExterneTabelle_Revisionen
• Inpa_Script_Revisionen
In the column „Verfügbare Dateitypen“ You have to select the data types. These column is
very important vor the export of the files, i.e. the data types which are selected will be
exported. Please pay attention on the correct selection.
If You have installed EDIABAS You will select the following data types:
• SGBDprg_english or SGBDprg_deutsch
• SGBDgrp
• EXTABprg_english or EXTABprg_deutsch
If You have installed INPA You will select the following data types in addition to the data
types above:
• INPAipo_english or INPAipo_deutsch
25. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 25 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
• Select also „Benutzereinst. verwenden“
• Select also „INPA-Konf.-Dateien“
After the download of the necessary files You have to copy the files in the right directories:
EDIABAS data:
1 …EDIABASECU
• SGBDen: SGBDprg_deutsch alle *.prg-Dateien
• externe Tabellen: EXTABprg_deutsch T_GRTB.prg, T_PCOD.prg
• Gruppen-SGBDen: SGBDgrp_deutsch alle *.grp-Dateien
INPA data:
1 …INPASGDAT
• INPA scripts: INPAipo_english all *.ipo files
1 …INPACFGDAT
• INPA-Konfig-Files: INPA_Konfig_xBD_Download_eng.zip
all *.ger files or *.eng files
Inpa.ini file
ger = german INPA config, eng = english INPA config
If You have problems with the xBD Export using ECCO Web Client please call the user
service center: Tel. 089-382-55555 or send a mail to ECCO hotline: ecco.hotline@bmw.de.
4.3 How can I find out if the serial interface COM1 has been taken?
There is a way to find out if the serial interface, for example COM1, has been taken, but it is
not possible to find out what programme has taken the interface.
As described in the respective sections of Chapter 3, the programmes that most often take
COM1 are HotSync for the Palm and ActiveSync for the lpack or a Nokia software. In order
to establish whether these programmes are automatically started when you start the
computer, please check your ‘Autostart’ settings. Do this by making sure that these
programmes don’t appear in the following directories:
- C:Documents and SettingsAll UsersStartmenuProgramsAutostart
- C:Documents and SettingsYour QX NumberStartmenuProgramsAutostart
Another way to check the utilisation of COM1 is to look in the system information. The
system information can be run with the DOS command winmsd in an input prompt (Start
Run… enter winmsd OK). Here, it is important that you only run winmsd if the Ediabas
server is closed. Under the path System Summary Components Ports Serial, the
information about the active serial ports COM1, COM2, and so on will be shown if they exist.
The current value can be seen in the element “Busy”. If this value is “No”, then the interface
is free, and if it is “Yes”, then the interface has been taken by a programme. You can’t find
out what programme it is here.
26. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 26 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
4.4 How do I start INPA?
Start Inpa using Inpaload.exe in C:InpaBin or alternatively C:EC-AppsInpaBin or use
Start All Programs EDIABAS INPA ELDI NCS NFS INPA(_.IPO) to start the general
reworking programme. This corresponds to calling Inpaload.exe under
smuc0900sgInpaBin or alternatively C:InpaBin.
4.5 How can I switch between OBD and ADS interfaces?
Prerequisite:
The appropriate driver must be installed for the interface that you want to use. In the
installation guide for INPA (http://smuc0900/TI-430 or http://smuc0900/TI-430 under Subjects
EDIABAS /INPA EDIABAS or INPA), you can look up how a driver is installed.
Now, you can change the interface directly in the file Ediabas.ini (C:EDIABASBIN). You
only have to make the appropriate change to the line where the interface is entered.
Interface = STD:OBD, i.e the OBD interface will be used.
Interface = ADS, i.e the ADS interface will be used.
27. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 27 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
For the case that OBD is being used via USB, an additional entry is necessary in OBD.ini.
See C:EDIABASBININI.PDF for this.
4.6 In which directory structure is OBD.ini saved?
If the OBD.ini file exists, then in order to not run the interface via COM1 by default (compare
to 1 i), then the OBD.ini file must be saved in the directory C:WINDOWS for Windows XP
or in directory C:WINNT for Windows NT up to the Ediabas Package 1.3 and as of Ediabas
Package 1.4 in directory C:EDIABASBIN. The current version of the Ediabas Package can
be seen in the files C:EDIABASversion.txt or C:EDIABASpackage.pdf.
4.7 How can I find out what interface I installed with INPA?
To do this, you have 2 possibilities:
1. Call Start All Programs EDIABAS INPA ELDI NCS NFS EDIABAS Tool32. In
the configuration menu, select Ediabas. There, you will find the desired information in the
interface line.
2. However, you can also check in the Ediabas.ini (C:EDIABASBIN) to see what
interface you have installed. For the OBD interface, you will find the line ‘Interface =
STD:OBD’ and for the ADS Interface the line ’Interface = ADS’.
4.8 How do I find out what EDIABAS package is installed?
The version of the currently installed Ediabas package can be seen in the files
C:EDIABASversion.txt or C:EDIABASpackage.pdf.
4.9 How can I uninstall EDIABAS or INPA?
You uninstall INPA by deleting the Ediabas and Inpa folders under C:.
Reason: No registry entries are made during the installation.
4.10 How can tell if the EDIABAS server is running as a 16-bit or a 32-bit
application?
Under Windows 95 and 98, the EDIABAS server runs as a 16-bit version. The can be
recognised by the yellow E in the task bar.
28. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 28 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
Under Windows NT4 and XP, the EDIABAS server runs as a 32-bit version. This can be
recognised by the green E in the task bar.
Note:
As of 2003, there is the EDIABAS Version 6.4. This can also run as a 32-bit application
under Windows 95/98 and XP.
4.11 What is the difference between EDIABASbinToolSet.exe and
EDIABAbinTool32.exe?
Tool32.exe is current and when it is started, the Ediabas server will start as a 32-bit
application. ToolSet.exe is an old version and is required under Windows 3.11.
4.12 What is an SGBD and what is its connection to EDIABAS?
The controller description files (SGBD) contain the controller-specific know-how. Each SGBD
contains the order telegram of the respective controller and decodes its reply telegrams. In
the process, the raw data (bytes) is converted into directly useable variables (Data types: int,
long, real, string), i.e the error code is converted into error text.
For each controller variation, there is exactly one variation-specific SGBD.
The SGBDs are loaded and interpreted by the EDIABAS runtime system by an application
programme when the order is issued. The file name of the SGBD (without extension) is the
name with which the application programme addresses a controller variation or controller
group.
4.13 Where are the individual SGBD names and their meanings given in
plain English?
Click the “Show” Version List SGBD button on the ”Dienste Tool” interface. There will be a
list of all SGBDs by name with the current version number, the person responsible at BMW,
and the name of the associated controller. It is only possible to access the version list when
the network is in operation or it can be viewed at smuc0900ReferenzReferenz.sgbd.
4.14 What is a Job?
Jobs are services that EDIABAS provides. They aren't hard coded in EDIABAS, but are a
main component of each SGBD.
Each job has a fixed name and any number of results. Jobs are independent of each other.
There is no data exchange between jobs.
A job corresponds to a function with one complete order. It usually reads data from a
controller, analyses it and returns results that can be used directly by different applications.
A job normally works with one diagnostics telegram (multiple in exceptional cases).
29. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 29 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
4.15 What do SGBDs with the name _xxx mean?
SGBDs that begin with “_” (e.g. _LWS5), contain jobs that are only intended for development
(e.g.: writing the ident data). These SGBDs are not used in production or in customer service.
4.16 What is the group file used for?
Among other things, INPA uses group files to select the respective SGBD. The group
identifies the controller and starts the corresponding SGBD. The choice is made using the
diagnostics, and as of E65 using the variation index in addition.
The group files are located in C:EDIABASECU and have the following naming convention:
D_00xx.grp were assigned up to the E65; xx = the controller address; For example:
D_0032.grp = transmission. The name D_??????.grp is assigned after the E65 and is
legible; for example D_KLIMA.grp or D_MOTOR.grp, etc.
Updating the group files as of the E65 has changed since February 2004. The table with the
information about which controller must load which SGBD, depending on the diagnostics and
variation index, was moved from the group file to an external table. At runtime, the swapped-
out table C:ECUT_GRTB.prg is used. Therefore, it is now only necessary to update this
table and not D_??????.prg.
Additional Information for SGBD Developers:
In the file STD_GRTB.b2s, the diagnostics and variation indexes of the individual SGBDs
can be seen as well as the group file to which the respective SGBD is assigned. You can
find the file STD_GRTB.b2s on drive smuc0900sg in directory ReferenzEdiabasInclude.
4.17 Diagnostics Index
a) Who creates it? Reinhold Drexel, TI-430
b) What is it used for? Identification of the controller
c) When does it change? When a new SGBD is due
4.18 Variation Index
a) Who creates it? Data handling team
b) What is it used for? Identification of the ECU
c) When does it change? When the SGBD and/or the PABD changes (PABD, if
something in ECU programming changes), e.g. if the
authentication changes or a timing has changed).
4.19 What is the meaning of the file EDIABAS.ini?
Ediabas.ini is the configuration file. Normally, no changes must be made here after the
installation. One reason for a change to Ediabas.ini is, for example, if you want to work with
a simulation file, i.e. there doesn’t have to be a ECU.
The Ediabas.ini can be found in the EdiasbasBin directory.
EcuPath:
The group files (d_*.grp) and SGBDs (*.prg) are found in the path given for EcuPath. In the
developer versions, it also contains *.b2v, *.b2s and *.txt files.
SimulationPath:
30. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 30 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
The path given in the SimulationPath is where the simulation files are located for groups
(d_*.sim) and for SGBDs (*.sim), which are only relevant to SGBD and INPA developers.
TracePath:
If ApiTrace and/or lfhTrace are activated, then the traces will be stored there with api.trc and
ifh.trc.
TraceSize:
You can set the size of the trace files ApiTrace and IfhTrace. If 1024 is set, then the
maximum size of the file is 1 MB; for 512, it is a maximum of 500 KB.
ApiTrace:
The ApiTrace file is activated by replacing the zero with a number from 1 to 7. The api.trc file
contains the job and result names with their data. If ApiTrace is not needed, this should be
set to zero to increase the performance of EDIABAS. You can find information about the
trace level in the Ediabas documentation.
IfhTrace:
The lfhTrace file is activated by replacing the zero with a number from 1 to 3. The ifh.trc file
only consists of the telegrams that have been sent (INPUT) and received (OUTPUT). If
lfhTrace is not needed, this should be set to zero to increase the performance of EDIABAS.
Simulation:
Simulation is used to check the SGBDs and INPA scripts without being directly connected to
a ECU. This function is activated by changing the zero to 1.
Interface:
You can directly change the interface here. You only have to make the appropriate change
to the line where the interface is entered.
Example:
Interface = STD:OBD, i.e the OBD interface will be used.
Interface = ADS, i.e the ADS interface will be used.
The prerequisite is to have the appropriate driver installed for the interface.
Excerpt form the Ediabas.ini file:
31. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 31 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
4.20 How is the simulation file connected to the trace file?
There is one simulation file for each ECU. In this file are the ECU’s request and reply
telegrams. This file has the same name as the ECU description file, however it has the
ending “*.SIM” (e.g. DME31.SIM).
There is also a separate simulation file for each interface that is to be simulated. The
filename is made up of the name of the interface with the ending “*.SIM” (e.g. EDIC.SIM).
The setting of the EDIABAS configuration element called Interface will be used as the
interface name. The interface-specific return values are in the interface simulation files.
The trace file records the telegrams that have been sent (INPUT) and received (OUTPUT).
The recording of such traces can be enabled in the Tool Set in the menu bar under
“Configuration” as well as in the Ediabas.ini configuration file.
A simulation file can be automatically created from the ifh.trc trace file by using
trace2sim.exe. This tool is found in smuc0900sgEdiabasSim trace2sim.exe.
4.21 Why have an XBD Generator?
Before the introduction of the SGBD generator, the source code was edited with a text editor
(up to 40,000 lines). For this purpose, it was necessary to learn the special, C-based
programming language BEST/2 (description language for ECU). Manual programming is
known to be very prone to errors (copy & paste), and it is very difficult to implement the
guidelines specified in the diagnostics specification sheet part 5 as the SGBD becomes
larger.
Now, the SGBD Generator is to be used to create an SGBD by means of menu-driven input
of the data, in which the BMW guidelines are kept. This should result in less effort for the
developer, but it definitely requires a certain amount of practice in working with the SGBD
Generator. A major advantage is the automatic integration of standard ‘include’ files,
whereby new standard ‘includes’ can be added without further ado (new sample XML).
4.22 What are the prerequisites for remote access via TCP/IP?
EDIABAS for WIN32 makes it possible to access the diagnostics interfaces and the attached
ECUs that are connected to another PC. The prerequisite for this is a network connection of
locally and remotely controlled PCs via TCP/IP as well as a WIN32 operating system that is
supported by EDIABAS.
Applications and EDIABAS run on the local PC and the interface handler (IFH) as well as the
IFH-Server run on the PC to be remotely controlled. Before accessing the remotely
controlled PC, the IFH server IFHSRV32.EXE must be started. The remote control is
activated, or alternatively controlled using the EDIABAS configuration file EDIABAS.INI. The
EDIABAS configuration must be performed manually on both PCs.
The EDIABAS configurations TracePath and SimulationPath are not transferred from the
local PC to the remotely controlled PC, rather the respective configurations of the
EDIABAS.INI file that is on the remotely controlled PC is used.
The network protocol TCP (NetworkProtocol entry) as well as a freely selectable port
number must be given on both PCs. The port number must be identical on both PC and
must not collide with other TCP applications (1000 < port number < 30000).
32. Frequently Asked Questions
aboutBMW Group
EDIABAS, INPA and the Tool Set Page 32 of 32
TI-430 Andreas Schandl Release date: 29.09.2006
4.23 What is the VC Tool and when is it used?
VC Tool (version check) can be used to check the versions of the files that are created
during the installation of EDIABAS. When it runs, the tool compares the files specified in the
files BMW_bin.pid, BMW_hw.pid and BMW_rest.pid with regard to their creation data and
creation time. That way, changes made incorrectly in the EDIABAS files can be detected and
corrected.
After running, the VC Tool creates a text file called VC.log in which the comparison is given
with the specific results. This file is stored in the directory where the VC Tool is found
(C:EDIABAS).
4.24 What is the KVP Editor?
KVP stands for continuous improvement process. The KVP Editor can be called when using
the INPA Tool. This is mainly used in reworking and in the plant. Here, the user has the
possibility to enter his name and telephone number and then enter an error description and
improvement request and then to send the form directly to the person responsible at BMW.