WP_Query Object
(
[query] => Array
(
[paged] => 16
[pagename] => about-us/news
)
[query_vars] => Array
(
[paged] => 16
[pagename] => about-us/news
[error] =>
[m] =>
[p] => 0
[post_parent] =>
[subpost] =>
[subpost_id] =>
[attachment] =>
[attachment_id] => 0
[name] =>
[page_id] => 0
[second] =>
[minute] =>
[hour] =>
[day] => 0
[monthnum] => 0
[year] => 0
[w] => 0
[category_name] =>
[tag] =>
[cat] =>
[tag_id] =>
[author] =>
[author_name] =>
[feed] =>
[tb] =>
[meta_key] =>
[meta_value] =>
[preview] =>
[s] =>
[sentence] =>
[title] =>
[fields] =>
[menu_order] =>
[embed] =>
[category__in] => Array
(
)
[category__not_in] => Array
(
[0] => 1047
)
[category__and] => Array
(
)
[post__in] => Array
(
)
[post__not_in] => Array
(
)
[post_name__in] => Array
(
)
[tag__in] => Array
(
)
[tag__not_in] => Array
(
)
[tag__and] => Array
(
)
[tag_slug__in] => Array
(
)
[tag_slug__and] => Array
(
)
[post_parent__in] => Array
(
)
[post_parent__not_in] => Array
(
)
[author__in] => Array
(
)
[author__not_in] => Array
(
)
[orderby] => date
[post_type] => Array
(
[0] => post
[1] => developer_blog
)
[post_status] => publish
[order] => DESC
[tax_query] => Array
(
[0] => Array
(
[taxonomy] => blog-group
[field] => slug
[terms] => Array
(
[0] => public
)
[operator] => IN
)
[1] => Array
(
[taxonomy] => blog-group
[field] => slug
[terms] => Array
(
[0] => general-user
[1] => technical-asociate
[2] => qualified-sales-representative
[3] => kvaser-internal
)
[operator] => NOT IN
)
)
[ignore_sticky_posts] =>
[suppress_filters] =>
[cache_results] => 1
[update_post_term_cache] => 1
[lazy_load_term_meta] => 1
[update_post_meta_cache] => 1
[posts_per_page] => 10
[nopaging] =>
[comments_per_page] => 50
[no_found_rows] =>
[taxonomy] => blog-group
[term] => public
)
[tax_query] => WP_Tax_Query Object
(
[queries] => Array
(
[0] => Array
(
[taxonomy] => blog-group
[terms] => Array
(
[0] => public
)
[field] => slug
[operator] => IN
[include_children] => 1
)
[1] => Array
(
[taxonomy] => blog-group
[terms] => Array
(
[0] => general-user
[1] => technical-asociate
[2] => qualified-sales-representative
[3] => kvaser-internal
)
[field] => slug
[operator] => NOT IN
[include_children] => 1
)
[2] => Array
(
[taxonomy] => category
[terms] => Array
(
[0] => 1047
)
[field] => term_id
[operator] => NOT IN
[include_children] =>
)
)
[relation] => AND
[table_aliases:protected] => Array
(
[0] => wp_term_relationships
)
[queried_terms] => Array
(
[blog-group] => Array
(
[terms] => Array
(
[0] => public
)
[field] => slug
)
)
[primary_table] => wp_posts
[primary_id_column] => ID
)
[meta_query] => WP_Meta_Query Object
(
[queries] => Array
(
)
[relation] =>
[meta_table] =>
[meta_id_column] =>
[primary_table] =>
[primary_id_column] =>
[table_aliases:protected] => Array
(
)
[clauses:protected] => Array
(
)
[has_or_relation:protected] =>
)
[date_query] =>
[queried_object] => WP_Post Object
(
[ID] => 1277
[post_author] => 38
[post_date] => 2014-11-21 12:03:40
[post_date_gmt] => 2013-12-19 15:28:51
[post_content] =>
[post_title] => News
[post_excerpt] =>
[post_status] => publish
[comment_status] => open
[ping_status] => open
[post_password] =>
[post_name] => news
[to_ping] =>
[pinged] =>
[post_modified] => 2021-08-12 09:14:30
[post_modified_gmt] => 2021-08-12 09:14:30
[post_content_filtered] =>
[post_parent] => 23
[guid] => https://www.kvaser.com/?page_id=1277
[menu_order] => 5
[post_type] => page
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[queried_object_id] => 1277
[request] => SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND (
wp_term_relationships.term_taxonomy_id IN (1026)
AND
wp_posts.ID NOT IN (
SELECT object_id
FROM wp_term_relationships
WHERE term_taxonomy_id IN (1025,1027,1028,1029)
)
AND
wp_posts.ID NOT IN (
SELECT object_id
FROM wp_term_relationships
WHERE term_taxonomy_id IN (1058)
)
) AND wp_posts.post_type IN ('post', 'developer_blog') AND ((wp_posts.post_status = 'publish')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 150, 10
[posts] => Array
(
[0] => WP_Post Object
(
[ID] => 29331
[post_author] => 6
[post_date] => 2020-09-02 18:37:41
[post_date_gmt] => 2020-09-02 18:37:41
[post_content] => [vc_row][vc_column][vc_single_image image="13763"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]As scientific challenges go, you can’t get much bigger than recreating conditions as they occurred immediately after the Big Bang. This is this mission of the CERN Large Hadron Collider (LHC), which smashes protons to further humanity’s understanding of a wide range of theoretical physical phenomena, including answering the question of what is mass, investigating extra dimensions and the particles that make up dark matter.[/vc_column_text][vc_column_text]During the LHC’s first run (2008–2012), among the successes chalked up was identification of the elusive Higgs boson. During the second run (2015–2018), the energy used to produce the collisions was increased and more data was collected from the two particle detectors, ATLAS and CMS, in order to observe more clearly the interplay between particles. At 46 m long, 25 m high and 25 m wide, ATLAS is the largest of the two detectors, comprising six detecting subsystems arranged in layers around an inner chamber.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_column_text]Aside from the data created by the experiment itself (recording the collision paths, momentum and energy of the particles), monitoring and controlling ATLAS is a data challenge in itself that is entirely run on CAN. During the LHC’s first run, hundreds of Kvaser’s PCIcanx boards played an important role within ATLAS, providing the link between the 7000-tonne detector and the 100 or so PCs that control and supervise it in ATLAS’ electronics rooms. Each of the PCs had up to three Kvaser cards, controlling over 5000 CAN nodes on more than 300 CAN buses and using CANopen as the high-level communication protocol.[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="29217"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]The CANbus nodes were designed and developed by ATLAS in collaboration with the National Institute for Nuclear Physics and High Energy Physics in Amsterdam and the Petersburg Nuclear Physics Institute. Referred to by the researchers as Embedded Local Monitoring Boards (ELMBs), Kvaser worked with ATLAS staff to optimise the PCICanx boards to suit the ELMBs needs.[/vc_column_text][vc_column_text]Asked why Kvaser’s boards were chosen, Dr Burckhart, in charge of the ATLAS Detector Control System (DCS) project at the time said:[/vc_column_text][vc_column_text]
“Kvaser’s initial form factor already fit well with our requirements. And following our suggestions they made a new version of their board, which exactly matched our needs. An additional plus was that they had CAN interface cards in USB and PCMCIA form factors which support the same application software. Kvaser was also very responsive when initial software fixes were needed.”
[/vc_column_text][vc_column_text]Among the physical requirements determining CERN’s choice of a CAN interface board was that each port would need an independent buffer and be independently controlled (so resetting one port wouldn’t affect another). From a software perspective, it was necessary to support Windows and Linux, and that a simple and intuitive API was needed.[/vc_column_text][vc_column_text]
“We were very happy with Kvaser’s PCICan cards and they ran very stably,”
[/vc_column_text][vc_column_text]confirmed Dr. Stefan Schlenker, now responsible for the ATLAS detector controls at CERN. Dr. Schlenker took over from Dr. Helfried Burckhart, who led the specification of the system. As Dr Burckhart explained, CAN was an automatic choice:[/vc_column_text][vc_column_text]
“It is robust, has good industrial support (including at the chip level), is inexpensive and provided adequate functionality.” Dr Schlenker confirms that ATLAS’ CAN system “is foreseen to operate for at least another 15 years with minor modifications.”
[/vc_column_text][vc_column_text]In 2013 and 2014, during CERN’s first long shutdown, the control system was updated as it was becoming more difficult to find PCI-based servers, and it was necessary to increase CAN port density. ATLAS moved to rack-mounted CAN to USB interfaces, with two USB ports serving 16 CAN ports.[/vc_column_text][vc_column_text]As speeds continue to increase within the LHC, so the detector control system (DCS) must evolve too. Whilst no major control system changes are planned during CERN’s second long shutdown (2020/2021), with many parts of the detector programmed for renewal during the next shutdown in 2025 – in particular, a move to an all silicon inner detector – more fundamental updates to the control system will be needed at that time. The original DCS monitored some 200,000 slowly changing parameters, such as voltage, current, temperature and pressure. Beyond 2024, the volume of data increases to millions of readouts per few seconds, so a move to CAN-to-Ethernet cards is scheduled for that time.[/vc_column_text][/vc_column][/vc_row]
[post_title] => CERN’s ATLAS project: A CAN control network of epic scale
[post_excerpt] => CERN's ATLAS project utilizes CANopen, via Kvaser's PCIcanx products, to control a CAN network and experiment of epic proportions.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => cerns-atlas-project-a-can-control-network-of-epic-scale
[to_ping] =>
[pinged] =>
[post_modified] => 2022-04-04 10:19:12
[post_modified_gmt] => 2022-04-04 10:19:12
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=29331
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[1] => WP_Post Object
(
[ID] => 29279
[post_author] => 38
[post_date] => 2020-09-02 05:54:28
[post_date_gmt] => 2020-09-02 05:54:28
[post_content] =>
[post_title] => In-Vehicle Communication Standards for Trucks: Where Do We Go With J1939? [Featuring Bryan Hennessy]
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => in-vehicle-communication-standards-for-trucks-where-do-we-go-with-j1939-featuring-bryan-hennessy
[to_ping] =>
[pinged] =>
[post_modified] => 2020-09-02 05:54:28
[post_modified_gmt] => 2020-09-02 05:54:28
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=29279
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[2] => WP_Post Object
(
[ID] => 29158
[post_author] => 6
[post_date] => 2020-08-18 18:17:54
[post_date_gmt] => 2020-08-18 18:17:54
[post_content] => [vc_row][vc_column][vc_single_image image="29168"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Editor's note: This event has already passed. If you would like to know about future webinars, you can create a MyKvaser account, or if you already have one, you can go to your settings and sign up for our monthly newsletter here where we share case studies, event schedules, and updates about our products.[/vc_column_text][vc_column_text]Learn how to use the Kvaser-ATI toolchain to log, import, and analyze vehicle CAN data.
The 60-minute webinar will demonstrate how to use a standalone CAN datalogger to record vehicle data and import that data into analysis software. Topics will cover logger configuration, DBC file usage, import/export process, file formats, and signal analysis. Bryan Hennessy (Kvaser Inc.) will teach the specifics of using Kvaser Memorator series products for CAN data recording, while ATI’s Maxwell Church will provide a tutorial on handling the data in the CANLab software.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
Session 1 (REGISTRATION IS FULL)
Title:CAN Datalogging: A Quickstart Guide to Logging, Importing, and Analyzing Vehicle Data
Date: Wednesday,19th August 2020
Time: 11:00 EST
Venue: Zoho Showtime
Register Here
(Session is full and not accepting new registrants, please register for Session 2 below)
Session 2
Title: CAN Datalogging: A Quickstart Guide to Logging, Importing, and Analyzing Vehicle Data
Date: Tuesday, 25th August 2020
Time: 11:00 EST
Venue: Zoho Showtime
Register Here >>
[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_separator_raket][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" header="Meet The Trainers"][/vc_column][/vc_row][vc_row][vc_column width="3/4"][vc_column_text]Bryan Hennessy (Kvaser)
Bryan has a history in design engineering, applications engineering, project management and small business ownership, which all contribute to his knowledge in the electronics industry. Bryan’s time and training as a field applications engineer gave him the extensive knowledge in supporting electronic products as well as working with large strategic customers.[/vc_column_text][/vc_column][vc_column width="1/4"][vc_single_image image="29162"][/vc_column][/vc_row][vc_row][vc_column width="3/4"][vc_column_text]Maxwell Church (ATI)
Max has a long history of technical sales and support experience. His debut in the automotive prototype testing and development industry began in 1991, and he has since worked in a wide variety of roles such as prototype build and instrumentation technician, purchasing, application engineer, and sales manager. Currently Max is a part of the business development team at ATI.[/vc_column_text][/vc_column][vc_column width="1/4"][vc_single_image image="29163"][/vc_column][/vc_row]
[post_title] => Webinar: CAN Datalogging with Accurate Technologies
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => webinar-can-datalogging-with-accurate-technologies
[to_ping] =>
[pinged] =>
[post_modified] => 2022-04-04 10:19:12
[post_modified_gmt] => 2022-04-04 10:19:12
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=29158
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[3] => WP_Post Object
(
[ID] => 28978
[post_author] => 22955
[post_date] => 2020-08-12 16:28:34
[post_date_gmt] => 2020-08-12 16:28:34
[post_content] => [vc_row][vc_column][vc_single_image image="32821"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Bryan Hennessy, Kvaser Technical Partner Manager, and Amir Rezaei, Senior Control Systems Engineer at Pi Innovo, created a Combined Charging System demonstrator for The Battery Show, North America.[/vc_column_text][vc_column_text]The system highlighted Pi Innovo’s Combined Charging System and Open ECU to implement the charging protocol in a battery management system, while Kvaser’s DIN Rail products and t program scripting language were utilized as an Electrical Vehicle Supply Equipment (EVSE) simulation and test circuit, to provide simulated hardware and software handshakes.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image image="32823" img_size="large"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]The end goal was to demonstrate the Combined Charging System’s ability to manage a CAN-based electric charging session.[/vc_column_text][vc_column_text]The full demonstration configuration consisted of two systems:
- Pi Innovo’s Combined Charging System and Open ECU units
- Kvaser’s DIN Rail 400SE-X10-based simulation and test circuit
[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column width="5/6"][vc_single_image image="32820"][/vc_column][vc_column width="1/6"][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="Combined Charging System (CSS)"][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_column_text]Pi Innovo’s Combined Charging System (CCS) is an applications source code product provided in Simulink models that implements IEC 61851-1, DIN 70121, SAE J2847 and SAE J1772 charging system development. [/vc_column_text][vc_column_text]M560 and M580 OpenECU modules are combined with CCS for development of a complete vehicle charging system.
The CCS was loaded onto the OpenECU module and used to manage the series of CAN-based interactions during the simulated vehicle charging session.[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="28985" onclick="custom_link" link="https://www.pi-innovo.com/open-ecu/"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Rezaei explains:
"OpenECU M560 and M580 are designed to meet ISO 26262 ASIL D functional safety for complex hybrid and EV control applications...
These control units are also equipped with the required hardware to interface and communication data with offboard AC and DC chargers. The OpenECU platform supports model-based programming in Simulink and runtime software calibration with different calibration tools such as ATI Vision, CANape, INCA or Pi Snoop."
[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="EVSE simulation and test circuit"][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_column_text]An Electrical Vehicle Supply Equipment (EVSE) used Kvaser DIN Rail modules, a resistor network and t programming to provide simulated hardware and software handshakes..
The new Kvaser DIN Rail hardware was used because of the need for digital and analogue I/O and controllable relays provided by the I/O modules that are optically coupled with the SE400X-X10 controller.
External circuits were needed to provide the hardware handshake required to detect connection to the vehicle, and manage the hardware handshakes required to simulate the charging sequence .[/vc_column_text][vc_column_text]Commented Hennessy:
"Kvaser’s DIN Rail products offer complete flexibility when creating simulation and/or test circuits that incorporate CAN interfaces. With all the I/O, plus four CAN channels, relays for higher voltages, analog functions, and the complete power of CANlib SDK or t programming to create test or simulation code, this system gives engineers an easy way to build exactly what they need."
[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="32822" onclick="custom_link" link="https://www.kvaser.com/product/kvaser-din-rail-se400s-x10/"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Kvaser’s t program scripting language was used for its ease in CAN message generation and reception, light weight and free Integrated Development Environment, and functionality with multiple Kvaser Pro products[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="Summary"][vc_column_text]The result was a simple, effective demonstration of battery charging communication.
Pi Innovo’s OpenECU M560 or M580 supervisory controllers and the OpenECU software platforms showed the ability to implement whichever AC or DC charging protocol is required, in accordance with SAE J1772 and DIN SPEC 70121.
The EVSE provided by Kvaser simulated the hardware and software handshakes required. The EVSE also helped Pi Innovo validate error handling code, message timing variations handling, charge interruption routines, and many other charging situations that are difficult to reproduce on the bench.[/vc_column_text][vc_separator_raket][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h2" header="Further Reading"][vc_column_text]
[/vc_column_text][/vc_column][/vc_row]
[post_title] => Simulating an Electric Vehicle Charging Station: Battery Show Demo Walkthrough
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => simulating-an-electric-vehicle-charging-station-battery-show-demo-walkthrough
[to_ping] =>
[pinged] =>
[post_modified] => 2023-08-08 12:12:29
[post_modified_gmt] => 2023-08-08 12:12:29
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=28978
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[4] => WP_Post Object
(
[ID] => 28881
[post_author] => 38
[post_date] => 2020-08-04 18:53:00
[post_date_gmt] => 2020-08-04 18:53:00
[post_content] => [vc_row][vc_column][vc_row_inner][vc_column_inner width="1/2"][vc_column_text]A cough aerosol simulator that uses CAN as the primary communication protocol is being used to study how well face masks and face shields block cough aerosols. The system was originally developed by Bill Lindsley and colleagues from the US National Institute for Occupational Safety and Health (NIOSH) to simulate a coughing patient in a medical examination room, but has since been used to research
the efficacy of ventilation systems in ambulances in limiting the exposure of staff to airborne particles, as well as protective measures to
limit airborne particle spread in aircraft.[/vc_column_text][/vc_column_inner][vc_column_inner width="1/2"][vc_single_image image="28882"][/vc_column_inner][/vc_row_inner][vc_column_text]The mobile simulator uses a Kvaser Leaf Light to connect a linear motor from
Copley Controls and the research team’s computer via CAN.[/vc_column_text][vc_button_raket title="DOWNLOAD PDF" text="White Paper" page_id="https://canlandbucket.s3-eu-west-1.amazonaws.com/productionResourcesFiles/504e8343-7eee-4844-89b1-ff3cbb4aa0b6/Lindsley_2019_Ambulance_ventilation_system_preprint.pdf"][/vc_column][/vc_row]
[post_title] => Studying the efficacy of face masks involves CAN
[post_excerpt] => A cough aerosol simulator that uses CAN as the primary communication protocol is being used to study how well face masks and face shields block cough aerosols.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => studying-the-efficacy-of-face-masks-involves-can
[to_ping] =>
[pinged] =>
[post_modified] => 2023-08-10 07:34:29
[post_modified_gmt] => 2023-08-10 07:34:29
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=28881
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[5] => WP_Post Object
(
[ID] => 28562
[post_author] => 910
[post_date] => 2020-06-29 04:52:12
[post_date_gmt] => 2020-06-29 04:52:12
[post_content] => [vc_row][vc_column][vc_column_text]I have not been able to find a good hexadecimal explanation site, so here’s an overview in my own words, with a few links for you to explore.
Understanding hexadecimal (hex) and binary is all about understanding numbering systems, or number bases. What we use every day is base ten, hexadecimal is base sixteen and binary is base two.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" header="Base ten is decimal"][vc_column_text]
In base ten, we have ten digits that represent a number; zero through nine, or 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9. When we get to 9, we shift left and start over at 10, 11, 12, 13,……19. We then go to 20.
Large decimal numbers are shown in sets of three with a comma between sets; 123,456,789.[/vc_column_text][vc_header_raket header_type="h3" header="Base sixteen is hexadecimal, or 'hex'"][vc_column_text]
In base sixteen, we have sixteen digits that represent a number; zero through F, or 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, and F. When we get to F, we shift left and start over at 10, 11, 12, 13, … 1F. We then go to 20.
Large hexadecimal numbers are shown in sets of two with a space between sets; 78 9A BC DE. A set of two hex characters is called a byte.[/vc_column_text][vc_header_raket header_type="h3" header="Base two is binary"][vc_column_text]
In base two, two digits represent a number; zero and one, or 0 and 1. When we get to 1, we shift left and start over at 10, 11, 100, 101, 110, … 1111. We then go to 0001 0000.
Large binary numbers are shown in sets of four with a space between sets, and zeros are used to make all sets of four; '0001 0101 1101 1111'.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" header="Binary vs hex"][vc_column_text]
There is a relationship between binary and hex. One hex character represents a block of four binary characters. See the table below:[/vc_column_text][vc_single_image image="42266"][/vc_column][/vc_row][vc_row][vc_column width="1/6"][/vc_column][vc_column width="2/3"][vc_single_image image="28563"][/vc_column][vc_column width="1/6"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
A binary character is called a bit. Computers and digital communications work in binary.
Eight bits make up a byte, and a byte is usually represented by two hex characters, like 3E or B8.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" header="More links to explore:"][vc_column_text]
[/vc_column_text][/vc_column][/vc_row]
[post_title] => Hexadecimal and Binary Numbering Systems
[post_excerpt] => Understanding hexadecimal (hex) and binary is all about understanding numbering systems, or number bases. Here’s an overview, with a few links to explore.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => hexadecimal-and-binary-numbering-systems
[to_ping] =>
[pinged] =>
[post_modified] => 2023-07-26 06:08:13
[post_modified_gmt] => 2023-07-26 06:08:13
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?post_type=developer_blog&p=28562
[menu_order] => 0
[post_type] => developer_blog
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[6] => WP_Post Object
(
[ID] => 28556
[post_author] => 22709
[post_date] => 2020-06-26 09:50:43
[post_date_gmt] => 2020-06-26 09:50:43
[post_content] =>
[post_title] => Intelligent data logger for electric trucks; Case study from TK Engineering
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => tke-case-study
[to_ping] =>
[pinged] =>
[post_modified] => 2022-04-04 10:19:11
[post_modified_gmt] => 2022-04-04 10:19:11
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=28556
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[7] => WP_Post Object
(
[ID] => 28270
[post_author] => 4840
[post_date] => 2020-06-17 01:21:58
[post_date_gmt] => 2020-06-17 01:21:58
[post_content] => [vc_row][vc_column][vc_column_text]
In this article, "Comparing CAN interface transfer delays", I will test and compare four different types of Kvaser CAN interfaces.[/vc_column_text][vc_column_text]
- PCIe interfaces mounted on the motherboard
- USB connected external interfaces
- Ethernet connected interfaces
- WLAN (WiFi) connected interfaces
[/vc_column_text][vc_column_text]
The goal is to measure and compare the difference in transfer delay between interface types.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_single_image image="28271"][/vc_column][vc_column width="1/3"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
The CAN-BUS I used for testing is built using four Kvaser T-Cannector v2s and is terminated at each end. During the tests I had 7 interfaces connected with a total of 13 channels.
All interfaces are connected to the same computer. I use a Router to make sure that I isolate the Ethernet interfaces from unwanted traffic. The Router is also a Wi-Fi access point.
One of the PCIE interfaces is used as a receiver. (The PCIE interfaces were shown to be the fastest ones, with variation between the different PCIE cards extremely low).
The target is to measure the Transfer Delay Time. I define this delay as:
The time needed from when the software has a package that shall be transmitted, until the time when the software has received it (on another channel).[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" header="1. Comparison Tests - Transfer Delay Time"][vc_column_text]
Sending a standard CAN message, 11 bit ID and 8 byte data payload.
With a 1MBit/s bitrate, this message takes approximately 110 µs to transfer on the CAN bus (measured with an oscilloscope). Please note that I am actually sending many messages, and calculating the mean time of transfer delay.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_single_image image="28272"][/vc_column][vc_column width="1/3"][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h4" header="1.1 Checking internal interface delay"][vc_column_text]
Sending and receiving with a Kvaser PCIEcan 4xHS, I measure a total delay of 225µs. (From pressing the TX button until the software has used the CANRead command).
The CAN msg occupies appr 110µs on the CAN-bus. The CANWrite command takes appr 25µs.
225 minus 110 minus 25 is 90µs.[/vc_column_text][vc_single_image image="28273"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
So we need to find out what happens during these 0.090ms. The message is stored somewhere in the electronics. Most probably it spends 45µs in the transmit queue and after that, 45µs in the receiving queue. (I have no method of checking that without doing some advanced measurements on the card, so I assume that both processes take the same amount of time).
According to this analysis, the PCIE interface delay is 45µs.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h4" header="1.2 Comparing interface types"][vc_column_text]
I use the values from [1.1. Checking internal interface delay] and the measured delay times and calculate the TX queue times for the different interface types.[/vc_column_text][vc_single_image image="28274"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
PCIE connected interface
[/vc_column_text][vc_column_text]
As seen in the tables above, the delays are extremely low and it is most probably the fastest method available for connecting a CAN interface.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
USB connected interface
[/vc_column_text][vc_column_text]
I used our most popular product, the Kvaser Leaf Light HS v2. This is not our fastest USB CAN interface, but it is a good example of a typical USB interface. As we can see in the table above, it adds an extra delay of 100µs when compared to a PCIE interface.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
LAN connected interface
[/vc_column_text][vc_column_text]
I used two of our LAN connected products, the Kvaser DIN Rail SE400S-X10 and the Kvaser Ethercan HS.Both show almost the same results. Compared to the PCIe cards, they add an extra delay of 225µs when compared to a PCIE interface.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
WLAN (WiFi) connected interface
[/vc_column_text][vc_column_text]
I used the Kvaser BlackBird v2 to test WLAN interfaces. I connected it in two different modes. The standard infrastructure mode and the Windows Hosted Mode. I measure a total delay of 1ms and 2ms when compared to a PCIE interface[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
Conclusion
[/vc_column_text][vc_column_text]
If you need very fast response times, then you should select the PCIe or USB connected interfaces. They provide a stable and secure connection to your CAN bus. The LAN connected interfaces are also a good choice, but it is important to understand that the increased transfer delay can cause problems in some applications. When using the WLAN interfaces, it is important to remember that the WiFi environment can cause long transfer delays.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h4" header="1.3 Comparing slower bitrate transmissions"][vc_column_text]
What happens if we use 250kBit/s and 29 bit ID?
An 8 byte CAN message with 29 bit ID takes approximately 520 us to transfer. I adjust the table from [1.2. Comparing interface types] :[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_single_image image="28275"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
When looking at the SUM, the PCIE, USB and LAN interfaces, give almost the same result. So in this case, selection of which interface family to use more or less depends upon how you want to connect to your CAN-bus.
PCIE interfaces require stationary hardware, USB interfaces allow you to be more flexible and the LAN interfaces make it possible to extend the distance between the CAN-bus and the client. The WLAN interfaces are also a good choice, especially in situations where the user is “monitoring” an object.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h3" header="2. APPENDIX A"][vc_header_raket header_type="h4" header="2.1 My own software"][vc_column_text]
To be able to detect the delays between sending and receiving data, I made a very simple program that detects the time when sending a package and the time of package receipt.
I wrote the basic test program in DELPHI (Pascal) and it uses Kvaser CANLib. It is not super optimized.[/vc_column_text][vc_column_text]
Timer resolution
[/vc_column_text][vc_column_text]
I am using the Performance Counter provided by the Windows operating system and the CPU. On my hardware, the frequency of this counter is 10MHz. That gives me a resolution of 0.1us. [/vc_column_text][vc_column_text]
Precision of results
[/vc_column_text][vc_column_text]
Please note, the variance of the results can be quite high, ±50% is not uncommon, so be a bit careful when using the results. Use the numbers more as a guideline.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_single_image image="28276"][/vc_column][vc_column width="1/3"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
Procedure in word:
- Something triggers the TX sequence. In most cases, it is me clicking on a button.
- As quickly as possible, readout the performance counter. This value is T0 (Time Zero).
- Add this T0 into a CAN message, and transmit it via the desired interface (channel).
- Now the software has to wait until CANlib sends an event, “CAN DATA available”.
- As quickly as possible, readout the performance counter. This value is T1.
- Read the CAN message from the CANlib buffer.
- Now we have: A CAN message, where the ID identifies the sender, and the payload contains T0.
- We can now subtract T0 from T1, and get the transfer delay, dT=T1-T0.
[/vc_column_text][vc_column_text]
Now we know the sender's ID and the transfer delay.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h4" header="2.2 CAN package used "][vc_column_text]
When I send a CAN frame, or “package”, I use an 11 bit identifier and 8 data bits.
At 1MBit baud rate, a package like this is approximately 110µs long.
(The size differs a bit because of the stuff bits that are added).
The ID will hold the HANDLE of the transmitting interface.
The 8 data bytes will hold the value of the Performance counter (UINT64).
This makes it possible for the receiving procedure to determine who sent it, and most important, when it was sent.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_header_raket header_type="h4" header="2.3 Hardware used"][vc_column_text]
2.3.1 CAN interfaces used
[/vc_column_text][vc_column_text]
[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
2.3.2 CAN test equipment used
[/vc_column_text][vc_column_text]
[/vc_column_text][vc_column_text]
2.3.3 Computer
[/vc_column_text][vc_column_text]
The computer is a standard Windows 10 machine.
- Processor: Intel Core i7 4770 3.4GHz
- Motherboard: Gigabyte Z87X-UD5H-CF
[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
2.3.4 Router
[/vc_column_text][vc_column_text]
- Dovado TINY AC
- This is a typical home router, I used it as a WiFi router, DHCP server and LAN provider.
[/vc_column_text][vc_column_text]
2.3.5 Switch
[/vc_column_text][vc_column_text]
[/vc_column_text][/vc_column][/vc_row]
[post_title] => Comparing CAN interface transfer delays
[post_excerpt] => Testing four different types of Kvaser CAN interfaces in order to compare the difference in transfer delay between interface types.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => comparing-can-interface-transfer-delays
[to_ping] =>
[pinged] =>
[post_modified] => 2020-06-18 21:11:04
[post_modified_gmt] => 2020-06-18 21:11:04
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?post_type=developer_blog&p=28270
[menu_order] => 0
[post_type] => developer_blog
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[8] => WP_Post Object
(
[ID] => 28392
[post_author] => 5
[post_date] => 2020-06-09 09:40:44
[post_date_gmt] => 2020-06-09 09:40:44
[post_content] => [vc_row][vc_column][vc_single_image image="21662"][vc_column_text]Kvaser's latest software release supports Linux 5.6 kernel.
Notable changes and additions include:
Python canlib package (pycanlib): Support has been dropped for v2.7, v3.4 and v3.5, but added for v3.7 and v3.8.
Kvaser Drivers for Windows SDK (canlib): This release fixes a bug that made programs fail when run on a computer with older CANlib drivers installed. If you are distributing the canlib32.dll as part of your application, please update to this version (V5.33). It is good practice to check the status return from CANlib function calls, to check that nothing is amiss.
Kvaser Drivers for Linux SDK (canlib): This has been updated for kernel v5.6.0. In this kernel version, the timeval identifier has been replaced with timespec64, so Kvaser’s code has changed accordingly. Firmware for mhydra-based devices: Autobaud detection has been improved for the Kvaser Memorator Light HS v2, whilst the Kvaser Blackbird v2 gains improved connection stability.
Kvaser SocketCan Drivers: In line with recent upstream changes in SocketCAN, the version available in the Kvaser Downloads section has been updated.
A new document is available,
‘Kvaser Hydra Command Protocol: The Basics’, for customers wanting to write their own driver to communicate directly with the Kvaser BlackBird v2 or DIN Rail devices over UDP and TCP/IP.
For the full release notes,
click here.
All files are available for download now on the
Kvaser Downloads page.[/vc_column_text][/vc_column][/vc_row]
[post_title] => Kvaser’s June 2020 Software Release
[post_excerpt] =>
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => kvasers-june-2020-software-release
[to_ping] =>
[pinged] =>
[post_modified] => 2020-06-29 22:12:08
[post_modified_gmt] => 2020-06-29 22:12:08
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=28392
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[9] => WP_Post Object
(
[ID] => 28314
[post_author] => 23
[post_date] => 2020-05-29 03:45:55
[post_date_gmt] => 2020-05-29 03:45:55
[post_content] => [vc_row][vc_column][vc_single_image image="28315"][/vc_column][/vc_row][vc_row][vc_column width="3/4"][vc_column_text]A test system for use in operational road tests and accident reconstructions created by automotive forensic analysis experts at Advanced Analysis Associates, Inc.and Automotive Systems Analysis, Inc., is detailed in a paper entitled “A Multi-Purpose Vehicle Test Instrument with MCC DASYLab Graphics and Kvaser CAN Interfaces” that can be found
here.[/vc_column_text][vc_column_text]Explains co-author, Bill Rosenbluth: “Our goal was to create a cost-effective, real-time test data recorder that, in operational road tests and accident reconstructions, recorded individual controller performance, communications between controllers and external factors, while presenting an easily readable, scaled graphical feedback interface to the test operator.”[/vc_column_text][/vc_column][vc_column width="1/4" css=".vc_custom_1591307492765{border-top-width: 1px !important;border-right-width: 1px !important;border-bottom-width: 1px !important;border-left-width: 1px !important;border-left-color: #000000 !important;border-left-style: solid !important;border-right-color: #000000 !important;border-right-style: solid !important;border-top-color: #000000 !important;border-top-style: solid !important;border-bottom-color: #000000 !important;border-bottom-style: solid !important;border-radius: 1px !important;}"][vc_column_text]
Download
the
White Paper
[/vc_column_text][vc_button_raket title="Download" text="" align="align_center" page_id="https://www.kvaser.com/wp-content/uploads/2020/05/amulti-purposevehicletestinst5j.pdf"][/vc_column][/vc_row][vc_row disable_element="yes"][vc_column][vc_well_raket title_link="1" post_id="https://www.kvaser.com/wp-content/uploads/2020/05/amulti-purposevehicletestinst5j.pdf" button_title="Download" title="Download the White Paper"][/vc_well_raket][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_column_text]The instrument system detailed in the paper uses a Kvaser Leaf CAN to USB interface, a DASYLab™ graphics display and USB A/D modules from Measurement Computing Corp., plus an American Engine Management GPS module, 8-channel K-thermocouple module and A/D module. Two custom Python scripts were created to combine the test interfaces. The resulting data acquisition and recording system logs both raw CAN and scaled parameter data, and has a logged CAN playback feature, which also accepts CAN logs from other popular formats and translates them identically to the system configuration in an original instrument.[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="28317"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]Rosenbluth explains why the research team chose Kvaser’s CAN to USB and PCI CAN interfaces: “All Kvaser interfaces handled 11-bit and 29-bit CAN modes, including J1939 messages. Additionally, Kvaser offered a publicly available and straightforward *.dbc database editor and free basic CAN data monitor(CanKing), which allowed quick and straightforward testing of incremental *.dbc databases. The Kvaser *.dbc database editor is an easy to use and intuitive tool, allowing straightforward merging of our many incremental and separately developed *.dbc databases.”
As this paper describes work accomplished as part of a continuing development project, the authors are keen to hear feedback on how to improve their system. To contact them directly, please email
Bill Rosenbluth.
For more information, please visit
www.advancedanalysisassociates.com and
www.asareston.com.[/vc_column_text][/vc_column][/vc_row]
[post_title] => A CAN test system for accident reconstruction & road testing
[post_excerpt] => Automotive forensic analysis experts use Kvaser interfaces in a real-time data recorder for use in road tests and accident reconstruction.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => a-can-test-system-for-accident-reconstruction-road-testing
[to_ping] =>
[pinged] =>
[post_modified] => 2022-05-24 10:44:35
[post_modified_gmt] => 2022-05-24 10:44:35
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=28314
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
)
[post_count] => 10
[current_post] => -1
[in_the_loop] =>
[post] => WP_Post Object
(
[ID] => 29331
[post_author] => 6
[post_date] => 2020-09-02 18:37:41
[post_date_gmt] => 2020-09-02 18:37:41
[post_content] => [vc_row][vc_column][vc_single_image image="13763"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]
As scientific challenges go, you can’t get much bigger than recreating conditions as they occurred immediately after the Big Bang. This is this mission of the CERN Large Hadron Collider (LHC), which smashes protons to further humanity’s understanding of a wide range of theoretical physical phenomena, including answering the question of what is mass, investigating extra dimensions and the particles that make up dark matter.[/vc_column_text][vc_column_text]During
the LHC’s first run (2008–2012), among the successes chalked up was identification of the elusive Higgs boson. During the second run (2015–2018), the energy used to produce the collisions was increased and more data was collected from the two particle detectors, ATLAS and CMS, in order to observe more clearly the interplay between particles. At 46 m long, 25 m high and 25 m wide,
ATLAS is the largest of the two detectors, comprising six detecting subsystems arranged in layers around an inner chamber.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column width="2/3"][vc_column_text]Aside from the data created by the experiment itself (recording the collision paths, momentum and energy of the particles), monitoring and controlling ATLAS is a data challenge in itself that is entirely run on CAN. During the LHC’s first run, hundreds of
Kvaser’s PCIcanx boards played an important role within ATLAS, providing the link between the 7000-tonne detector and the 100 or so PCs that control and supervise it in ATLAS’ electronics rooms. Each of the PCs had up to three Kvaser cards, controlling over 5000 CAN nodes on more than 300 CAN buses and using
CANopen as the high-level communication protocol.[/vc_column_text][/vc_column][vc_column width="1/3"][vc_single_image image="29217"][/vc_column][/vc_row][vc_row][vc_column][vc_column_text]The CANbus nodes were designed and developed by ATLAS in collaboration with the National Institute for Nuclear Physics and High Energy Physics in Amsterdam and the Petersburg Nuclear Physics Institute. Referred to by the researchers as Embedded Local Monitoring Boards (ELMBs), Kvaser worked with ATLAS staff to optimise the PCICanx boards to suit the ELMBs needs.[/vc_column_text][vc_column_text]Asked why Kvaser’s boards were chosen, Dr Burckhart, in charge of the ATLAS Detector Control System (DCS) project at the time said:[/vc_column_text][vc_column_text]
“Kvaser’s initial form factor already fit well with our requirements. And following our suggestions they made a new version of their board, which exactly matched our needs. An additional plus was that they had CAN interface cards in USB and PCMCIA form factors which support the same application software. Kvaser was also very responsive when initial software fixes were needed.”
[/vc_column_text][vc_column_text]Among the physical requirements determining CERN’s choice of a CAN interface board was that each port would need an independent buffer and be independently controlled (so resetting one port wouldn’t affect another). From a software perspective, it was necessary to support Windows and Linux, and that a simple and intuitive API was needed.[/vc_column_text][vc_column_text]
“We were very happy with Kvaser’s PCICan cards and they ran very stably,”
[/vc_column_text][vc_column_text]confirmed Dr. Stefan Schlenker, now responsible for the ATLAS detector controls at CERN. Dr. Schlenker took over from Dr. Helfried Burckhart, who led the specification of the system. As Dr Burckhart explained, CAN was an automatic choice:[/vc_column_text][vc_column_text]
“It is robust, has good industrial support (including at the chip level), is inexpensive and provided adequate functionality.” Dr Schlenker confirms that ATLAS’ CAN system “is foreseen to operate for at least another 15 years with minor modifications.”
[/vc_column_text][vc_column_text]In 2013 and 2014, during CERN’s first long shutdown, the control system was updated as it was becoming more difficult to find PCI-based servers, and it was necessary to increase CAN port density. ATLAS moved to rack-mounted CAN to USB interfaces, with two USB ports serving 16 CAN ports.[/vc_column_text][vc_column_text]As speeds continue to increase within the LHC, so the detector control system (DCS) must evolve too. Whilst no major control system changes are planned during CERN’s second long shutdown (2020/2021), with many parts of the detector programmed for renewal during the next shutdown in 2025 – in particular, a move to an all silicon inner detector – more fundamental updates to the control system will be needed at that time. The original DCS monitored some 200,000 slowly changing parameters, such as voltage, current, temperature and pressure. Beyond 2024, the volume of data increases to millions of readouts per few seconds, so a move to CAN-to-Ethernet cards is scheduled for that time.[/vc_column_text][/vc_column][/vc_row]
[post_title] => CERN’s ATLAS project: A CAN control network of epic scale
[post_excerpt] => CERN's ATLAS project utilizes CANopen, via Kvaser's PCIcanx products, to control a CAN network and experiment of epic proportions.
[post_status] => publish
[comment_status] => closed
[ping_status] => closed
[post_password] =>
[post_name] => cerns-atlas-project-a-can-control-network-of-epic-scale
[to_ping] =>
[pinged] =>
[post_modified] => 2022-04-04 10:19:12
[post_modified_gmt] => 2022-04-04 10:19:12
[post_content_filtered] =>
[post_parent] => 0
[guid] => https://www.kvaser.com/?p=29331
[menu_order] => 0
[post_type] => post
[post_mime_type] =>
[comment_count] => 0
[filter] => raw
)
[comment_count] => 0
[current_comment] => -1
[found_posts] => 469
[max_num_pages] => 47
[max_num_comment_pages] => 0
[is_single] =>
[is_preview] =>
[is_page] =>
[is_archive] =>
[is_date] =>
[is_year] =>
[is_month] =>
[is_day] =>
[is_time] =>
[is_author] =>
[is_category] =>
[is_tag] =>
[is_tax] =>
[is_search] =>
[is_feed] =>
[is_comment_feed] =>
[is_trackback] =>
[is_home] => 1
[is_privacy_policy] =>
[is_404] =>
[is_embed] =>
[is_paged] => 1
[is_admin] =>
[is_attachment] =>
[is_singular] =>
[is_robots] =>
[is_favicon] =>
[is_posts_page] => 1
[is_post_type_archive] =>
[query_vars_hash:WP_Query:private] => 8287461eafc1a19c76be9009ba6fa5b1
[query_vars_changed:WP_Query:private] => 1
[thumbnails_cached] =>
[stopwords:WP_Query:private] =>
[compat_fields:WP_Query:private] => Array
(
[0] => query_vars_hash
[1] => query_vars_changed
)
[compat_methods:WP_Query:private] => Array
(
[0] => init_query_flags
[1] => parse_tax_query
)
)
CERN’s ATLAS project: A CAN control network of epic scale
02/09/2020
As scientific challenges go, you can’t get much bigger than recreating conditions as they occurred immediately after the Big Bang.… Read More
Read More
In-Vehicle Communication Standards for Trucks: Where Do We Go With J1939? [Featuring Bryan Hennessy]
02/09/2020
Read More
Read More
Webinar: CAN Datalogging with Accurate Technologies
18/08/2020
Editor’s note: This event has already passed. If you would like to know about future webinars, you can create a MyKvaser account,… Read More
Read More
Simulating an Electric Vehicle Charging Station: Battery Show Demo Walkthrough
12/08/2020
Bryan Hennessy, Kvaser Technical Partner Manager, and Amir Rezaei, Senior Control Systems Engineer at Pi Innovo, created a Combined Charging… Read More
Read More
Studying the efficacy of face masks involves CAN
04/08/2020
A cough aerosol simulator that uses CAN as the primary communication protocol is being used to study how well face… Read More
Read More
Hexadecimal and Binary Numbering Systems
29/06/2020
I have not been able to find a good hexadecimal explanation site, so here’s an overview in my own words,… Read More
Read More
Intelligent data logger for electric trucks; Case study from TK Engineering
26/06/2020
Read More
Read More
Comparing CAN interface transfer delays
17/06/2020
In this article, “Comparing CAN interface transfer delays”, I will test and compare four different types of Kvaser CAN interfaces.… Read More
Read More
Kvaser’s June 2020 Software Release
09/06/2020
Kvaser’s latest software release supports Linux 5.6 kernel. Notable changes and additions include: Python canlib package (pycanlib): Support has been… Read More
Read More
A CAN test system for accident reconstruction & road testing
29/05/2020
A test system for use in operational road tests and accident reconstructions created by automotive forensic analysis experts at Advanced… Read More
Read More
youku