uvs:programs
Differences
This shows you the differences between two versions of the page.
| Previous revision | |||
| — | uvs:programs [2025/01/01 12:10] (current) – [Summary] uvsoftware | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Programs ====== | ||
| + | |||
| + | ===== CANopen Object Browser for Windows ===== | ||
| + | {{http:// | ||
| + | **CANopen Object Browser for generic CAN Interfaces** | ||
| + | |||
| + | The CANopen Object Browser is a tool to display and browse through a CANopen Object Dictionary based on EDS-Files. | ||
| + | The program allows an online access to any connected CANopen device. | ||
| + | This means to read and to write individual parameter values of a connected device. | ||
| + | |||
| + | The Object Dictionary window displays the CANopen object dictionary of a CANopen device taken either from an EDS-File or from a XML-File. | ||
| + | On the left side of the window all objects are listed in a tree view order by categories. | ||
| + | To navigate through the object tree use either the cursor-up/ | ||
| + | On the right side all attributes and attribute values of the highlighted object are shown. | ||
| + | |||
| + | Parameter values can be entered in hexadecimal, | ||
| + | The value range of the data type will be checked by the program. | ||
| + | But the value range of the parameter will be check by the device. | ||
| + | Data access is only possible if a device is connected to the CAN-Interface board. | ||
| + | |||
| + | __**Please note**__: | ||
| + | Do not connect the program to a real application with a running CANopen network. | ||
| + | This can damage your application. | ||
| + | |||
| + | ==== Supported Interface ==== | ||
| + | Currently (COPbrorwser v0.5) the following CAN devices are supported: | ||
| + | * IXXAT Automation: all CAN devices with VCI driver (VCI V2; tested with iPC-I320/ | ||
| + | * PEAK-System Technik: all CAN devices with PCAN driver (PCAN-Basic V1.0 + PCAN-Light V1.55; tested with PCAN-USB) | ||
| + | * Vector Informatik: all CAN devices with VXL driver (VXL library V3.0; tested with CANcaseXL, USB) | ||
| + | * M+K GmbH: RS-CAN-Wandler with ASPopen Interface (SW.M16C.MEW.C1R1.CANopen.ASP.2005.06) | ||
| + | * UV Software: CANopen-over-TCP/ | ||
| + | |||
| + | |{{ http:// | ||
| + | ^ IXXAT VCI V2 ^ PEAK PCAN-Basic | ||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ CANopen Object Browser (Windows) | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | ^Documentation | ||
| + | ^License | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | ^Download server | ||
| + | |||
| + | |||
| + | ===== CANopen Object Browser for Linux ===== | ||
| + | {{ http:// | ||
| + | **CANopen Object Browser for Linux with BerliOS SocketCAN** | ||
| + | |||
| + | The CANopen Object Browser is a tool to display and browse through a CANopen Object Dictionary based on EDS-files. | ||
| + | The program allows an online access to any connected CANopen device. | ||
| + | This means to read and to write individual parameter values of a connected device. | ||
| + | |||
| + | The CANopen Object Browser for Linux is a Qt3 GUI application (http:// | ||
| + | Furthermore the program offers a gateway function for interfacing CANopen with TCP/IP. | ||
| + | |||
| + | __**Please note**__: | ||
| + | Do not connect the program to a real application with a running CANopen network. | ||
| + | This can damage your application. | ||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ CANopen Object Browser (Linux) | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | ^Documentation | ||
| + | ^License | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | ^Download server | ||
| + | |||
| + | |||
| + | ===== CANopen Commandline Tool ===== | ||
| + | {{http:// | ||
| + | The //CANopen Commandline Tool// is a text-based program to request CANopen services from CANopen devices on the command line by entering commands at the program´s prompt or processing them from a batch file. | ||
| + | |||
| + | The syntax for these commands is taken from the CANopen specification CiA DS-309/3 (// | ||
| + | The program is build on the UVS [[uvs: | ||
| + | Here the //CANopen Commandline Tool// uses the [[wp> | ||
| + | it runs well with a PEAK PCAN-USB-Dongle on Debian Etch and on a MPC5200B evaluation board with an Embedded Linux. | ||
| + | Furthermore the program offers a gateway function for interfacing CANopen with TCP/IP. | ||
| + | |||
| + | The program allows reading and writing of individual parameter values of any connected CANopen device. | ||
| + | Due to the fact, that the UVS CANopen Master library is not a complete CANopen stack, some limitations must be taken into account. | ||
| + | But the missing CANopen services can be build up manually from the CAN layer 2 commands of the program. | ||
| + | |||
| + | ==== Syntax ==== | ||
| + | |||
| + | Usage: can_open < | ||
| + | Options: | ||
| + | -g, --gateway=< | ||
| + | -i, --id=< | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | -h, --help | ||
| + | | ||
| + | Examples: | ||
| + | 1. Local mode: | ||
| + | 2.1 Gateway mode: can_open < | ||
| + | 2.2 Remote mode: | ||
| + | In local mode and in remote mode press ^D to leave the interactive input. | ||
| + | In gateway mode press ^C to close the port and exiting the program. | ||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ can_open (CANopen Commandline Tool) ^^ | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | ^Documentation | ||
| + | ^License | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | ^Download server | ||
| + | |||
| + | |||
| + | ===== CANopen-over-TCP/ | ||
| + | {{ http:// | ||
| + | |||
| + | This little program is for accessing a CANopen-over-TCP/ | ||
| + | |||
| + | With this text-based program you can access any CANopen device connected to a CANopen-over-TCP/ | ||
| + | The syntax is taken from the CANopen specification CiA DS-309/3 (Interfacing CANopen with TCP/IP - ASCII Mapping) and is described [[http:// | ||
| + | |||
| + | |||
| + | ==== Syntax ==== | ||
| + | copnet < | ||
| + | copnet (/ | ||
| + | copnet (/ABOUT | /µ) | ||
| + | Options: | ||
| + | /P, / | ||
| + | /E, /ECHO echo input stream to output stream | ||
| + | /?, /HELP display this help and exit | ||
| + | /µ, / | ||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ copnet (CANopen-over-TCP/ | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | ^Documentation | ||
| + | ^License | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | |||
| + | |||
| + | ===== CAN Monitor using SocketCAN ===== | ||
| + | {{http:// | ||
| + | |||
| + | Yes, this is another CAN monitor using [[wp> | ||
| + | The [[http:// | ||
| + | but I hate this messing around with binary masks for identifier filtering. | ||
| + | So I wrote this little program to have an //exclude list// for single identifiers or identifier ranges (see program option '' | ||
| + | |||
| + | ==== Syntax ==== | ||
| + | Usage: can_moni < | ||
| + | Options: | ||
| + | -t, --time=(abs|rel|zero) | ||
| + | -i, --id=(hex|dec|oct) | ||
| + | -d, --data=(hex|dec|oct) | ||
| + | -a, --ascii=(on|off) | ||
| + | -x, --exclude=[~]< | ||
| + | -h, --help | ||
| + | | ||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ can_moni (CAN Monitor using SocketCAN) | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | ^Documentation | ||
| + | ^License | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | ^Download server | ||
| + | |||
| + | |||
| + | ===== CAN Monitor goes Mac OS X ===== | ||
| + | {{ http:// | ||
| + | |||
| + | This is a port of the CAN Monitor program from Linux to Mac. It is running with a PCAN-USB device or PCAN-USB FD device on macOS Mountain Lion and hopefully on later versions of the world´s mostest advanced OS. | ||
| + | |||
| + | ==== Syntax ==== | ||
| + | Usage: can_moni < | ||
| + | Options: | ||
| + | -t, --time=(ZERO|ABS|REL) | ||
| + | | ||
| + | -d, --data=(HEX|DEC|OCT) | ||
| + | -a, --ascii=(ON|OFF) | ||
| + | -x, --exclude=[~]< | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | -m, --mode=(2.0|FDF[+BRS]) | ||
| + | | ||
| + | | ||
| + | | ||
| + | -b, --baudrate=< | ||
| + | | ||
| + | -v, --verbose | ||
| + | -y, --trace=(ON|OFF) | ||
| + | | ||
| + | -L, --list-boards | ||
| + | -T, --test-boards | ||
| + | -h, --help | ||
| + | | ||
| + | Interfaces: | ||
| + | PCAN-USB1 | ||
| + | PCAN-USB2 | ||
| + | PCAN-USB3 | ||
| + | PCAN-USB4 | ||
| + | PCAN-USB5 | ||
| + | PCAN-USB6 | ||
| + | PCAN-USB7 | ||
| + | PCAN-USB8 | ||
| + | CAN 2.0 baud rate index (default=3): | ||
| + | 0 = 1000 kBit/s | ||
| + | 1 = 800 kBit/s | ||
| + | 2 = 500 kBit/s | ||
| + | 3 = 250 kBit/s | ||
| + | 4 = 125 kBit/s | ||
| + | 5 = 100 kBit/s | ||
| + | 6 = 50 kBit/s | ||
| + | 7 = 20 kBit/s | ||
| + | 8 = 10 kBit/s | ||
| + | CAN FD bit rate as comma-separeted < | ||
| + | f_clock=< | ||
| + | f_clock_mhz=< | ||
| + | nom_brp=< | ||
| + | nom_tseg1=< | ||
| + | nom_tseg2=< | ||
| + | nom_sjw=< | ||
| + | nom_sam=< | ||
| + | data_brp=< | ||
| + | data_tseg1=< | ||
| + | data_tseg2=< | ||
| + | data_sjw=< | ||
| + | Examples: | ||
| + | 125kbps: | ||
| + | 250kbps: | ||
| + | 500kbps: | ||
| + | 1000kbps: | ||
| + | 2000kbps: | ||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ can_moni (CAN Monitor using PCAN-USB) | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | ^Documentation | ||
| + | ^License | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | ^Download server | ||
| + | ^GitHub repo | ||
| + | |||
| + | ===== CAN Monitor App for OS X ===== | ||
| + | {{http:// | ||
| + | |||
| + | The MacCAN Monitor App is a little demo program to show the functionally of the PCBUSB library: the [[http:// | ||
| + | |||
| + | The program displays received CAN messages in a table view; its size is limited to 1024 rows. Furthermore it is possible to send single standard CAN messages with 0 to 8 data bytes. | ||
| + | Only PCAN-USB devices from PEAK-System Technik GmbH are supported; and only the first channel of a device. The PCAN-USB interface number is taken from the IO registry. | ||
| + | USB interface and CAN baud rate must be chosen once the program is started; they cannot be changed afterwards. | ||
| + | |||
| + | |||
| + | __Please note__: Do not connect your CAN device to a real CAN network when using this program, this might damage your application. | ||
| + | |||
| + | |||
| + | ==== Summary ==== | ||
| + | ^ MacCAN Monitor App (Demo) | ||
| + | ^Developer | ||
| + | ^Current version | ||
| + | / | ||
| + | ^Documentation | ||
| + | / | ||
| + | / | ||
| + | ^License | ||
| + | ^Source code | ||
| + | ^Standard(s) | ||
| + | ^Driver(s) | ||
| + | ^Category | ||
| + | ^Operating system | ||
| + | ^Download server | ||
| + | ^GitHub repo | ||
| + | ^Additional information |PCAN is a registered trademark of [[http:// | ||
| + | |||
| + | ===== CANopen Master Library ===== | ||
| + | [[http:// | ||
| + | **CANopen Master Library in C** | ||
| + | |||
| + | [To Be Continued] | ||
| + | |||
| + | **Softwarepaket CANopen Master Library für Infineon C16x** | ||
| + | * Initialisierung des on-chip CAN Controllers (82527-kompatibel): | ||
| + | * Baudraten: 10kBit/s bis 1MBit/s (gemäß CiA Bit-timing Tabelle) | ||
| + | * SDO-Protokoll (segmented und expedited, gemäß CiA DS-301 Version 4.0): | ||
| + | * Einfacher Zugriff auf 8-bit, 16-bit und 32-bit Objektwerte (CiA Encoding Rules) | ||
| + | * Einstellbare Time-out Überwachung (bei Time-out wird ein SDO-Abort gesendet) | ||
| + | * Detaillierte Fehlerrückgabe (Kommunikationsfehler bzw. SDO-Abort Codes) | ||
| + | * NMT-Broadcast (Network Management gemäß CiA DS-301 Version 4.0): | ||
| + | * Start_remote_node | ||
| + | * Stop_remote_node | ||
| + | * Enter_preoperational_state | ||
| + | * Reset_node | ||
| + | * Reset_communication | ||
| + | * LSS-Services (Layer Settings Services gemäß CiA DSP-305 Version 1.0): | ||
| + | * Switch_mode_global | ||
| + | * Switch_mode_selective | ||
| + | * Configure_node_id | ||
| + | * Configure_bit_timing | ||
| + | * Activate_bit_timing | ||
| + | * Store_configuration | ||
| + | * Inquiry Services | ||
| + | * Baudraten-Detektor und Node-Scanner (***Special Feature by UV Software***): | ||
| + | * Der Baudraten-Detektor erkennt die aktuelle Baudrate des CAN-Netzwerk. | ||
| + | * Der Node-Scanner liefert die Anzahl der angeschlossenen CANopen-Knoten. | ||
| + | * Event-Queue für ereignis-gesteuerte Nachrichtenverarbeitung, | ||
| + | * asynchrone PDOs | ||
| + | * Emergency-Messages | ||
| + | * Heartbeat-Messages | ||
| + | * Zugriff auf CAN Layer 2: | ||
| + | * Transmit Message (z.B. für TxPDOs, SYNC-Objekt, | ||
| + | * Request Message (z.B. für RTR-PDOs, Node-Guarding) | ||
| + | * ASCII-codierte RS-232 Schnittstelle (***Special Feature by UV Software***): | ||
| + | * Zugriff auf das Objektverzeichnis aller angeschlossenen CANopen-Knoten über RS-232 | ||
| + | * Syntax in Anlehnung an DriveServer Spezifikation (siehe http:// | ||
| + | |||
| + | Das Paket zeichnet sich durch die minimale Verwendung von Mikrocontroller-Ressourcen aus. | ||
| + | Die Softwarelibrary liegt auch für Mikrocontroller Infineon XC16x (TwinCan) und Mitsubishi M16C (Renesas) vor. | ||
| + | |||
| + | Preise: //auf Anfrage// | ||
| + | |||
| + | |||
| + | ---- | ||
| + | ^To Be Continued| | ||