pip3
instead of pip
in order to install the Python package in the correct place.
Now we can write a small Python program, sendReceiveSingleCanMsg.py
, that sends a CAN message on channel 1 and receives the same CAN message on channel 0:[/vc_column_text][vc_code_raket language="python" code="aW1wb3J0JTIwY2FubGliLmNhbmxpYiUyMGFzJTIwY2FubGliJTBBJTBBJTBBZGVmJTIwc2V0VXBDaGFubmVsJTI4Y2hhbm5lbCUzRDAlMkMlMEElMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjBvcGVuRmxhZ3MlM0RjYW5saWIuY2FuT1BFTl9BQ0NFUFRfVklSVFVBTCUyQyUwQSUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMGJpdHJhdGUlM0RjYW5saWIuY2FuQklUUkFURV81MDBLJTJDJTBBJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwYml0cmF0ZUZsYWdzJTNEY2FubGliLmNhbkRSSVZFUl9OT1JNQUwlMjklM0ElMEElMjAlMjAlMjAlMjBjbCUyMCUzRCUyMGNhbmxpYi5jYW5saWIlMjglMjklMEElMjAlMjAlMjAlMjBjaCUyMCUzRCUyMGNsLm9wZW5DaGFubmVsJTI4Y2hhbm5lbCUyQyUyMG9wZW5GbGFncyUyOSUwQSUyMCUyMCUyMCUyMHByaW50JTI4JTIyVXNpbmclMjBjaGFubmVsJTNBJTIwJTI1cyUyQyUyMEVBTiUzQSUyMCUyNXMlMjIlMjAlMjUlMjAlMjhjaC5nZXRDaGFubmVsRGF0YV9OYW1lJTI4JTI5JTJDJTBBJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwY2guZ2V0Q2hhbm5lbERhdGFfRUFOJTI4JTI5JTI5JTI5JTBBJTIwJTIwJTIwJTIwY2guc2V0QnVzT3V0cHV0Q29udHJvbCUyOGJpdHJhdGVGbGFncyUyOSUwQSUyMCUyMCUyMCUyMGNoLnNldEJ1c1BhcmFtcyUyOGJpdHJhdGUlMjklMEElMjAlMjAlMjAlMjBjaC5idXNPbiUyOCUyOSUwQSUyMCUyMCUyMCUyMHJldHVybiUyMGNoJTBBJTBBJTBBZGVmJTIwdGVhckRvd25DaGFubmVsJTI4Y2glMjklM0ElMEElMjAlMjAlMjAlMjBjaC5idXNPZmYlMjglMjklMEElMjAlMjAlMjAlMjBjaC5jbG9zZSUyOCUyOSUwQSUwQWNsJTIwJTNEJTIwY2FubGliLmNhbmxpYiUyOCUyOSUwQXByaW50JTI4JTIyY2FubGliJTIwdmVyc2lvbiUzQSUyMCUyNXMlMjIlMjAlMjUlMjBjbC5nZXRWZXJzaW9uJTI4JTI5JTI5JTBBJTBBJTBBY2hhbm5lbF8wJTIwJTNEJTIwMCUwQWNoYW5uZWxfMSUyMCUzRCUyMDElMEFjaDAlMjAlM0QlMjBzZXRVcENoYW5uZWwlMjhjaGFubmVsJTNEMCUyOSUwQWNoMSUyMCUzRCUyMHNldFVwQ2hhbm5lbCUyOGNoYW5uZWwlM0QxJTI5JTBBJTBBbXNnSWQlMjAlM0QlMjAxMDAlMEFtc2clMjAlM0QlMjAlNUIxJTJDJTIwMiUyQyUyMDMlMkMlMjA0JTVEJTBBZmxnJTIwJTNEJTIwY2FubGliLmNhbk1TR19FWFQlMEFjaDEud3JpdGUlMjhtc2dJZCUyQyUyMG1zZyUyQyUyMGZsZyUyOSUwQSUwQXdoaWxlJTIwVHJ1ZSUzQSUwQSUyMCUyMCUyMCUyMHRyeSUzQSUwQSUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyOG1zZ0lkJTJDJTIwbXNnJTJDJTIwZGxjJTJDJTIwZmxnJTJDJTIwdGltZSUyOSUyMCUzRCUyMGNoMC5yZWFkJTI4JTI5JTBBJTIwJTIwJTIwJTIwJTIwJTIwJTIwJTIwZGF0YSUyMCUzRCUyMCUyNyUyNy5qb2luJTI4Zm9ybWF0JTI4eCUyQyUyMCUyNzAyeCUyNyUyOSUyMGZvciUyMHglMjBpbiUyMG1zZyUyOSUwQSUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMHByaW50JTI4JTIydGltZSUzQSUyNTlkJTIwaWQlM0ElMjU5ZCUyMCUyMGZsYWclM0EweCUyNTAyeCUyMCUyMGRsYyUzQSUyNWQlMjAlMjBkYXRhJTNBJTI1cyUyMiUyMCUyNSUwQSUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyOHRpbWUlMkMlMjBtc2dJZCUyQyUyMGZsZyUyQyUyMGRsYyUyQyUyMGRhdGElMjklMjklMEElMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjBicmVhayUwQSUyMCUyMCUyMCUyMGV4Y2VwdCUyMCUyOGNhbmxpYi5jYW5Ob01zZyUyOSUyMGFzJTIwZXglM0ElMEElMjAlMjAlMjAlMjAlMjAlMjAlMjAlMjBOb25lJTBBJTIwJTIwJTIwJTIwZXhjZXB0JTIwJTI4Y2FubGliLmNhbkVycm9yJTI5JTIwYXMlMjBleCUzQSUwQSUyMCUyMCUyMCUyMCUyMCUyMCUyMCUyMHByaW50JTI4ZXglMjklMEElMEF0ZWFyRG93bkNoYW5uZWwlMjhjaDAlMjklMEF0ZWFyRG93bkNoYW5uZWwlMjhjaDElMjklMEE="][vc_column_text]Running the above Python program results in the following:[/vc_column_text][vc_code_raket code="JTI0JTIwcHl0aG9uJTIwc2VuZFJlY2VpdmVTaW5nbGVDYW5Nc2cucHklMEFjYW5saWIlMjB2ZXJzaW9uJTNBJTIwNS4xOCUwQVVzaW5nJTIwY2hhbm5lbCUzQSUyMEt2YXNlciUyMFVTQmNhbiUyMFBybyUyMDJ4SFMlMjB2MiUyMCUyOGNoYW5uZWwlMjAwJTI5JTJDJTIwRUFOJTNBJTIwNzMtMzAxMzAtMDA3NTItOSUwQVVzaW5nJTIwY2hhbm5lbCUzQSUyMEt2YXNlciUyMFVTQmNhbiUyMFBybyUyMDJ4SFMlMjB2MiUyMCUyOGNoYW5uZWwlMjAxJTI5JTJDJTIwRUFOJTNBJTIwNzMtMzAxMzAtMDA3NTItOSUwQXRpbWUlM0ElMjAlMjAyODE5NzEwJTIwaWQlM0ElMjAlMjAlMjAlMjAlMjAlMjAxMDAlMjAlMjBmbGFnJTNBMHgwNCUyMCUyMGRsYyUzQTQlMjAlMjBkYXRhJTNBMDEwMjAzMDQ="][vc_column_text]If you are using Python v3, you would probably be using python3
instead of python
.
And thus we have successfully sent and received a CAN message using the Python canlib package.
Bug reports, contributions, suggestions for improvements, and similar things are much appreciated and can be sent by e-mail to [email protected].[/vc_column_text][/vc_column][/vc_row]
[post_title] => [Archive] Running Python wrapper on Linux
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => archive-running-python-wrapper-linux
[to_ping] =>
[pinged] =>
[post_modified] => 2022-10-04 13:08:52
[post_modified_gmt] => 2022-10-04 13:08:52
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?post_type=developer_blog&p=39865
[menu_order] => 0
[post_type] => developer_blog
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[2] => WP_Post Object
(
[ID] => 13631
[post_author] => 23
[post_date] => 2016-09-23 22:10:29
[post_date_gmt] => 2016-09-23 22:10:29
[post_content] => [vc_row][vc_column width="1/4"][/vc_column][vc_column width="1/2"][vc_single_image image="13596"][/vc_column][vc_column width="1/4"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Alerting all those involved in industrial and heavy-duty applications. Kvaser has now released a Leaf Light HS v2 J1939-13 Type II with the characteristic green-coloured diagnostic socket. The 9-pin J1939-13 (Type II) compliant CAN connector is used for off-board connection to a vehicle’s SAE J1939 communication network and supports either 250 Kbps or 500 Kbps. While the SAE approved the specification for this off-board diagnostic connection in 2011, we are only just seeing demand from customers for this socket now that the Type I socket is being phased out.
View the Leaf Light HS v2 J1939-13 Type II here[/vc_column_text][/vc_column][/vc_row]
[post_title] => J1939-13 Type II connection is now available
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => j1939-13-type-ii-connection-now-available
[to_ping] =>
[pinged] =>
[post_modified] => 2022-09-29 05:16:50
[post_modified_gmt] => 2022-09-29 05:16:50
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=13631
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[3] => WP_Post Object
(
[ID] => 13600
[post_author] => 5
[post_date] => 2016-09-22 12:07:16
[post_date_gmt] => 2016-09-22 12:07:16
[post_content] => [vc_row][vc_column][vc_single_image image="13603"][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="Improved Comparison function"][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_column_text]If you are a regular visitor to Kvaser.com, you’ll notice some big changes took place in August. Top of the list was some overall design refreshment, resulting in, among other benefits, a simplified click-through path to our products and those of our software partners.
However, the biggest advantage to customers from the new design will come from the implementation of a ‘My Kvaser’ facility, where you can log in, quickly view your previously researched items, compare them and export the information to PDF and email, plus view previous orders, including detailed information such as any device serial numbers that you have registered.
[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="13627" img_size="400x407"][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="Request info on CAN software"][vc_column_text]My Kvaser is designed to make your life easier, helping you request information from third party software providers and track their response, provide a record of your purchases and keep you apprised of their warranty status.[/vc_column_text][vc_single_image image="13630"][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="Register your product"][/vc_column][/vc_row][vc_row][vc_column width="1/2"][vc_column_text]If you buy Kvaser devices through a Kvaser Qualified Sales Representative, we encourage you to register your device within My Kvaser to benefit from an extra year of warranty, as well as alerts for software updates that relate to your registered product/s, news of software tutorials relevant to your product and eventually, End of Life information.[/vc_column_text][/vc_column][vc_column width="1/2"][vc_single_image image="13625"][/vc_column][/vc_row]
[post_title] => Kvaser’s website gets more than a new look
[post_excerpt] => If you are a regular visitor to Kvaser.com, you’ll notice some big changes took place in August. Top of the list was some overall design refreshment, resulting in, among other benefits, a simplified click-through path to our products and those of our software partners.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => kvasers-website-gets-new-look
[to_ping] =>
[pinged] =>
[post_modified] => 2022-09-29 05:16:49
[post_modified_gmt] => 2022-09-29 05:16:49
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=13600
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[4] => WP_Post Object
(
[ID] => 12544
[post_author] => 5
[post_date] => 2016-07-28 12:49:32
[post_date_gmt] => 2016-07-28 12:49:32
[post_content] => Leading Controller Area Network (CAN) interface specialist, Kvaser AB, is pleased to announce a marine version of its highly popular Leaf Light HS v2 interface. With a USB 2.0 connector at one end and a 5-pin National Marine Electronics Association (NMEA) approved CAN connector at the other, the Kvaser Leaf Light HS v2 M12 provides a simple way to connect a PC to the on-board computer of a marine electronics system.
Supporting high speed USB, all Kvaser Leaf Light v2 application-specific interfaces can send up to 8000 messages per second, each time-stamped with 100 microsecond accuracy. Galvanic isolation, previously a more expensive option on Kvaser’s original Leaf Light, comes as standard on the Leaf Light HS v2 series, enhancing protection from power surges or electrical shocks. The Leaf Light v2 M12 is ideal for diagnosing NMEA 2000 bus issues, configuring and flashing NMEA 2000 bus nodes, monitoring NMEA 2000 bus traffic and load conditions and stimulating or emulating NMEA 2000 nodes.
Used with Kvaser’s CANlib library, which is free to download from Kvaser’s website (www.kvaser.com), the Leaf Light HS v2 interface series provide application programmers with quick and easy access to the CAN network. The software can be used across Kvaser’s product portfolio and enables hardware initialization, bus on/off, setting of bus parameters and buffers, as well as read/write commands.
For more information on the Kvaser Leaf Light HS v2 M12, please visit the product page here.
[post_title] => Kvaser releases marine version of its popular Leaf Light HS v2 CAN interface [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => marine-version-of-leaf-light-hs-v2-can-interface [to_ping] => [pinged] => [post_modified] => 2022-09-29 04:14:14 [post_modified_gmt] => 2022-09-29 04:14:14 [post_content_filtered] => [post_parent] => 0 [guid] => https://www.kvaser.com/?p=12544 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [5] => WP_Post Object ( [ID] => 12421 [post_author] => 5 [post_date] => 2016-07-05 18:38:46 [post_date_gmt] => 2016-07-05 18:38:46 [post_content] => [vc_row el_class="full_width"][vc_column][vc_column_text][/vc_column_text][vc_column_text]Have you ever wondered why 95% of the ocean is still unexplored? To begin with, it’s an extremely hard environment to survive in, which is why building an Autonomous Underwater Vehicle that explores and interacts with the ocean environment is a particularly challenging task. From pressure resistance, to artificial intelligence, every detail counts or an AUV will fail.[/vc_column_text][vc_column_text]Since 1999, team S.O.N.I.A. of École de Technologie Supérieure in Montreal has participated in the annual Robosub Competition in San Diego, California, which sets out a series of difficult visual- and acoustic-based tasks for student-built autonomous robotic submarines. With an impressive legacy of AUV know-how, S.O.N.I.A. competes against some of the world’s top universities and is currently ranked one of Robosub’s top teams. Nevertheless, every year brings multiple new challenges.[/vc_column_text][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column width="2/3"][vc_column_text]For 2016, team S.O.N.I.A. – composed of more than 25 students – has decided to focus on building modularity into their system. From mechanical designs, to electrical custom-made PCBs and software, using a modular approach contributes to overall system reliability. For example, if a node fails, it can simply be swapped out of the system, without any effect on the system as a whole. Modularity also enables the team to prototype at 10 times the speed. In the case of S.O.N.I.A’s UAV, there are various hardware and related sensors or ‘nodes’ within the submarine. These include a navigation system, cameras, six motors, a high brightness light, a torpedo launcher (a technology demonstrator, as opposed to a live version!) and two small robotic arms.[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="12461"][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column][vc_column_text]Notes Etienne Pilon, S.O.N.I.A.’s Team Leader: “Building submarines isn’t the biggest trend at the moment, so the team always need to find new ways of solving problems and prototyping is a huge focus for us. Of course, our prototyping needs to stand on solid ground. For the past few years, this solid ground is ensured by the Kvaser unit used for the communication between all the sensors, devices and computer. By taking care of the CAN communication, the team can work on what really matters i.e. the electrical team can focus on building new devices, and the software team can concentrate on designing better artificial intelligence. Hence, the Kvaser unit’s reliability and ease of use accelerates the development of new features and gives us an innovative edge.”[/vc_column_text][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column width="1/4"][vc_single_image image="12483" img_size="139x200"][/vc_column][vc_column width="3/4"][vc_column_text][/vc_column_text][vc_column_text]Notably, S.O.N.I.A. has used a Kvaser USBcan II for many years and has recently been supplied with a Kvaser Leaf Pro HS v2. As Linux users, the team initially chose Kvaser CAN hardware because of Kvaser’s support for both Windows and Linux. [/vc_column_text][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column][vc_column_text][/vc_column_text][vc_column_text]Team S.O.N.I.A. are not just committed users of Open Source software, but they have also created an OpenSource package for robotic systems that interface with Kvaser devices. Recounts Pilon: “We believe that innovation should not be kept secret. That’s why this year, the team has developed an open source package that connects our Kvaser device with the UAV’s main processing unit. The interface is built on ROS (Robotic Operating System), highly popular middleware for many robotic projects.[/vc_column_text][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column][vc_column_text]Pilon concludes: “The team hopes this will provide an easy way for other teams to use their Kvaser CAN interface to the maximum.”[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" advanced_params="1" header_size="h3" header_align="center" preheader="Image Gallery"][vc_gallery interval="3" images="12435,12438,12437,12439" img_size="870x374"][/vc_column][/vc_row] [post_title] => Team SONIA’s Autonomous Underwater Vehicle dives with Kvaser [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => team-sonias-autonomous-underwater-vehicle-dives-kvaser [to_ping] => [pinged] => [post_modified] => 2022-09-29 04:14:13 [post_modified_gmt] => 2022-09-29 04:14:13 [post_content_filtered] => [post_parent] => 0 [guid] => https://www.kvaser.com/?p=12421 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [6] => WP_Post Object ( [ID] => 39867 [post_author] => 1121 [post_date] => 2016-07-05 13:11:06 [post_date_gmt] => 2016-07-05 13:11:06 [post_content] => [vc_row][vc_column][vc_tabs interval="0"][vc_tab title="Improving Performance" tab_id="cf53f926-eb7b-10"][vc_video link="https://www.youtube.com/watch?v=ElJJzJcvBGU"][vc_row_inner][vc_column_inner width="2/3"][vc_column_text]In this video, we show how CAN FD makes it possible to increase performance in your CAN-system.[/vc_column_text][/vc_column_inner][vc_column_inner width="1/3"][vc_column_text][/vc_column_text][vc_button_raket title="CAN FD" text="Learn More" align="align_center" page_id="https://www.kvaser.com/about-can/can-fd/"][/vc_column_inner][/vc_row_inner][/vc_tab][vc_tab title="A Technical Comparison" tab_id="652d9cb1-0ff3-6"][vc_video link="https://www.youtube.com/watch?v=zuzFbeiUtI0"][vc_row_inner][vc_column_inner width="2/3"][vc_column_text]This video shows a comparison between how CAN, CAN FD, and Ethernet differ from one another.[/vc_column_text][/vc_column_inner][vc_column_inner width="1/3"][vc_column_text][/vc_column_text][vc_button_raket title="CAN FD" text="Learn More" align="align_center" page_id="https://www.kvaser.com/about-can/can-fd/"][/vc_column_inner][/vc_row_inner][/vc_tab][/vc_tabs][/vc_column][/vc_row][vc_row][vc_column][vc_accordion active_tab="false"][vc_accordion_tab title="Improving Performance Transcript"][vc_column_text] Hi, I am Kent Lennartsson. I am the research manager at Kvaser. In the previous part we showed why we need CAN and CAN-FD to get good real-time performance. In this part, it is shown how CAN-FD makes it possible to increase performance in your CAN-system. To show this, will I use some animations. CAN is designed in such way that no bit is corrupted during a collision. By prioritization it is possible to have 100% bus-load, without any delays caused by collision. With CAN-FD it is possible to increase the bit-rate from 1 up to 10 Mbit/s, still without any delays caused by collision. The good real time performance in CAN doesn’t come for free. In order to evaluate CAN frame priority, every bit needs to cover all connected units. The bit is spread over the cable by the speed of light. If the distance between units is less than 40 meters, it is possible to use up to 1 Mbit/s. If a longer cable is used, every bit needs more time to be distributed and the bit rate must be lowered to 250 or 500 kBits/s. CAN is very responsive when controlling a car or a machine, but doesn’t perform so well for sending video or large data files. However, with CAN FD it is possible to retain CAN’s good real-time behavior with much higher data throughput. Let us see, how CAN-FD is implemented in the CAN-frame. The first bit in the CAN-frame is the Start Of Frame, this is a single bit, that synchronizes all units connected to the CAN-bus and start the priority process. After this bit comes the priority section, where several units could be sending in parallel during the arbitration process. The CAN frame with the highest priority wins access to the bus line. The following part is the data part that will be sent by the single winner of the arbitration. After the data section, there is an end of frame, that synchronizes the units, in preparation for the next CAN frame. This ensures that it is possible to start a new CAN frame without any delay in-between. CAN’s limited bit-rate ensures that arbitration works successfully in the first part of the CAN-frame. The data section after arbitration is sent by one single unit. When there is just one sender, it is possible to increase the bit-rate. This possibility available in CAN is utilized by the CAN-FD standard. The beginning and the end of the CAN frame will keep the arbitration CAN bit-rate to secure the real time performance. This is the main difference between CAN and CAN FD. CAN FD increases the bit-rate by switching to a shorter bit time after the arbitration process and returns to the arbitration bit time after the CRC Delimiter. This CAN frame has one single byte of data. However, in CAN, it is possible to have up to 8 bytes of data. When data bytes, together with Data Length Code and CRC-bits, all framed in blue, are sent at a higher bit-rate, will it reduce the CAN frame length in time. CAN limit the number of bytes in a CAN frame to 8 Bytes. In CAN FD, it is possible to have up to 64 byte of data. By increasing the bit-rate on such a large frame, it’s possible to reduce the frame length considerably. The combination of CAN prioritized access to the communication and the higher bit-rate in CAN-FD makes it possible to combine advanced real-time performance and high data throughput. Your system can be optimized by using CAN FD technology in two different ways. Either, CAN-FD makes CAN-frames shorter in time, to decrease the delay and increase real-time performance. Or put more data bytes in the CAN-frames to decrease the overhead. Of course, it is possible to combine those two features by putting more data in the CAN FD frames and still make them shorter by increasing the bit-rate. Welcome to CAN FD. CAN-FD will bring better real time performance and higher data throughput in your existing CAN-system. With CAN-FD, you will get this high performance with minor changes to your software, hardware and the tools already in use today. Good luck with your CAN-FD projects. If you need more information go to our homepage, kvaser.com. Hope to see you back soon.[/vc_column_text][/vc_accordion_tab][vc_accordion_tab title="A Technical Comparison Transcript"][vc_column_text]Hi, I am Kent Lennartsson. I'm the research manager at Kvaser AB. I and Lars-Berno founded Kvaser in 1985. Our first CANbird was launched in 1989 based on the Phillips 82C200 and Intel 82856 CAN controller. This is a short overview of the CAN technology and the functionality of CAN FD important for the future CAN applications. We start with a quick history of CAN. The CAN protocol was first defined in mid 1980 by a team at Bosch led by Owe Kiencke. CAN was presented before a broader public in 1987 as the future data communication standard to be used by the automotive industry. The CAN protocol has some nice features optimized for real-time control systems. By 1989, very soon after the first publication, Dornier, a manufacturer of weaving looms, was using CAN in the airjet weaving machines. The first automotive application of CAN was in the Mercedes S Class 1993. Here is a simplified animation of a car. The driver expects a direct response to any input, like controlling the headlight, is not good enough to be responsive in 99.99% of the cases. The driver expects the car to respond accurately each and every time over the car's entire lifetime. A communication delay would be as bad as having air in the brake lines. In this simplified view of the car there are four control units. One at the brake pedal, sensing how hard the driver compresses the pedal, one at the front wheel braking, one for rear wheel braking, and one for displaying the braking condition to cars behind. All control units are connected together by the data communication bus line. By 1973, Ethernet was already running at 3MB/s. Today Ethernet supports speeds of 10, 100 and even 1000MB/s. There is a certain probability that two units will start sending an Ethernet frame at the same time. This will result in a collision and the sending process will stop. All units wait a random delay time before they restart sending. If after such delay collisions still occur, the random delay time is increased until one unit starts sending before all other units. Ethernet is very efficient as long as there is no collision. If the busload is high, the transfer delay can increase significantly due to collision. There are solution where additional rules can be added on top of the Ethernet protocol to reduce or even remove this problem. With CAN collision is solved without any delay. With CAN every package has a priority level. There can be up to 53 million different priority levels in CAN. In this example we only show four levels. As soon as there is no traffic on the CAN bus, any unit can send package. At this point CAN function is same as Ethernet. The difference occurs when there is a collision. In CAN the collision can be resolved in real time because the highest priority package will be sent first. There is no priority between the different units and a unit can send packages with different priorities. CAN is designed in such a way that no bit is corrected during a collision. This makes it possible to have 100% busload without causing any delays. The cost for this nice feature is a bit-rate below 1MB/s. With CAN FD it is possible to increase the bit-rate from 1 to 10MB/s still without any delay caused by the collisions. Here we have one of our products supporting CAN FD. In this case it's the PCI-Express board with four CAN FD controllers. All four in these Atera FPGA. Such a board is installed in this computer here running a CAN FD application and the bus from that application is connected to the oscilloscope here where we can see a classic CAN frame with 8 byte of data. If we switch to CAN FD we will see that the length of the message is decreased to 20% of the classical CAN frame. CAN FD also support 64 byte of data and you can see here how we increase the number of byte from 8 to 64 where the CAN FD frame become longer. Still, the CAN FD frame is only 50% of the classical CAN frame with 8 byte of data. In coming with use we will describe how CAN FD provide this higher bit-rate and more data into the CAN frame. Good luck now with your CAN FD projects and if you need more information go to our homepage. Hope to see you soon.[/vc_column_text][/vc_accordion_tab][/vc_accordion][/vc_column][/vc_row] [post_title] => CAN FD with Kent Lennartsson [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => can-fd-with-kent-lennartsson [to_ping] => [pinged] => [post_modified] => 2022-10-04 13:12:11 [post_modified_gmt] => 2022-10-04 13:12:11 [post_content_filtered] => [post_parent] => 0 [guid] => https://www.kvaser.com/?post_type=developer_blog&p=39867 [menu_order] => 0 [post_type] => developer_blog [post_mime_type] => [comment_count] => 0 [filter] => raw ) [7] => WP_Post Object ( [ID] => 12218 [post_author] => 23 [post_date] => 2016-06-14 07:00:39 [post_date_gmt] => 2016-06-14 07:00:39 [post_content] => [vc_row][vc_column][vc_column_text]The next two weeks are packed with events around the world. Take a look at where you can find Kvaser at upcoming events![/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Commented Lars-Berno Fredriksson, president of Kvaser AB: “This two channel combined interface and datalogger in Kvaser’s trademark form factor is our most advanced yet. The extra memory capacity on the Kvaser Memorator Pro 2xHS v2 makes it the ultimate ‘troubleshooter’, providing the headroom needed to detect intermittent faults over several days or weeks. Along with the capacity to split log files during extraction, users won’t find themselves combining successive logfiles from two or three different memory cards ever again.”The Kvaser Memorator Pro 2xHS v2 has two 9 pin DSUBs, and one USB connector. When connected to the host computer, the Memorator Pro 2xHS v2 is automatically in interface mode and when connected only to CAN, it is in datalogger mode. It also has an internal battery to handle short periods of power loss during logging. The Kvaser Memorator Pro 2xHS v2 is compatible with J1939, CANopen, NMEA 2000® and DeviceNet. This device is also fully CAN FD compliant up to 8Mbit/s. It is supported in the latest versions of CANLIB and Kvaser Memorator Config Tool software. Kvaser qualified reseller and technical associate Accurate Technologies will be displaying the Kvaser Memorator Pro 2xHS v2 at Automotive Testing Expo Europe, booth number 1542. [post_title] => Dual channel, CAN FD compliant interface and datalogger with scripting capabilities debuts at Automotive Testing Expo 2016 [post_excerpt] => [post_status] => publish [comment_status] => closed [ping_status] => closed [post_password] => [post_name] => dual-channel-can-fd-compliant-interface-datalogger-scripting-capabilities-debuts-automotive-testing-expo-2016 [to_ping] => [pinged] => [post_modified] => 2022-09-29 04:14:12 [post_modified_gmt] => 2022-09-29 04:14:12 [post_content_filtered] => [post_parent] => 0 [guid] => https://www.kvaser.com/?p=12131 [menu_order] => 0 [post_type] => post [post_mime_type] => [comment_count] => 0 [filter] => raw ) [9] => WP_Post Object ( [ID] => 12145 [post_author] => 5 [post_date] => 2016-05-30 05:33:36 [post_date_gmt] => 2016-05-30 05:33:36 [post_content] => [vc_row el_class="full_width"][vc_column][vc_single_image image="12149" img_size="full"][vc_column_text] The CAN Calibration Protocol (CCP) and Universal Measurement and Calibration Protocol (XCP) protocols for reading measurement data and writing parameters to electronic control units (ECUs) are now commonly used during development, testing and in-vehicle calibration. Developed by the Association for Standardization of Automation and Measuring Systems (ASAM), CCP was designed purely for CAN networking applications, whilst its successor, XCP – introduced in the early 2000s – caters for a variety of transport layers, including LIN, FlexRay, Ethernet and, of course, CAN. As with any standard, it is impossible to specify every detail for every application, so experienced, trustworthy suppliers are essential to delivering robust solutions. [/vc_column_text][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column][vc_column_text] Whilst the CCP and XCP higher layer protocols were intended as universal standards, many vehicle OEMs have implemented them in slightly different ways. A notable example is ECU security, where proprietary usage is not standard and yet is increasingly necessary. For software tool providers, a tailor-made approach – demanding considerable cooperation between the software vendor and the customer – is usually required to optimise the calibration toolchain. [/vc_column_text][/vc_column][/vc_row][vc_row el_class="full_width"][vc_column][vc_column_text] [/vc_column_text][vc_column_text]
Request more information before you complete the purchase.