Pcan View Driver Download

[Gregory Monty]

iam using SPC560B54L5 and i am testing can protocol in pcan view i got error busheavy status . i am also checking on oscilloscope only getting rx signal from transceiver. CAN interface connectionis like from pcan to transceiver and transceiver to mcu please check attached pic & help me for fixing the problem thanks in advanced.

I intend to communicate Labview with a motor controller through CAN network by using a PCAN-USB adapter from Peak System. I wanted to know if NI-CAN is able to send and receive commands through devices that are not from National Instrument (in this case it will be the PCAN-USB adapter from Peak System). Can anyone that knows anything on this matter help me out please?

We have used PCAN-USB using the LabVIEW driver that PEAK provide. I don't think you can use NI-CAN or NI-XNET to talk directly to the CAN network using the PCAN USB but we do use the conversion functions of NI XNET to convert between CAN messages and signal/value data and vice-versa and then use the PCAN LabVIEW driver to read/write the messages.

NI-CAN supports only National Instruments devices. However, you should be able to use Peak System's library (DLL) instead of NI-CAN to read and write CAN messages from within LabVIEW. There's nothing special about NI-CAN.

you indicated you used the xnet vi's to perform conversions. Would you please share how you created a valid xnet session? I would like to use that functionality but I receive an error on the session for invalid or nor CAN hardware.

XNet frame and channel conversion can be done without XNet hardware, it is just a translation of data from one format to another. So read your frames like you normally would with what ever drivers it comes with, and then use that API to convert it into signals, given a database.

Unfortunately, the EVM examples are all loopback mode examples. I suggest starting with the "mcan_external_loopback_interrupt_am273x-evm" and make a useable multi-device application example to start. I don't know PCAN-VIEW yet, but I suspect it acts like a MCAN device on the bus, correct?

Hi Randy i have attached CAN_Use_case_PCAN.drawio file this is my hardware setup.

as you mentioned in previous comments it requires pcan-view driver support from sdk end your means changes required MCU+SDK for AM273x.

Please can you elaborate more regarding changes from driver end.

which type of custom changes required for sdk driver. I am having few questions related to that.

1. How to set buad rate to exchangs can messages from pcan-view to AM273x.

Note-I have a option to change baud rate in pcan-view tool so i have to match this in TI SOC(AM273x) driver program

How do we do that?

If detect_available_configs only returns PCAN_USBBUS1, that means the underlying driver could only detect that channel. If PCAN provides a utility to view available channels, you can check whether it detects the same number of channels as python-can.

Interfaces=None returns a lot of information most of it is error because my laptop has only pcan connected with hardware and nothing else.

As far as pcan information in the details provided by setting interfaces=None it shows only PCAN_USBBUS1 only with the device id of my pcan.

The CANUSB can utilize of virtual COM port driver, so that it appears to your system as a standard serial port, which can make it trivial to write your own tools or test rigs. If you need higher bandwidth for high bus-loads, a direct USB driver is available as well. USB drivers for CANUSB are available for Windows, OSX and Linux, although the bus monitor utilities available from LAWICEL are Windows-only.

Intrepid Control Systems offers the ValueCAN3 at $300. Rumor has it that the CANUSB/232 from LAWICEL falls short on higher bus rates, or even highly loaded busses at lower rates. The ValueCAN can keep up with a fully loaded 1 Mbit/sec bus. The ValueCAN achieves this in part by utilizing a true USB interface, unlike the CANUSB, which uses an off-board serial-to-USB converter chip from FTDI.

The ValueCAN3 comes with a limited trial license for its Vehicle Spy software, but a full license for the basic version is $1000 per seat. This is still significantly cheaper that what you would pay Vector! Another pitfall of the ValueCAN is that the software and driver are only available for the Windows platform.

Although the PCAN-USB supplied PCAN-VIEW and other software programs are Windows-only, uvsoftware has developed free device drivers for Linux and OSX as well. To top it off, uvsoftware also has a slew of different free and multi-platform software packages, and the source code is also available for the super techies who want to dig in and write their own kick-ass test rigs!

