{"id":585,"date":"2018-01-30T15:17:07","date_gmt":"2018-01-30T14:17:07","guid":{"rendered":"http:\/\/www.embedded-communication.com\/?p=585"},"modified":"2018-08-17T14:33:44","modified_gmt":"2018-08-17T12:33:44","slug":"energybus-implementation-hints","status":"publish","type":"post","link":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/","title":{"rendered":"EnergyBus Implementation Hints"},"content":{"rendered":"<p>Some implementation hints for EnergyBus in light-electric vehicles such as e-bikes:<\/p>\n<h2>All components<\/h2>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li>Differ between Sleep and Deep Sleep. The typical EnergyBus low power mode is called &#8216;Sleep&#8217; and means, that the devices are powered by the auxiliary voltage and can wakeup on receiving CAN messages.<\/li>\n<li>Implement real Sleep\/Wake-Up handling. The EnergyBus Controller (EBC) command the network wide Sleep. The typical Display (HMI) power button send (only) a sleep request to the EBC.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>EnergyBus Controller<\/h2>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li>Create a system design with the maximum components. The EBC must support this maximal network.<\/li>\n<li>Provide non-volatile memory on EnergyBus Controller (EBC) hardware<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>It is recommended to have some non-volatile memory (EEPROM, EEPROM emulation, &#8230;) on the EBC hardware to store identity information of the connection components. This will increase the start-up of the network inside the vehicle significantly.<\/p>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li>Detect connection of an EnergyBus service tool in the EBC<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>An EnergyBus service tool according to the CiA 454 specification reports itself by sending heartbeat of the node-ID 125. The EBC should recognize this and should e.g. prevent the Motor Controller (MCU) from powering. The bike shouldn&#8217;t move when a service tool is connected or do SDO transfers.<\/p>\n<h2>All &#8216;slave&#8217; components: battery, display, manufacturer-specific devices, &#8230;<\/h2>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li>Use dynamic node-Ids as required by the specification CiA 454<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>The EnergyBus specification CiA 454 requires the use of dynamic node-IDs assigned by the EBC at startup. Using fixed node-IDs might work in the beginning with some other devices, but it will cause compatibility problems in the long term.<\/p>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li>Support a dynamic instance offset<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Using a dynamic instance offset (write-able object 0x6000:xx), the EBC can assign a different global instance number to the device and thus multiple devices of the same type, will be supported. It always only starts with 1 battery or 1 HMI, but mostly there will be more in the future.<\/p>\n<h2>Bootloader<\/h2>\n<p>According to the EnergyBus specification the usage of a boot-loader to update the firmware in the field is recommended. In addition to that it is recommended to implement some checks in the bootloader that it does not start a wrong application but with valid CRC, that has been flashed by accident.<\/p>","protected":false},"excerpt":{"rendered":"<p>Some implementation hints for EnergyBus in light-electric vehicles such as e-bikes: All components Differ between Sleep and Deep Sleep. The typical EnergyBus low power mode is called &#8216;Sleep&#8217; and means, that the devices are powered by the auxiliary voltage and can wakeup on receiving CAN messages. Implement real Sleep\/Wake-Up handling. The EnergyBus Controller (EBC) command &hellip; <a href=\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;EnergyBus Implementation Hints&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-585","post","type-post","status-publish","format-standard","hentry","category-energybus"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>EnergyBus Implementation Hints - embedded communication<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EnergyBus Implementation Hints - embedded communication\" \/>\n<meta property=\"og:description\" content=\"Some implementation hints for EnergyBus in light-electric vehicles such as e-bikes: All components Differ between Sleep and Deep Sleep. The typical EnergyBus low power mode is called &#8216;Sleep&#8217; and means, that the devices are powered by the auxiliary voltage and can wakeup on receiving CAN messages. Implement real Sleep\/Wake-Up handling. The EnergyBus Controller (EBC) command &hellip; Continue reading &quot;EnergyBus Implementation Hints&quot;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\" \/>\n<meta property=\"og:site_name\" content=\"embedded communication\" \/>\n<meta property=\"article:published_time\" content=\"2018-01-30T14:17:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2018-08-17T12:33:44+00:00\" \/>\n<meta name=\"author\" content=\"Torsten Gedenk\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@EmbeddedComm\" \/>\n<meta name=\"twitter:site\" content=\"@EmbeddedComm\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Torsten Gedenk\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\"},\"author\":{\"name\":\"Torsten Gedenk\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#\/schema\/person\/8f0fcf033edee00b06d4dd4cf196680e\"},\"headline\":\"EnergyBus Implementation Hints\",\"datePublished\":\"2018-01-30T14:17:07+00:00\",\"dateModified\":\"2018-08-17T12:33:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\"},\"wordCount\":360,\"publisher\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#organization\"},\"articleSection\":[\"EnergyBus\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\",\"url\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\",\"name\":\"EnergyBus Implementation Hints - embedded communication\",\"isPartOf\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#website\"},\"datePublished\":\"2018-01-30T14:17:07+00:00\",\"dateModified\":\"2018-08-17T12:33:44+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Startseite\",\"item\":\"https:\/\/www.embedded-communication.com\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EnergyBus Implementation Hints\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#website\",\"url\":\"https:\/\/www.embedded-communication.com\/en\/\",\"name\":\"embedded communication\",\"description\":\"A blog about embedded communcation protocols.\",\"publisher\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.embedded-communication.com\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#organization\",\"name\":\"embedded communication\",\"url\":\"https:\/\/www.embedded-communication.com\/en\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.embedded-communication.com\/wp-content\/uploads\/2016\/08\/embedded-communication.png\",\"contentUrl\":\"https:\/\/www.embedded-communication.com\/wp-content\/uploads\/2016\/08\/embedded-communication.png\",\"width\":240,\"height\":240,\"caption\":\"embedded communication\"},\"image\":{\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/EmbeddedComm\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.embedded-communication.com\/en\/#\/schema\/person\/8f0fcf033edee00b06d4dd4cf196680e\",\"name\":\"Torsten Gedenk\",\"url\":\"https:\/\/www.embedded-communication.com\/en\/author\/ged\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"EnergyBus Implementation Hints - embedded communication","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/","og_locale":"en_US","og_type":"article","og_title":"EnergyBus Implementation Hints - embedded communication","og_description":"Some implementation hints for EnergyBus in light-electric vehicles such as e-bikes: All components Differ between Sleep and Deep Sleep. The typical EnergyBus low power mode is called &#8216;Sleep&#8217; and means, that the devices are powered by the auxiliary voltage and can wakeup on receiving CAN messages. Implement real Sleep\/Wake-Up handling. The EnergyBus Controller (EBC) command &hellip; Continue reading \"EnergyBus Implementation Hints\"","og_url":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/","og_site_name":"embedded communication","article_published_time":"2018-01-30T14:17:07+00:00","article_modified_time":"2018-08-17T12:33:44+00:00","author":"Torsten Gedenk","twitter_card":"summary_large_image","twitter_creator":"@EmbeddedComm","twitter_site":"@EmbeddedComm","twitter_misc":{"Written by":"Torsten Gedenk","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/#article","isPartOf":{"@id":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/"},"author":{"name":"Torsten Gedenk","@id":"https:\/\/www.embedded-communication.com\/en\/#\/schema\/person\/8f0fcf033edee00b06d4dd4cf196680e"},"headline":"EnergyBus Implementation Hints","datePublished":"2018-01-30T14:17:07+00:00","dateModified":"2018-08-17T12:33:44+00:00","mainEntityOfPage":{"@id":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/"},"wordCount":360,"publisher":{"@id":"https:\/\/www.embedded-communication.com\/en\/#organization"},"articleSection":["EnergyBus"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/","url":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/","name":"EnergyBus Implementation Hints - embedded communication","isPartOf":{"@id":"https:\/\/www.embedded-communication.com\/en\/#website"},"datePublished":"2018-01-30T14:17:07+00:00","dateModified":"2018-08-17T12:33:44+00:00","breadcrumb":{"@id":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.embedded-communication.com\/en\/energybus\/energybus-implementation-hints\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Startseite","item":"https:\/\/www.embedded-communication.com\/en\/"},{"@type":"ListItem","position":2,"name":"EnergyBus Implementation Hints"}]},{"@type":"WebSite","@id":"https:\/\/www.embedded-communication.com\/en\/#website","url":"https:\/\/www.embedded-communication.com\/en\/","name":"embedded communication","description":"A blog about embedded communcation protocols.","publisher":{"@id":"https:\/\/www.embedded-communication.com\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.embedded-communication.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.embedded-communication.com\/en\/#organization","name":"embedded communication","url":"https:\/\/www.embedded-communication.com\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.embedded-communication.com\/en\/#\/schema\/logo\/image\/","url":"https:\/\/www.embedded-communication.com\/wp-content\/uploads\/2016\/08\/embedded-communication.png","contentUrl":"https:\/\/www.embedded-communication.com\/wp-content\/uploads\/2016\/08\/embedded-communication.png","width":240,"height":240,"caption":"embedded communication"},"image":{"@id":"https:\/\/www.embedded-communication.com\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/EmbeddedComm"]},{"@type":"Person","@id":"https:\/\/www.embedded-communication.com\/en\/#\/schema\/person\/8f0fcf033edee00b06d4dd4cf196680e","name":"Torsten Gedenk","url":"https:\/\/www.embedded-communication.com\/en\/author\/ged\/"}]}},"_links":{"self":[{"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/posts\/585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/comments?post=585"}],"version-history":[{"count":10,"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/posts\/585\/revisions"}],"predecessor-version":[{"id":685,"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/posts\/585\/revisions\/685"}],"wp:attachment":[{"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/media?parent=585"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/categories?post=585"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.embedded-communication.com\/en\/wp-json\/wp\/v2\/tags?post=585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}