![EmSA CANopen](/img/default-banner.jpg)
- 49
- 140 613
EmSA CANopen
Germany
Registrace 18. 12. 2018
Educational channel by Embedded Systems Academy. Training sessions about Embedded Systems, Controller Area Network and higher layer protocols like CANopen and J1939.
CANopen Instant Access Module Testing
Testing the module that has been developed through this video series. Demonstrates SDOs, PDOs and coordinated motion of a robot arm.
For more details see: www.canopenia.com
Published by EmSA: www.em-sa.com
For more details see: www.canopenia.com
Published by EmSA: www.em-sa.com
zhlédnutí: 164
Video
CANopen Instant Access Module Host Firmware
zhlédnutí 98Před rokem
How to interact with the module from host firmware. Just a few simple function calls are needed to implement SDO and PDO handling! For more details visit: www.canopenia.com Published by EmSA: www.em-sa.com
CANopen Instant Access Module Configuration
zhlédnutí 198Před rokem
How to configure a CANopenIA module with custom object dictionary entries. Also demonstrated is documentation export. For more details visit: www.canopenia.com Published by EmSA: www.em-sa.com
CANopen Instant Access Module Integration
zhlédnutí 111Před rokem
Integration of CANopenIA modules into custom circuit boards. A look at the components required, schematic diagram and dimensions. For more details visit: www.canopenia.com Published by EmSA: www.em-sa.com
CANopen Instant Access Module Introduction
zhlédnutí 216Před rokem
Introduction to a five-part series on integrating CANopen into a new or existing project. For more details visit: www.canopenia.com Published by EmSA: www.em-sa.com
PCAN MicroMod FD: CANopen (FD) Firmware Update
zhlédnutí 653Před 3 lety
We provide CANopen and CANopen FD Software options for the PCAN MicroMod FD modules by PEAK-System Technik GmbH (www.peak-system.com). This video shows how to update the firmware for these modules. www.em-sa.com/peak
PCAN MicroMod FD: CANopen (FD) Activation
zhlédnutí 1,1KPřed 3 lety
We provide CANopen and CANopen FD Software options for the PCAN MicroMod FD modules by PEAK System Technik GmbH (www.peak-system.com). This video shows how to activate CANopen (FD) for these modules. www.em-sa.com/peak
CANopen Magic - Trace Analysis
zhlédnutí 692Před 3 lety
An overview of the trace analysis feature in CANopen Magic Ultimate. Quickly analyze the contents of the trace buffer. www.em-sa.com, www.canopenmagic.com
CANopen Magic - Visualize Data
zhlédnutí 851Před 3 lety
A demonstration of how to visualize real time data using meters, charts and LEDs on a CANopen network. www.em-sa.com, www.canopenmagic.com
CANopen Magic - Node Object Dictionaries
zhlédnutí 952Před 3 lety
A demonstration of how to read the entire object dictionary and scan for hidden entries in CANopen Magic Professional and Ultimate www.em-sa.com, www.canopenmagic.com
CANopen Magic - Simulation
zhlédnutí 1,8KPřed 3 lety
A demonstration of the node simulation functionality in CANopen Magic Ultimate www.em-sa.com, www.canopenmagic.com
CANopen Architect - Console
zhlédnutí 230Před 3 lety
A demonstration of the console functionality in CANopen Architect Professional. www.em-sa.com, www.canopenarchitect.com
CANopen Architect - Source Code Export
zhlédnutí 574Před 3 lety
An overview of the features and settings of source code export from CANopen Architect for our CANopen stack - MicroCANopen Plus. www.em-sa.com, www.canopenarchitect.com
CANopen Architect - Configurations and Groups
zhlédnutí 344Před 3 lety
An overview and demonstration of how configurations and groups work in CANopen Architect Professional www.em-sa.com, www.canopenarchitect.com
CANopen Architect - Documentation Export
zhlédnutí 296Před 3 lety
A demonstration of the documentation export functionality available in CANopen Architect Professional. www.em-sa.com, www.canopenarchitect.com
CANopenArchitect: Download and Versions
zhlédnutí 501Před 4 lety
CANopenArchitect: Download and Versions
CANopen Architect: Getting Started with Process Data and PDOs
zhlédnutí 2,3KPřed 4 lety
CANopen Architect: Getting Started with Process Data and PDOs
NXP MCUXpresso SDK: Middleware combination demo: Embedded Wizard's GUI and EmSA's CANopen (FD)
zhlédnutí 1KPřed 4 lety
NXP MCUXpresso SDK: Middleware combination demo: Embedded Wizard's GUI and EmSA's CANopen (FD)
CANopen Logxaminer: Network Description
zhlédnutí 46Před 4 lety
CANopen Logxaminer: Network Description
CANopen Logxaminer: Searching and Filtering
zhlédnutí 37Před 4 lety
CANopen Logxaminer: Searching and Filtering
CANopen Magic: Extended tracing and logging
zhlédnutí 644Před 4 lety
CANopen Magic: Extended tracing and logging
i am not able to add more than four TPOD in EDS editor
I need to program a state checking device, I guess a PLD, to monitor the state of all devices on the CANBus prior to their initiation. Do you have any videos that might help with that? p.s. find all of your content really useful, thanks!
CanOpen Magic can open a DBC file in order to interpret the can-bus data.. yet the most common device file provided by the manufacturer is an EDS! To make matters more confusing, there is also a DCF file format, which seems to be a tailored version of an EDS to a specific device. However, not sure the difference between DCF and DBC. Any suggestions how to create a DBC file based on either an EDS/DCF file or from the product's documentation listing the SDO/PDOs?
Well Done 👍 I actually understand now how the mapping actually works
How do You set Time to system Time so I can compare CAN logs to other app logs?
Our software takes the time stamps as provided by the CAN hardware used. The only modification we can make in the software is to set a new zero point.
Whats exactly the data, that - through the electronic datasheet eds - gets shown/visualized? It seems here in the video there is an active CANopen bus providing data as the eds rarely has data. With dcf there are average defaults but no variation of values. Is it possible to mix it with CAN data (and the corresponding dbc explanation?). Further, can data be retrieved from a Linux CANdump file or directly without the installation of additional hardware on the data-bus?
Yes correct, this instance of the software is connected to a CAN bus producing data and that gets visualized.
time stamp 2:25 Receive RPDO index no : 1600h - 16FFh it should be : 1600h - 17FFh
Good catch! Yes, it should.
Please provide information regarding getting response from sever through tpdo
For PDO there is no client/server defined. PDOs use producers (TPDO) and consumers (RPDO). SDO are client / server communication. Client requests access to an OD entry of a server.
TPDO mapping is done with three objects 0x6078 ,0x606c,0x22a2 and the transmission type is asynchronous i.e 0xff and return type 16bit,32bit,16bit respectively with help of dsp 301 manual as menitoned below. TPDO1 id 0x183 Set 0 to 0x1A00(0) Stop all emissions of TPDO1. Set 0x60780010 to 0x1A00(1) Program the actual current value (object 0x6078) to first 2bytes of the PDO. Set 0x606c0020 to 0x1A00(2) Program object 0x606c for next 4 bytes (actual velocity). Set 0x22a20010 to 0x1A00(3) Program object 0x22a2 for next 2 bytes (temparature). Set 1 to 0x1800(2) Set transmission type in PDO communication parameters to “Transmit every SYNC.” Other PDO communication parameters are not programmable . Set 3 to 0x1A00(0) Activate the three mapped objects. and gave response as in the manual . i think i just mapped the objects . i"m not seeing any response data regarding the objects from the elmo. am i need to do any additional thing. when can i read the tpdo1 data from elmo can u please help me with this
Fantastic video. However, I can't find an explanation of how one can have more than four addressable PDOs per node when in the COB-ID seven bits are the node ID and the remaining four bits are for the function ID, which only allows four PDOs. All the bits are used, so how?
The documents and training describes the default COB-ID assignment. Both the exact CAN ID used and the number of PDOs iused per device is just a default and can be re-configured. Usually it means re-using default COB-IDs from devices not present in the network. EXAMPLE: If in your system you only use node ID 1 to 63 and 64 to 127 are unused (never present), then you can re-assign the default COB-IDs from nodes 64 to 127 to the other nodes.
@@EmSACANopen Thanks for this explanation. I had a suspicion this is the case, that one has to use up some other IDs. But then it's not really true when it is said that one can node can have 512 PDOs, unless you have only a single node.
After sending the Network Management (NMT) Request for Node 3 to go from Pre-Operational to Operational, I see the GUI displays the relative / delta time between TPDO 1/2 messages.. but what does the enabled RPDO messages do? So as a general rule of thumb, the Event-Driven-Trigger + Event Time Trigger is used for slow changing data, the former as a precaution should it unexpectedly generate lots of data.. while the latter is used as a precaution against silencing a node for too long? For fast changing data, like a pressure sensor, what is the maximum can-bus utilization that should be considered? Regarding SYNC, if you set the Transmission Type to Synchronous, is it still necessary to set the Inhibit/Event to 0ms? And if a Node has multiple PDO IDs that will transmit every Sync, how is it ensured that Node 4 will send it's data only AFTER Node 3 has sent all its PDOs? Or is that what the PDO's "SYNC counter start value" entry is used for? Can any node on the bus issue a SYNC message? In the GUI, is the "ID" column the same as the "Connection ID Block (COB)"?
A RPDO configuration is not "visible" on the bus. It is just the configuration for a consumer, somebody else needs to produce it. Maximum busload caused by a single node or CAN frame repetition is typically not defined and are application specific. For a strictly event time driven system, recommendation is to stay below 90 busload. An event driven system should stay (in average) well below 50% bus load.
What defines an SDO vs PDO.. is it simply the ID number? And does CanOpen CIA define the mapping between the numbers and if it's PDO, SDO, heartbeat, etc? For example Transmit PDO at 0x181-0x1FF, Receive PDO 0x201-27F, Heartbeat 0x701-0x77F, etc? Also what is CanOpen IA Configuration used for?
SDO, PDO, HB, EMVY are all different services. Each service requires a unique CAN ID to be used. By default this unique CAN ID is determined by a base number plus the node ID of the node using the service. For EMCY: base is 80h, so node 5 uses CAN ID 85h. CANopenIA is a HW product range providing Instant Access to CANopen.
hi , does your software only work with certain usb to CAN interfaces ? I have Komodo CAN Duo Interface from total phase . will it work with your software ??
Interfaces supported by this software are from www.peak-system.com/ and www.kvaser.com/
Which version would you recommend for displaying/graphing data from a few CanOpen devices using a PEAK USB master? Also, is there any EmSA product for for simulating CanOpen devices to learn how CanOpen operates?
Graphical visualization of PDO data is in Professional and Ultimate, node simulation is in Ultimate. Ultimate also has graphical visualization of simulated nodes' object dictionary data.
When setting up a CVS repository in MCUXpresso, what is the best source for getting a CVS repository set up? I don't quite understand the CVS directory listed in the MCUXpresso HELP guide. Say could we get it set up in WinCVS and use that repository location?
Unfortunately our knowledge about MCUXpresso is limited to integrating our CANopen libraries . Please try posting your question in the NXP forums, for example at community.nxp.com/community/mcuxpresso/mcuxpresso-ide/
Is it possible to operate a CANopen FD Master with a CANopen slave? In other words, the master would only receive 8 bits of data in the data field.
This depends on the CANopen FD Manager/Master implementation which is not standardized. I would expect that any CANopen FD Manager should also be backward compatible to process PDOs of any length, no matter if 1, 2, ... 8 or more bytes.
@@EmSACANopen Is there any issue with the different message frames? A CANFD message frame is different from a CAN2.0 frame. Is it possible to have a system with mixed slave nodes (some CAN2.0 running CANopen and some CAN-FD running CANopenFD), all controlled by CANopenFD master? Thanks.
Unfortunately no, if you put a pure classical CANopen (or CAN) device on a CANopen FD (or CAN FD) network, it will destroy the CAN FD frames and cause error frames. You need a bridge separating the two. See can-newsletter.org/uploads/media/raw/c8f2bab1e505c72108efc741fa8239fc.pdf
I understand CANopen defines a master/slave protocol on top of canbus.. I'm using standard slow canbus (non-FD) running on STM32s / CANopenNode. Is it possible to create a canopen topology, such that the slaves broadcast their sensor data (PDO) independently (without request), but the master on the bus can still control/configure the slave nodes? Regarding monitoring, what hardware does Cangineberry's "CANopen Architect Mini Software" work with? ex. USB Peak, CANedge2?
Yes, this is how combination of PDO / SDO works. PDO for independent data communication between devices. At any time (or not at all) Manager can use SDO to configure devices. CANopen Architect Mini is a pure EDS Editor. It does not need/support any HW.
@@EmSACANopen Is Mapping parameters the way you would transfer a file using CanOpen? I don't see another mechanism for sending a large burst of data where the integrity / order must must be ensured!
In CANopen, you can "send" (write/download or read/upload) a file through SDO segmented or block transfer to/from a DOMAIN type OD entry only. The transfer is always started from the SDO client (normally also the master or manager) and connects to one SDO server (normally a slave node).
@@bennguyen1313 This can be done using the segmented or blocked SDO transfer.
@@bennguyen1313 Use (U)SDO for file transfers.