Though there are many firms that have made good use of CANoe, the fact that the CANoe programming language is proprietary and very low-level, makes it inefficient for many testing applications. If Vector would provide bindings for other higher-level languages, like Python, Ruby or even C#, it would be more feasible.

Great collection of CAN tools!

For the more adventurous, there are also some great CAN micro development boards from chip makers that have all of the hardware to be used as interfacing tools. At Techmor, we make sensors for the CAN Bus to be viewed and logged over Bluetooth on Android apps.

PEAK-System Technik is a leading provider of hardware, software, and services for the industrial communication. The focus is on the field busses CAN and LIN. The product range includes: CAN/LIN interface modules for common PC hardware interfaces (PCI, cPCI, Mini PCI, PCIe, PC/104, USB, PC Card, and ExpressCard), Configurable microcontroller hardware with CAN interfaces for individual developments, measurement data acquisition, and control applications, Various software products for Windows 7, Vista, and XP, used for diagnosis, monitoring, and influencing of CAN and LIN networks

The PCAN-Basic API (application programming interface) allows easy development of powerful software with CAN and CAN FD support. It includes all of the functions that an application needs in order to communicate with PCAN PC hardware. The cross-operating-system design makes it possible to easily port software projects between platforms.

The professional programming interface PCAN-API of the PCAN-Developer package makes it possible to create complex Windows applications with CAN and CAN FD support. The API (Application Programming Interface) provides an extensive function library using interface DLLs for 32-bit and 64-bit systems.

Unlike PCAN-Basic, the CAN communication is handled by Clients and offers significant advantages. Thus, not only a single but multiple applications can access a physical CAN channel. Furthermore, it works even without hardware: Via virtual connections, Clients establish a simulated CAN communication among Windows applications.

The PCAN-RP1210 API by PEAK-System is an implementation of the RP1210 versions A and C with support for CAN and SAE J1939 networks. Thus, the API makes it possible to develop own RP1210 applications and to use already existing ones with CAN interfaces by PEAK-System.

The PCAN-CCP API is a programming interface for the communication between Windows applications (Masters) and electronic control units (Slave ECUs). The API is based on the CAN Calibration Protocol (CCP) by ASAM and is mainly deployed for development in the automotive area. The PCAN-CCP API uses the CAN bus as transmission medium.

For accessing the CAN hardware in the computer, PCAN-CCP utilizes the programming interface PCAN-Basic, which is part of the scope of supply of every CAN interface from PEAK-System. The PCAN-CCP API package is available free of charge.

The PCAN-XCP API is a programming interface for the communication between Windows applications (Masters) and electronic control units (Slave ECUs). The Universal Measurement and Calibration Protocol (XCP) is a further development of the CAN Calibration Protocol (CCP) by ASAM. XCP supports multiple transmission mediums, but is not compatible to CCP.

For accessing the CAN hardware in the computer, PCAN-XCP utilizes the programming interface PCAN-Basic, which is part of the scope of supply of every CAN interface from PEAK-System. The PCAN-XCP API package is available free of charge.

For the programming of control units (ECU), there are countless applications from various manufacturers which are used in the development and diagnosis of vehicle electronics. The interface for the communication between these applications and the control units is defined by the international standard SAE J2534 (Pass-Thru). Thus, the hardware for the connection to the control unit can be selected regardless of its manufacturer.

ISO-TP (ISO 15765-2) is an international standard for the transfer of data packages via CAN. Above CAN (OSI layers 1 and 2), the protocol covers the OSI layers 3 (Network Layer) and 4 (Transport Layer). It can transmit data packages of up to 4095 bytes per CAN message. The data bytes are transmitted segmented with multiple CAN frames.

The PCAN-ISO-TP API implements the functionality of the standard on the basis of 10 functions. They are categorized in Allocation, Configuration, Address Mapping Configuration, Information, and Communication.

UDS (ISO 14229-1) stands for Unified Diagnostic Services and defines the communication with control units (ECUs). The Windows software tests the controller using various services. The process is done on the client-server principle where the program is in the position of the client (also called tester). UDS uses the ISO-TP standard as transport protocol, thus UDS can transmit data blocks of up to 4095 bytes size. Besides the exchange of maintenance information, for example, the transfer of firmware is possible.

3a8082e126