angrycamel.com

There's a crack in the interweb

The new IEBus firmware is working!

I just got to a stopping point on the firmware tonight and decided to grab some data off the bus for review. You can check it out here if you want. You will notice a lot less errors. Its because my firmware is lighter and seems to run considerably faster. I think the reason for the errors you saw in the video before was because of the firmware was not processing the packets fast enough to keep up with the bus.

Also, this is what we are looking at for the structure of the lib files. (for defined devices and events per vehicle) This is the filetype that you will be able to open and work with in IEBus Studio. Pretty simple, right!

<vehicle>
  <make>Acura</make>
  <model>TSX</model>
  <year>2004</year>
  <navigation>yes</navigation>
</vehicle>
<device>
  <address>0x183</address>
  <name>Navigation Computer</name>
  <description>Navigation computer mounted in the trunk of the car.</description>
</device>
<device>
  <address>0x131</address>
  <name>Touchscreen Controller</name>
  <description>Touchscreen controller for sending touch events from the navigation screen in the dashboard to the navigation unit in the trunk.</description>
</device>
<device>
  <address>0x100</address>
  <name>Head Unit</name>
  <description>The head unit send commands like the volume up or down as well as changing the channel on the radio.</description>
</device>
<event>
	<name>Volume Level 3</name>
  <raw>1:100:183:F:14:60:2:31:0:2:0:3:10:0:E0:20:0:0:9D</raw>
  <broadcast>1</broadcast>
  <master_device>0x100</master_device>
  <slave_device>0x183</slave_device>
  <control>0xF</control>
  <datasize>0xE</datasize>
  <data>0x60</data>
  <data>0x2</data>
  <data>0x31</data>
  <data>0x0</data>
  <data>0x2</data>
  <data>0x0</data>
  <data>0x3</data>
  <data>0x10</data>
  <data>0x0</data>
  <data>0xE0</data>
  <data>0x20</data>
  <data>0x0</data>
  <data>0x0</data>
  <data>0x9D</data>
</event>

Categorised as: Automotive, IEBus, Programming


Leave a Reply