{"id":13675,"date":"2019-05-07T14:44:50","date_gmt":"2019-05-07T04:44:50","guid":{"rendered":"http:\/\/legoeng.local?p=13675&preview=true&preview_id=13675"},"modified":"2019-05-07T14:45:05","modified_gmt":"2019-05-07T04:45:05","slug":"yellow-diamond-error-in-ev3-software","status":"publish","type":"post","link":"http:\/\/legoeng.local\/yellow-diamond-error-in-ev3-software\/","title":{"rendered":"Yellow Diamond Error in EV3 Software"},"content":{"rendered":"

One of my robotics teams recently ran across an error message and problem that I had never seen before.\u00a0While they were rehearsing for a local robotics competition, their robot began to act “wacky”. I suggested they just re-download the program to the EV3 brick. This was when everything got really weird. On the screen above each block in their program was a little yellow diamond.<\/p>\n

I have attempted to recreate the situation in the EV3 software image below (it never dawned on me to take a screenshot of the error while it was on the laptop).<\/p>\n

\"\"<\/a>
A re-creation of the error<\/figcaption><\/figure>\n

Perplexed, we disconnected the USB cable from the EV3 brick and opened the robot in Port View<\/em>. We checked each of the ports individually and before our eyes we saw something odd. This particular robot was employing one NXT motor and two large EV3 motors, which normally work fine together. Today was different. Although Port B on the robot was connected to an EV3 large motor, Port View was displaying it as B: M-MOTOR-DEG. Thinking the older NXT motor on Port D was causing the problem, I disconnected and reconnected the cable between the EV3 brick and the motor. Nothing changed. Then I disconnected and reconnected the EV3 large motor on Port B and as soon as the connection was restored it began reading correctly. See the Port View<\/em> images below.<\/p>\n

\"\"<\/a>
Port View before and after the error<\/figcaption><\/figure>\n

The rest of the day went on as normal and that team even finished in 3rd place.<\/p>\n","protected":false},"excerpt":{"rendered":"

One of my robotics teams recently ran across an error message and problem that I had never seen before.\u00a0While they were rehearsing for a local robotics competition, their robot began to act “wacky”. I suggested they just re-download the program to the EV3 brick. This was when everything got really weird. On the screen above […]<\/p>\n","protected":false},"author":440,"featured_media":13678,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[159],"tags":[],"_links":{"self":[{"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/posts\/13675"}],"collection":[{"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/users\/440"}],"replies":[{"embeddable":true,"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/comments?post=13675"}],"version-history":[{"count":0,"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/posts\/13675\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/media\/13678"}],"wp:attachment":[{"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/media?parent=13675"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/categories?post=13675"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/legoeng.local\/wp-json\/wp\/v2\/tags?post=13675"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}