https://wiki.autosportlabs.com/api.php?action=feedcontributions&feedformat=atom&user=Jstoezel 2026-09-20T12:51:29Z User contributions MediaWiki 1.44.0 https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=6020 2015-01-10T21:33:09Z

<p>Jstoezel: /* CAN Bus Initialization */</p> <hr /> <div>=AIM Solo DL=<br /> AIM Solo DL research is underway.<br /> <br /> =MyChron 4=<br /> MyChron 4 research is underway.<br /> <br /> =MyChron 3=<br /> This section documents how to control an AIM Mychron3 Dash display, using a RaceCapture/Pro telemetry system unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings by Jean-Sebastien Stoezel [http://sites.google.com/site/mychron3/home/can-bus-protocol documented here]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> [[File:AIM_Mychron3.jpg|500px]]<br /> <br /> == Wiring / Connection==<br /> TODO: show wiring and connection information between RaceCapture/Pro and Mychron3<br /> <br /> == CAN Bus Initialization ==<br /> The AIM Mychron3 requires a CAN bus rate of 1Mb/s, in standard form (11 bit identifiers). The following code example initializes the CAN bus channel #2 at 1Mb/s.<br /> <br /> initCAN(2, 1000000)<br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are connected to different sensors<br /> local temp1 = getAnalog(0)<br /> local temp2 = getAnalog(1)<br /> local temp3 = getAnalog(2)<br /> local temp4 = getAnalog(3)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> function onTick()<br /> local shiftLeds = 0<br /> local rpm = getTimerRpm(0)<br /> if rpm &gt; 5000 then shiftLeds = shiftLeds + 1 end <br /> if rpm &gt; 6000 then shiftLeds = shiftLeds + 2 end <br /> if rpm &gt; 7000 then shiftLeds = shiftLeds + 4 end<br /> if rpm &gt; 7500 then shiftLeds = shiftLeds + 8 end<br /> if rpm &gt; 7700 then shiftLeds = shiftLeds + 16 end<br /> local msg = {0, 0, 0, 0, 0, 0, shiftLeds, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5999 2015-01-09T14:37:55Z

<p>Jstoezel: /* MyChron 3 */</p> <hr /> <div>=MyChron 3=<br /> This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings by Jean-Sebastien Stoezel [http://sites.google.com/site/mychron3/home/can-bus-protocol documented here]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> == CAN Bus Initialization ==<br /> The AIM Mychron3 requires a CAN bus rate of 1Mb/s, in standard form (11 bit identifiers). The following code example initializes the CAN bus channel at 1Mb/s.<br /> <br /> initCAN(2, 1000000)<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are connected to different sensors<br /> local temp1 = getAnalog(0)<br /> local temp2 = getAnalog(1)<br /> local temp3 = getAnalog(2)<br /> local temp4 = getAnalog(3)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> function onTick()<br /> local shiftLeds = 0<br /> local rpm = getTimerRpm(0)<br /> if rpm &gt; 5000 then shiftLeds = shiftLeds + 1 end <br /> if rpm &gt; 6000 then shiftLeds = shiftLeds + 2 end <br /> if rpm &gt; 7000 then shiftLeds = shiftLeds + 4 end<br /> if rpm &gt; 7500 then shiftLeds = shiftLeds + 8 end<br /> if rpm &gt; 7700 then shiftLeds = shiftLeds + 16 end<br /> local msg = {0, 0, 0, 0, 0, 0, shiftLeds, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5996 2015-01-09T03:49:53Z

<p>Jstoezel: </p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> function onTick()<br /> local shiftLeds = 0<br /> local rpm = getTimerRpm(0)<br /> if rpm &gt; 5000 then shiftLeds = shiftLeds + 1 end <br /> if rpm &gt; 6000 then shiftLeds = shiftLeds + 2 end <br /> if rpm &gt; 7000 then shiftLeds = shiftLeds + 4 end<br /> if rpm &gt; 7500 then shiftLeds = shiftLeds + 8 end<br /> if rpm &gt; 7700 then shiftLeds = shiftLeds + 16 end<br /> local msg = {0, 0, 0, 0, 0, 0, shiftLeds, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5995 2015-01-09T03:49:17Z

<p>Jstoezel: /* Packet 405h: Shift LEDs, Alarm LEDs */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> function onTick()<br /> local shiftLeds = 0<br /> local rpm = getTimerRpm(0)<br /> if rpm &gt; 5000 then shiftLeds = shiftLeds + 1 end <br /> if rpm &gt; 6000 then shiftLeds = shiftLeds + 2 end <br /> if rpm &gt; 7000 then shiftLeds = shiftLeds + 4 end<br /> if rpm &gt; 7500 then shiftLeds = shiftLeds + 8 end<br /> if rpm &gt; 7700 then shiftLeds = shiftLeds + 16 end<br /> local msg = {0, 0, 0, 0, 0, 0, shiftLeds, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5994 2015-01-09T03:45:54Z

<p>Jstoezel: /* Packet 406h: RPM range for the digital RPM readout */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> Byte[6]:4-0: Controls the shift LEDs. The LEDs are bitmaped, meaning the far most LEDs on each side of the display turn on if bit 1 is set, bit 2 controls the second farthest LEDs from the centre. A value of 0x1F turns on all the LEDs and make them blink.<br /> <br /> function onTick()<br /> local leds = 0<br /> <br /> local msg = {0, 0, 0, 0, 0, 0, leds, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5993 2015-01-09T03:45:37Z

<p>Jstoezel: /* Packet 405h: Shift LEDs, Alarm LEDs */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> Byte[6]:4-0: Controls the shift LEDs. The LEDs are bitmaped, meaning the far most LEDs on each side of the display turn on if bit 1 is set, bit 2 controls the second farthest LEDs from the centre. A value of 0x1F turns on all the LEDs and make them blink.<br /> <br /> function onTick()<br /> local leds = 0<br /> <br /> local msg = {0, 0, 0, 0, 0, 0, leds, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local rpm = <br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5992 2015-01-09T03:44:31Z

<p>Jstoezel: /* Packet 405h: Shift LEDs, Alarm LEDs */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> Byte[6]:4-0: Controls the shift LEDs. The LEDs are bitmaped, meaning the far most LEDs on each side of the display turn on if bit 1 is set, bit 2 controls the second farthest LEDs from the centre. A value of 0x1F turns on all the LEDs and make them blink.<br /> <br /> function onTick()<br /> local msg = {0, 0, 0, 0, 0, 0, temp4 % 4, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local rpm = <br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5991 2015-01-09T03:44:07Z

<p>Jstoezel: /* Packet 405h: Shift LEDs, Alarm LEDs */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> Byte[6]:4-0: Controls the shift LEDs. The LEDs are bitmaped, meaning the far most LEDs on each side of the display turn on if bit 1 is set, bit 2 controls the second farthest LEDs from the centre. A value of 0x1F turns on all the LEDs and make them blink.<br /> <br /> function onTick()<br /> local msg = {0, 0, 0, 0, 0, 0, temp4 % 4, 0, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local rpm = <br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5990 2015-01-09T03:43:05Z

<p>Jstoezel: /* Packet 406h: RPM range for the digital RPM readout */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> Byte[6]:4-0: Controls the shift LEDs. The LEDs are bitmaped, meaning the far most LEDs on each side of the display turn on if bit 1 is set, bit 2 controls the second farthest LEDs from the centre. A value of 0x1F turns on all the LEDs and make them blink.<br /> <br /> function onTick()<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local rpm = <br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1030, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5989 2015-01-09T03:42:46Z

<p>Jstoezel: /* Packet 405h: Shift LEDs, Alarm LEDs */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> Byte[6]:4-0: Controls the shift LEDs. The LEDs are bitmaped, meaning the far most LEDs on each side of the display turn on if bit 1 is set, bit 2 controls the second farthest LEDs from the centre. A value of 0x1F turns on all the LEDs and make them blink.<br /> <br /> function onTick()<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local rpm = <br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5988 2015-01-09T03:40:47Z

<p>Jstoezel: /* Packet 406h: RPM range for the digital RPM readout */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> function onTick()<br /> -- Set the RPM range<br /> -- Value RPM Range<br /> -- 0 25,000 - 0<br /> -- 1 22,000 - 0<br /> -- 2 20,000 - 0<br /> -- 3 16,000 - 0<br /> -- 4 12,000 - 0<br /> -- 5 10,000 - 0<br /> -- 6 8,000 - 0<br /> -- 7 6,000 - 0<br /> -- 8 4,000 - 0<br /> local rpmRange = 6 -- Up to 8000 RPM<br /> local rpm = <br /> local msg = {0, rpmRange * 16, 0, 0, 0, 0, 0, 0}<br /> txCAN(0, 1029, 0, msg)<br /> end<br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5987 2015-01-09T03:40:27Z

<p>Jstoezel: /* Packet 405h: Shift LEDs, Alarm LEDs */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5986 2015-01-09T03:34:54Z

<p>Jstoezel: /* Packet 402h: Temperature/Pressure fields (bottom left of display) */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5985 2015-01-09T03:34:29Z

<p>Jstoezel: </p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5984 2015-01-09T03:33:47Z

<p>Jstoezel: /* Packet 402h: Temperature/Pressure fields (bottom left of display) */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> function onTick()<br /> -- Assume different temperature values are stored in virtual channels<br /> local temp1 = getChannel(temp1Id)<br /> local temp2 = getChannel(temp2Id)<br /> local temp3 = getChannel(temp3Id)<br /> local temp4 = getChannel(temp4Id)<br /> local msg = {temp1 % 256, temp1 / 256, temp2 % 256, temp2 / 256, temp3 % 256, temp3 / 256, temp4 % 4, temp4 / 256}<br /> txCAN(0, 1026, 0, msg)<br /> end<br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5983 2015-01-09T03:27:31Z

<p>Jstoezel: /* Packet 401h: RPM, Speed, Gear blink control, Gear */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> local rpm = getTimerRpm(0)<br /> local speedmph = getGpsSpeed()<br /> -- Assume the gear is calculated and stored in a virtual channel.<br /> -- Refer to LUA scripting example to calculate the gear based on speed and RPM<br /> local gear = getChannel(gearId)<br /> local msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5982 2015-01-08T22:09:51Z

<p>Jstoezel: /* Packet 401h: RPM, Speed, Gear blink control, Gear */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> rpm = getChannel(rpmId)<br /> speedmph = getChannel(speedMphId)<br /> gear = getChannel(gearId)<br /> msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5981 2015-01-08T22:09:25Z

<p>Jstoezel: /* Packet 401h: RPM, Speed, Gear blink control, Gear */</p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> function onTick()<br /> rpm = getChannel(rpmId)<br /> speedmph = getChannel(speedMphId)<br /> gear = getChannel(gearId)<br /> msg = {rpm % 256, rpm / 256, (speedmph % 16) % 256, (speedmph / 16) / 256, 0, 0, gear, 0}<br /> txCAN(0, 1025, 0, msg)<br /> end<br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5980 2015-01-08T21:54:43Z

<p>Jstoezel: </p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below.<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5979 2015-01-08T21:53:12Z

<p>Jstoezel: </p> <hr /> <div>This section documents how to control an AIM Mychron3 Dash display, using an RCP unit via LUA scripting.<br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Examples of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5978 2015-01-08T21:52:08Z

<p>Jstoezel: </p> <hr /> <div><br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5977 2015-01-08T21:51:28Z

<p>Jstoezel: </p> <hr /> <div>'''AIM Mychron 3 Dash'''<br /> <br /> ----<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> <br /> == Packet 401h: RPM, Speed, Gear blink control, Gear ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 402h: Temperature/Pressure fields (bottom left of display) ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 404h: Control for fields displayed on bottom left of display ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 405h: Shift LEDs, Alarm LEDs ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 406h: RPM range for the digital RPM readout ==<br /> <br /> <br /> TODO<br /> <br /> <br /> == Packet 408h: Timing ==<br /> <br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5976 2015-01-08T21:50:47Z

<p>Jstoezel: </p> <hr /> <div>'''AIM Mychron 3 Dash'''<br /> <br /> ----<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> Packet 401h: RPM, Speed, Gear blink control, Gear<br /> <br /> TODO<br /> <br /> Packet 402h: Temperature/Pressure fields (bottom left of display)<br /> <br /> TODO<br /> <br /> Packet 404h: Control for fields displayed on bottom left of display<br /> <br /> TODO<br /> <br /> Packet 405h: Shift LEDs, Alarm LEDs<br /> <br /> TODO<br /> <br /> Packet 406h: RPM range for the digital RPM readout<br /> <br /> TODO<br /> <br /> Packet 408h: Timing<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5975 2015-01-08T21:48:52Z

<p>Jstoezel: </p> <hr /> <div>'''AIM Mychron 3 Dash'''<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> Packet 401h: RPM, Speed, Gear blink control, Gear<br /> <br /> TODO<br /> <br /> Packet 402h: Temperature/Pressure fields (bottom left of display)<br /> <br /> TODO<br /> <br /> Packet 404h: Control for fields displayed on bottom left of display<br /> <br /> TODO<br /> <br /> Packet 405h: Shift LEDs, Alarm LEDs<br /> <br /> TODO<br /> <br /> Packet 406h: RPM range for the digital RPM readout<br /> <br /> TODO<br /> <br /> Packet 408h: Timing<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5974 2015-01-08T21:48:42Z

<p>Jstoezel: </p> <hr /> <div>'''AIM Mychron 3 Dash'''<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> Packet 401h: RPM, Speed, Gear blink control, Gear<br /> <br /> TODO<br /> <br /> Packet 402h: Temperature/Pressure fields (bottom left of display)<br /> <br /> TODO<br /> <br /> Packet 404h: Control for fields displayed on bottom left of display<br /> <br /> TODO<br /> <br /> Packet 405h: Shift LEDs, Alarm LEDs<br /> <br /> TODO<br /> <br /> Packet 406h: RPM range for the digital RPM readout<br /> <br /> TODO<br /> <br /> [[Packet 408h: Timing]]<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5973 2015-01-08T21:48:16Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> [[AIM_CAN]]</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5972 2015-01-08T21:48:08Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> [AIM_CAN]</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5971 2015-01-08T21:48:00Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> [/AIM_CAN]</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5970 2015-01-08T21:47:44Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> [http://autosportlabs.net/AIM_CAN]</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5969 2015-01-08T21:47:34Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> [[http://autosportlabs.net/AIM_CAN]]</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5968 2015-01-08T21:47:12Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> [http://autosportlabs.net/AIM_CAN]</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=AIM_CAN&diff=5967 2015-01-08T21:46:50Z

<p>Jstoezel: Created page with &quot;&#039;&#039;&#039;AIM Mychron 3 Dash&#039;&#039;&#039; The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Ex...&quot;</p> <hr /> <div>'''AIM Mychron 3 Dash'''<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> [[Packet 401h: RPM, Speed, Gear blink control, Gear]] <br /> <br /> TODO<br /> <br /> [[Packet 402h: Temperature/Pressure fields (bottom left of display)]] <br /> <br /> TODO<br /> <br /> [[Packet 404h: Control for fields displayed on bottom left of display]] <br /> <br /> TODO<br /> <br /> [[Packet 405h: Shift LEDs, Alarm LEDs]] <br /> <br /> TODO<br /> <br /> [[Packet 406h: RPM range for the digital RPM readout]]<br /> <br /> TODO<br /> <br /> [[Packet 408h: Timing]]<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5966 2015-01-08T21:46:40Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5965 2015-01-08T21:44:20Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> <br /> '''AIM Mychron 3 Dash'''<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> [[Packet 401h: RPM, Speed, Gear blink control, Gear]] <br /> <br /> TODO<br /> <br /> [[Packet 402h: Temperature/Pressure fields (bottom left of display)]] <br /> <br /> TODO<br /> <br /> [[Packet 404h: Control for fields displayed on bottom left of display]] <br /> <br /> TODO<br /> <br /> [[Packet 405h: Shift LEDs, Alarm LEDs]] <br /> <br /> TODO<br /> <br /> [[Packet 406h: RPM range for the digital RPM readout]]<br /> <br /> TODO<br /> <br /> [[Packet 408h: Timing]]<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5964 2015-01-08T21:43:54Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> <br /> '''AIM Mychron 3 Dash'''<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> Packet 401h: RPM, Speed, Gear blink control, Gear <br /> <br /> TODO<br /> <br /> Packet 402h: Temperature/Pressure fields (bottom left of display) <br /> <br /> TODO<br /> <br /> Packet 404h: Control for fields displayed on bottom left of display <br /> <br /> TODO<br /> <br /> Packet 405h: Shift LEDs, Alarm LEDs <br /> <br /> TODO<br /> <br /> Packet 406h: RPM range for the digital RPM readout<br /> <br /> TODO<br /> <br /> Packet 408h: Timing<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5963 2015-01-08T21:43:41Z

<p>Jstoezel: /* Controlling a CAN enabled Device */</p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==<br /> <br /> AIM Mychron 3 Dash<br /> <br /> The following information is a sum up of reverse engineering findings documented here: [http://sites.google.com/site/mychron3/home/can-bus-protocol]. Example of LUA implementation of the the different packets documented on the Mychron 3 Hack page are provided below:<br /> <br /> Packet 401h: RPM, Speed, Gear blink control, Gear <br /> <br /> TODO<br /> <br /> Packet 402h: Temperature/Pressure fields (bottom left of display) <br /> <br /> TODO<br /> <br /> Packet 404h: Control for fields displayed on bottom left of display <br /> <br /> TODO<br /> <br /> Packet 405h: Shift LEDs, Alarm LEDs <br /> <br /> TODO<br /> <br /> Packet 406h: RPM range for the digital RPM readout<br /> <br /> TODO<br /> <br /> Packet 408h: Timing<br /> <br /> TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=CAN_Bus_Integration&diff=5962 2015-01-08T21:39:28Z

<p>Jstoezel: </p> <hr /> <div>=Introduction=<br /> <br /> ==Researching CAN Bus protocol==<br /> <br /> ==Reverse Engineering==<br /> <br /> ==Reading a CAN message==<br /> <br /> ==Mapping to a Virtual Channel==<br /> <br /> ==Controlling a CAN enabled Device==</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapture-Pro_MK1&diff=5756 2014-10-15T01:29:46Z

<p>Jstoezel: /* Race Capture Pro MK2 Quick Links */</p> <hr /> <div>==Race Capture Pro MK2 Quick Links==<br /> * [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> <br /> *'''[[RaceCapturePro_V2_software|Version 2 BETA software and app]]<br /> <br /> *'''[[RaceCapturePro_mk2_QuickStart|Super Quick Start]]'''<br /> *'''[[RaceCapturePro_mk2_TelemetryQuickstart|Realtime Telemetry Quick Start]]'''<br /> *'''[[RaceCapturePro_Downloads|Software and Firmware downloads]]'''<br /> *'''[[RaceCapturePro_Sensors|Sensor Guide]]'''<br /> *'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''<br /> *[[RaceCapturePro_FAQ|FAQ / &quot;How Do I...?&quot;]]<br /> *[[RaceCapturePro_installation_guide|Installation Guide]]<br /> *[[RaceCapturePro_SoftwareOperation|Software Operation Guide]]<br /> *[https://github.com/autosportlabs Source code]<br /> *[[RaceCapture/Pro_Feature_List|Upcoming Features]]<br /> *[[RaceTracks|List of supported Race Tracks and Track Maps]]<br /> <br /> <br /> [[Image:RaceCapturePro_inforgraphic.jpg|800px|center]]<br /> <br /> &lt;br/&gt;<br /> <br /> ==Open Source Data Acquisition and Control==<br /> '''Autosport Labs is excited to announce our latest project: RaceCapture/Pro mk2 - a powerful, multi-channel data acquisition and control system for motorsport applications'''<br /> ==Impact==<br /> RaceCapture/Pro transcends most traditional &quot;Data Logging&quot; systems by virtue of its powerful processor, an emphasis on outputs as well as inputs, and on-board Lua scripting that lets you define custom behaviors. The ability to perform data acquisition while controlling other devices and systems, coupled with flexible end-user customization offers an unprecedented level of capability.<br /> <br /> ==Significance==<br /> While the primary application of RaceCapture/Pro mk2 is focused towards race car data acquisition, its powerful processor combined with a wealth of inputs and outputs also makes RaceCapture/Pro a general purpose automotive computer, one capable of handling many different tasks - limited only by your imagination. If the question is &quot;Can RaceCapture do ...?&quot; the answer will likely be 'Yes' and often with little to no external hardware support necessary.<br /> <br /> ==Flexibility==<br /> <br /> ===On-board scripting===<br /> We embedded the [http://www.lua.org Lua] scripting language right on board RaceCapture/Pro; with Lua you can control RaceCapture's behavior at run-time, no firmware programming required.<br /> <br /> Some Examples:<br /> ** Activate a warning light when an input threshold is exceeded, such as temperature or pressure, or a combination of both<br /> ** Log data at a higher rate when in range of a particular GPS coordinate, or when some other condition is met<br /> ** Auto-start/stop logging based on speed, RPM, or any other condition<br /> ** Experiment with active aerodynamics by adjusting a wing based on GPS velocity<br /> ** Define logic to control an intercooler sprayer<br /> ** Intercept and remap an OEM sensor<br /> ** Activate Smoke screens against your competitors :)<br /> <br /> ===Software Connectivity===<br /> RaceCapture/Pro features software to:<br /> * Customize logging channels<br /> * View Runtime Data<br /> * Edit custom scripting<br /> * Perform data analysis and replay<br /> <br /> ===Infinite Possibilities===<br /> * Far more than a data-logging system: flexible Inputs and Outputs coupled with a powerful processor offers endless customization<br /> * Share configurations, tips and ideas with our online community<br /> * '''Fully Open Source System - Open Standards, Open File format''' Frequent software updates and end-user customizable!<br /> * [https://github.com/autosportlabs Source code]<br /> <br /> ==Technical Specifications==<br /> <br /> &lt;font size=&quot;3&quot;&gt;Extreme flexibility comes with a powerful processor and a wealth of inputs and outputs. &lt;/font&gt;<br /> <br /> ===Input and Output Channels===<br /> RaceCapture mk2 offers 21 input and output channels and serial communication port, enough to handle complex logging and control tasks.<br /> <br /> * '''7 dedicated 0-5v analog input channels'''<br /> ** Measure sensors or process input from other devices.<br /> <br /> * '''3 dedicated 0-5v frequency input channels'''<br /> ** Measure RPM, wheel speed, or any kind of periodic pulse.<br /> <br /> * '''4 configurable 0-5v analog or frequency output (PWM) channels'''<br /> ** Control other systems or even override OEM sensors<br /> <br /> * '''3 configurable digital channels, settable for input or output'''<br /> ** Receive input from switches or digital signals; or configure as output and use to activate accessories or drive indicator lamps with on-board 1A self-protected mosfets<br /> <br /> * '''4 Axis Accelerometer: 3 channel accelerometer module plus Z-axis gyro (+/- 2G per axis, 3G optional)'''<br /> ** Measure and log 3D G-force in real-time with one of the industry's most accurate accelerometers.<br /> ** Z-axis gyroscope measures yaw/drift in real-time.<br /> <br /> * '''50Hz GPS module'''<br /> ** Internal state of the art GPS module<br /> *** Plot location, speed and time. Onboard detection of start/finish line for automatic lap count and lap time. Real time predictive timing.<br /> <br /> * '''Auxiliary Serial Port'''<br /> ** Interface to real time telemetry, bluetooth adapter, dashboard display or other interface<br /> <br /> * '''CAN Bus Expansion'''<br /> ** Two high speed CAN bus ports provide the ability to virtually interface with any type of CAN bus enabled equipment, from ECUs to tire temperature sensors.<br /> <br /> ===Logging===<br /> * '''SD Memory card slot for data acquisition'''<br /> ** Store up to 32GB of logging data<br /> <br /> ===CPU===<br /> * '''168MHz 32 bit ARM processor'''<br /> ** Enough juice to perform high resolution logging and running complex, user-defined logic<br /> <br /> ===Input/Output Protection===<br /> * '''40v protection''' on all input pins<br /> * Analog outputs protected by '''auto-resettable fuses'''<br /> * Digital outputs are rated at '''1A with self-protected mosfets'''<br /> * '''Over-current protection''' on 5V reference<br /> * '''2A''' internal switching power supply<br /> <br /> ===Mechanical===<br /> * '''Compact, rugged design '''<br /> ** Unit measures approximately 4 x 3 inches (100 x 82 mm) <br /> ** Weighs 8.4oz<br /> ** Real-Time module weighs 7oz<br /> * Easy to use screw terminal block for wiring<br /> * On-board 'action' switch to start/stop logging (or other use)<br /> * On-board Status LEDs<br /> <br /> ===Power===<br /> *** TODO ***<br /> * 9-17v power<br /> * &lt; 100mA for RaceCapture/Pro. <br /> * May burst to 2A temporarily when using RealTime Telemetry module<br /> <br /> ==Example Sensor Connectivity==<br /> &lt;center&gt;<br /> [[Image:RaceCapturePro_infographic_sensors.jpg]]<br /> <br /> <br /> [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> &lt;/center&gt;</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapturePro_mk2_TelemetryQuickstart&diff=5755 2014-10-15T01:28:53Z

<p>Jstoezel: Created page with &quot;=Unbox= =Install SIM Card into Telemetry Module= ==Purchasing a SIM Card== ===Which SIM card to get?=== This is largely determined by the coverage map of the race track you&#039;ll ...&quot;</p> <hr /> <div>=Unbox=<br /> <br /> =Install SIM Card into Telemetry Module=<br /> ==Purchasing a SIM Card==<br /> <br /> ===Which SIM card to get?===<br /> This is largely determined by the coverage map of the race track you'll be at. Use the coverage map checker for the respective carriers.<br /> <br /> ===T-Mobile===<br /> Purchase a &quot;Pay By the Day&quot; SIM card from your local T-Mobile dealer. We recommend picking a plan with the 2G/3G unlimited data, which is currently $3 USD/day. The plan is only charged when data is actually used during a 24 hour period. Visit [http://prepaid-phones.t-mobile.com/prepaid-plans T-Mobile] for more details on prepaid plans.<br /> <br /> [http://autosportlabs.net/RaceCapturePro_TelemetryQuickstart T-Mobile Coverage map tool]<br /> <br /> In the RaceAnalyzer software, configure the APN settings using the following values:<br /> *APN Host: epc.tmobile.com<br /> *APN User: &lt;leave this blank&gt;<br /> *APN Password: &lt;leave this blank&gt;<br /> <br /> ===AT&amp;T===<br /> In the RaceAnalyzer software, configure the APN settings using the following values:<br /> <br /> *APN Host: wap.cingular<br /> *APN User: wap@cingulargprs.com<br /> *APN Password: cingular1<br /> <br /> [http://www.att.com/maps/wireless-coverage.html AT&amp;T Coverage Map tool]<br /> <br /> <br /> [[Cellular_Telemetry_APNs|Big list of Carriers / APNs worldwide]]<br /> <br /> ==Installing SIM card==<br /> * Open RaceCapture/Pro mk2 enclosure<br /> <br /> TODO<br /> <br /> ===Unlatch SIM card holder===<br /> Unlatch the card holder by gently sliding the cover in the 'open' direction and swing the cover open.<br /> <br /> ===Insert SIM card===<br /> Insert the SIM card, taking note of the beveled edge. The SIM card can only be inserted in one direction.<br /> <br /> TODO PIC<br /> <br /> ===Latch simcard holder in place===<br /> Swing the cover closed and slide towards the 'lock' position. take care that the cover is locked on both sides of the holder and it is flush with the board.<br /> <br /> TODO<br /> <br /> ===Re-assemble case===<br /> Slide board back into enclosure. Ensure LEDs are aligned with end plate and reattach end plate with screws. <br /> * You may need to gently press the LEDs down flush against the board in order for them to line up with the holes in the opposite end plate.<br /> <br /> =Connect components=<br /> <br /> ==Connecting Antenna==<br /> * Connect antenna to RF port<br /> <br /> TODO<br /> <br /> <br /> ==Telemetry LEDs==<br /> <br /> TODO<br /> <br /> ===Power LED===<br /> <br /> TODO<br /> <br /> ===Network status LED===<br /> <br /> TODO<br /> <br /> ===Transmit / Receive LEDs===<br /> <br /> TODO<br /> <br /> =Create a RCLive account and register your device=<br /> <br /> * Go to [http://www.race-capture.com www.race-capture.com], click on Signup in the top navigation<br /> * Create your account<br /> * After creating your account you will be prompted to add your device. Do it :)<br /> * Once added you will be given a device id, save this, you'll need it soon.<br /> <br /> =Install RaceAnalyzer=<br /> Follow the software installations instructions here: http://www.autosportlabs.net/RaceCapturePro_SoftwareOperation<br /> <br /> =Configure RaceCapture/Pro=<br /> For general RaceCapture/Pro installation and configuration be sure to review the [[RaceCapturePro_installation_guide|Installation]] and [[RaceCapturePro_SoftwareOperation|Software]] guides.<br /> <br /> ===Read Configuration===<br /> '''Before configuring any parameters [[RaceCapturePro_SoftwareOperation#Reading_Configuration|read the configuration]] from RaceCapture/Pro'''<br /> <br /> ===Set channel sample rates===<br /> <br /> Note, with the real-time telemetry sample rates are automatically limited to 10Hz. Logging to local SD card will be at the normal sample rates defined in the configuration.<br /> <br /> ====Available bandwidth====<br /> The total available data rate is a function of number of channels combined with sample rate and is also affected by cellular network conditions. We will have an expanded guide and tool set to help identify optimal sample rates.<br /> <br /> ===Set device id===<br /> <br /> Add your device id that you wrote down when adding your device to race-capture.com to the Telemetry Device Id field under the Logging/Telemetry section:<br /> [[File:Devicesetup.png]]<br /> <br /> ==Write configuration==<br /> * Click the 'Write' button in RaceAnalyzer<br /> * Power cycle RCP (turn off then on again)<br /> <br /> ==Testing==<br /> RaceCapture/Pro with GPS &amp; telemetry needs more power than a regular USB port can supply. You'll either need to connect it to your car's power directly, via a cigarette power adapter with wires or a powered usb hub similar to these:<br /> <br /> * [http://www.amazon.com/Sabrent-Powered-adapter-compatible-HB-USB30/dp/B00BJPRI1Y/ref=sr_1_3?ie=UTF8&amp;qid=1367991516&amp;sr=8-3&amp;keywords=usb+hub+high+power Sabrent Powered USB hub]<br /> * [http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF/ref=sr_1_5?ie=UTF8&amp;qid=1367991578&amp;sr=8-5&amp;keywords=usb+hub+high+power D-Link powered hub]<br /> <br /> We have not tested the above units; we offer them as suggestions of possible USB hubs with enhanced power capabilities.<br /> <br /> Press the black switch on the front of your RaceCapture/Pro device to start logging. You will observe the Transmit LED blinking rapidly once the Cellular module is registered to the cellular network and after the link has been initialized, which ranges from a few seconds and up to 1 minute.<br /> <br /> Got to [http://race-capture.com/home race-capture.com/home], you should see a new event labeled 'Ad-hoc event ...', click on it, then click on your device on the next page.<br /> <br /> ==Success==<br /> View your live telemetry!<br /> Race faster!<br /> <br /> =Troubleshooting=<br /> <br /> If you cannot see data flowing to [http://www.race-capture.com www.race-capture.com] check the following:<br /> <br /> * You have $$ on your sim card from T-Mobile. <br /> ** Refill [http://prepaid-phones.t-mobile.com/prepaid-refill T-Mobile Refill site]<br /> <br /> * Your RaceCapture/Pro logging rates are set to the suggested sample rates<br /> <br /> * You are powering RaceCapture/Pro using a 12v power supply through the terminal block. It will not work over computer USB power due to power constraints<br /> <br /> * When connected to the cell network you should see a slow flash on the cellular module's status light - 1 flash every 3 seconds<br /> <br /> * When actively logging you should see the TX light (upper left light on cellular module) rapidly flashing. '''This may take up to 1 minute for the initial connection'''.<br /> <br /> * If you didn't create an explicit event for the day on [http://www.race-capture.com www.race-capture.com], it will create an 'ad hoc' event. Watch for it to show up automatically on your [http://race-capture.com/home home event page]<br /> <br /> * Still having troubles? Let us know on the [http://www.autosportlabs.org forums] and we'll help you out!</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapturePro_TelemetryQuickstart&diff=5754 2014-10-15T01:24:24Z

<p>Jstoezel: Undo revision 5753 by Jstoezel (talk)</p> <hr /> <div>=Unbox=<br /> <br /> =Install SIM Card into Telemetry Module=<br /> ==Purchasing a SIM Card==<br /> <br /> ===Which SIM card to get?===<br /> This is largely determined by the coverage map of the race track you'll be at. Use the coverage map checker for the respective carriers.<br /> <br /> ===T-Mobile===<br /> Purchase a &quot;Pay By the Day&quot; SIM card from your local T-Mobile dealer. We recommend picking a plan with the 2G/3G unlimited data, which is currently $3 USD/day. The plan is only charged when data is actually used during a 24 hour period. Visit [http://prepaid-phones.t-mobile.com/prepaid-plans T-Mobile] for more details on prepaid plans.<br /> <br /> [http://autosportlabs.net/RaceCapturePro_TelemetryQuickstart T-Mobile Coverage map tool]<br /> <br /> In the RaceAnalyzer software, configure the APN settings using the following values:<br /> *APN Host: epc.tmobile.com<br /> *APN User: &lt;leave this blank&gt;<br /> *APN Password: &lt;leave this blank&gt;<br /> <br /> ===AT&amp;T===<br /> In the RaceAnalyzer software, configure the APN settings using the following values:<br /> <br /> *APN Host: wap.cingular<br /> *APN User: wap@cingulargprs.com<br /> *APN Password: cingular1<br /> <br /> [http://www.att.com/maps/wireless-coverage.html AT&amp;T Coverage Map tool]<br /> <br /> <br /> [[Cellular_Telemetry_APNs|Big list of Carriers / APNs worldwide]]<br /> <br /> ==Installing SIM card==<br /> * Open telemetry enclosure<br /> Unscrew the end plate on the antenna side of the telemetry module and slide the board from the case.<br /> <br /> [[Image:telemetry unit half in enclosure.jpg]]<br /> <br /> ===Unlatch SIM card holder===<br /> Unlatch the card holder by gently sliding the cover in the 'open' direction and swing the cover open.<br /> <br /> ===Insert SIM card===<br /> Insert the SIM card, taking note of the beveled edge. The SIM card can only be inserted in one direction.<br /> <br /> [[Image:telemetry sim chip cover open.jpg]]<br /> <br /> ===Latch simcard holder in place===<br /> Swing the cover closed and slide towards the 'lock' position. take care that the cover is locked on both sides of the holder and it is flush with the board.<br /> <br /> [[Image:telemetry unit sim cover closed.jpg]]<br /> <br /> ===Re-assemble case===<br /> Slide board back into enclosure. Ensure LEDs are aligned with end plate and reattach end plate with screws. <br /> * You may need to gently press the LEDs down flush against the board in order for them to line up with the holes in the opposite end plate.<br /> <br /> =Connect components=<br /> <br /> ==Connecting Antenna==<br /> * Connect antenna to RF port<br /> Thread antenna onto RF port of telemetry module, position antenna in vertical position and then torque the nut, locking the antenna into position.<br /> *Don't overtorque! You only need a moderate amount of force on the nut.<br /> <br /> [[Image:telemetry unit white.jpg]]<br /> <br /> ==Connect Telemetry module to RaceCapture/Pro==<br /> * Connect Telemetry module to connectivity port (port to the right of pushbutton switch)<br /> [[Image:rcp and telemetry connected.jpg]]<br /> <br /> ==Telemetry LEDs==<br /> [[Image:telemetry_front.jpg]]<br /> <br /> ===Power LED===<br /> * Rightmost LED<br /> The telemetry module is powered by RaceCapture/Pro via the RJ11 tethered cable. It should glow constantly when powered up.<br /> <br /> ===Network status LED===<br /> * Middle LED<br /> The Network status LED will flash indicating the cellular network status.<br /> <br /> * '''Searching''': Flashes once per second when searching for the network<br /> * '''Registered on network''': Flashes slowly (once every 3 seconds) when registered to the cellular network.<br /> <br /> ===Transmit / Receive LEDs===<br /> The Transmit/Receive (TX/RX) LEDs indicate communication activity on the network, useful for diagnostics.<br /> * Top Left LED<br /> This LED will flash when RaceCapture/Pro is transmitting to the network.<br /> * Bottom Left LED<br /> This LED will flash when RaceCapture/Pro receives data from the network.<br /> <br /> When RaceCapture/Pro is streaming to the network you will observe a constant blinking of the Transmit LED.<br /> <br /> =Create a RCLive account and register your device=<br /> <br /> * Go to [http://www.race-capture.com www.race-capture.com], click on Signup in the top navigation<br /> * Create your account<br /> * After creating your account you will be prompted to add your device. Do it :)<br /> * Once added you will be given a device id, save this, you'll need it soon.<br /> <br /> =Install RaceAnalyzer=<br /> Follow the software installations instructions here: http://www.autosportlabs.net/RaceCapturePro_SoftwareOperation<br /> <br /> =Configure RaceCapture/Pro=<br /> For general RaceCapture/Pro installation and configuration be sure to review the [[RaceCapturePro_installation_guide|Installation]] and [[RaceCapturePro_SoftwareOperation|Software]] guides.<br /> <br /> ===Read Configuration===<br /> '''Before configuring any parameters [[RaceCapturePro_SoftwareOperation#Reading_Configuration|read the configuration]] from RaceCapture/Pro'''<br /> <br /> ===Set channel sample rates===<br /> <br /> Note, with the real-time telemetry sample rates are automatically limited to 10Hz. Logging to local SD card will be at the normal sample rates defined in the configuration.<br /> <br /> ====Available bandwidth====<br /> The total available data rate is a function of number of channels combined with sample rate and is also affected by cellular network conditions. We will have an expanded guide and tool set to help identify optimal sample rates.<br /> <br /> ===Set device id===<br /> <br /> Add your device id that you wrote down when adding your device to race-capture.com to the Telemetry Device Id field under the Logging/Telemetry section:<br /> [[File:Devicesetup.png]]<br /> <br /> ==Write configuration==<br /> * Click the 'Write' button in RaceAnalyzer<br /> * Power cycle RCP (turn off then on again)<br /> <br /> ==Testing==<br /> RaceCapture/Pro with GPS &amp; telemetry needs more power than a regular USB port can supply. You'll either need to connect it to your car's power directly, via a cigarette power adapter with wires or a powered usb hub similar to these:<br /> <br /> * [http://www.amazon.com/Sabrent-Powered-adapter-compatible-HB-USB30/dp/B00BJPRI1Y/ref=sr_1_3?ie=UTF8&amp;qid=1367991516&amp;sr=8-3&amp;keywords=usb+hub+high+power Sabrent Powered USB hub]<br /> * [http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF/ref=sr_1_5?ie=UTF8&amp;qid=1367991578&amp;sr=8-5&amp;keywords=usb+hub+high+power D-Link powered hub]<br /> <br /> We have not tested the above units; we offer them as suggestions of possible USB hubs with enhanced power capabilities.<br /> <br /> Press the black switch on the front of your RaceCapture/Pro device to start logging. You will observe the Transmit LED blinking rapidly once the Cellular module is registered to the cellular network and after the link has been initialized, which ranges from a few seconds and up to 1 minute.<br /> <br /> Got to [http://race-capture.com/home race-capture.com/home], you should see a new event labeled 'Ad-hoc event ...', click on it, then click on your device on the next page.<br /> <br /> ==Success==<br /> View your live telemetry!<br /> Race faster!<br /> <br /> =Troubleshooting=<br /> <br /> If you cannot see data flowing to [http://www.race-capture.com www.race-capture.com] check the following:<br /> <br /> * You have $$ on your sim card from T-Mobile. <br /> ** Refill [http://prepaid-phones.t-mobile.com/prepaid-refill T-Mobile Refill site]<br /> <br /> * Your RaceCapture/Pro logging rates are set to the suggested sample rates<br /> <br /> * You are powering RaceCapture/Pro using a 12v power supply through the terminal block. It will not work over computer USB power due to power constraints<br /> <br /> * When connected to the cell network you should see a slow flash on the cellular module's status light - 1 flash every 3 seconds<br /> <br /> * When actively logging you should see the TX light (upper left light on cellular module) rapidly flashing. '''This may take up to 1 minute for the initial connection'''.<br /> <br /> * If you didn't create an explicit event for the day on [http://www.race-capture.com www.race-capture.com], it will create an 'ad hoc' event. Watch for it to show up automatically on your [http://race-capture.com/home home event page]<br /> <br /> * Still having troubles? Let us know on the [http://www.autosportlabs.org forums] and we'll help you out!</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapturePro_TelemetryQuickstart&diff=5753 2014-10-15T01:21:56Z

<p>Jstoezel: </p> <hr /> <div>=Unbox=<br /> <br /> =Install SIM Card into Telemetry Module=<br /> ==Purchasing a SIM Card==<br /> <br /> ===Which SIM card to get?===<br /> This is largely determined by the coverage map of the race track you'll be at. Use the coverage map checker for the respective carriers.<br /> <br /> ===T-Mobile===<br /> Purchase a &quot;Pay By the Day&quot; SIM card from your local T-Mobile dealer. We recommend picking a plan with the 2G/3G unlimited data, which is currently $3 USD/day. The plan is only charged when data is actually used during a 24 hour period. Visit [http://prepaid-phones.t-mobile.com/prepaid-plans T-Mobile] for more details on prepaid plans.<br /> <br /> [http://autosportlabs.net/RaceCapturePro_TelemetryQuickstart T-Mobile Coverage map tool]<br /> <br /> In the RaceAnalyzer software, configure the APN settings using the following values:<br /> *APN Host: epc.tmobile.com<br /> *APN User: &lt;leave this blank&gt;<br /> *APN Password: &lt;leave this blank&gt;<br /> <br /> ===AT&amp;T===<br /> In the RaceAnalyzer software, configure the APN settings using the following values:<br /> <br /> *APN Host: wap.cingular<br /> *APN User: wap@cingulargprs.com<br /> *APN Password: cingular1<br /> <br /> [http://www.att.com/maps/wireless-coverage.html AT&amp;T Coverage Map tool]<br /> <br /> <br /> [[Cellular_Telemetry_APNs|Big list of Carriers / APNs worldwide]]<br /> <br /> ==Installing SIM card==<br /> <br /> TODO<br /> <br /> ===Unlatch SIM card holder===<br /> <br /> TODO<br /> <br /> ===Insert SIM card===<br /> <br /> TODO<br /> <br /> ===Latch simcard holder in place===<br /> <br /> TODO<br /> <br /> ===Re-assemble case===<br /> <br /> TODO<br /> <br /> =Connect components=<br /> <br /> ==Connecting Antenna==<br /> * Connect antenna to RF port<br /> <br /> TODO<br /> <br /> ==Telemetry LEDs==<br /> <br /> TODO<br /> <br /> ===Network status LED===<br /> <br /> TODO<br /> <br /> ===Transmit / Receive LEDs===<br /> <br /> TODO<br /> <br /> =Create a RCLive account and register your device=<br /> <br /> * Go to [http://www.race-capture.com www.race-capture.com], click on Signup in the top navigation<br /> * Create your account<br /> * After creating your account you will be prompted to add your device. Do it :)<br /> * Once added you will be given a device id, save this, you'll need it soon.<br /> <br /> =Install RaceAnalyzer=<br /> Follow the software installations instructions here: http://www.autosportlabs.net/RaceCapturePro_SoftwareOperation<br /> <br /> =Configure RaceCapture/Pro=<br /> For general RaceCapture/Pro installation and configuration be sure to review the [[RaceCapturePro_installation_guide|Installation]] and [[RaceCapturePro_SoftwareOperation|Software]] guides.<br /> <br /> ===Read Configuration===<br /> '''Before configuring any parameters [[RaceCapturePro_SoftwareOperation#Reading_Configuration|read the configuration]] from RaceCapture/Pro'''<br /> <br /> ===Set channel sample rates===<br /> <br /> Note, with the real-time telemetry sample rates are automatically limited to 10Hz. Logging to local SD card will be at the normal sample rates defined in the configuration.<br /> <br /> ====Available bandwidth====<br /> The total available data rate is a function of number of channels combined with sample rate and is also affected by cellular network conditions. We will have an expanded guide and tool set to help identify optimal sample rates.<br /> <br /> ===Set device id===<br /> <br /> Add your device id that you wrote down when adding your device to race-capture.com to the Telemetry Device Id field under the Logging/Telemetry section:<br /> [[File:Devicesetup.png]]<br /> <br /> ==Write configuration==<br /> * Click the 'Write' button in RaceAnalyzer<br /> * Power cycle RCP (turn off then on again)<br /> <br /> ==Testing==<br /> RaceCapture/Pro with GPS &amp; telemetry needs more power than a regular USB port can supply. You'll either need to connect it to your car's power directly, via a cigarette power adapter with wires or a powered usb hub similar to these:<br /> <br /> * [http://www.amazon.com/Sabrent-Powered-adapter-compatible-HB-USB30/dp/B00BJPRI1Y/ref=sr_1_3?ie=UTF8&amp;qid=1367991516&amp;sr=8-3&amp;keywords=usb+hub+high+power Sabrent Powered USB hub]<br /> * [http://www.amazon.com/D-Link-DUB-H7-High-Speed-7-Port/dp/B00008VFAF/ref=sr_1_5?ie=UTF8&amp;qid=1367991578&amp;sr=8-5&amp;keywords=usb+hub+high+power D-Link powered hub]<br /> <br /> We have not tested the above units; we offer them as suggestions of possible USB hubs with enhanced power capabilities.<br /> <br /> Press the black switch on the front of your RaceCapture/Pro device to start logging. You will observe the Transmit LED blinking rapidly once the Cellular module is registered to the cellular network and after the link has been initialized, which ranges from a few seconds and up to 1 minute.<br /> <br /> Got to [http://race-capture.com/home race-capture.com/home], you should see a new event labeled 'Ad-hoc event ...', click on it, then click on your device on the next page.<br /> <br /> ==Success==<br /> View your live telemetry!<br /> Race faster!<br /> <br /> =Troubleshooting=<br /> <br /> If you cannot see data flowing to [http://www.race-capture.com www.race-capture.com] check the following:<br /> <br /> * You have $$ on your sim card from T-Mobile. <br /> ** Refill [http://prepaid-phones.t-mobile.com/prepaid-refill T-Mobile Refill site]<br /> <br /> * Your RaceCapture/Pro logging rates are set to the suggested sample rates<br /> <br /> * You are powering RaceCapture/Pro using a 12v power supply through the terminal block. It will not work over computer USB power due to power constraints<br /> <br /> * When connected to the cell network you should see a slow flash on the cellular module's status light - 1 flash every 3 seconds<br /> <br /> * When actively logging you should see the TX light (upper left light on cellular module) rapidly flashing. '''This may take up to 1 minute for the initial connection'''.<br /> <br /> * If you didn't create an explicit event for the day on [http://www.race-capture.com www.race-capture.com], it will create an 'ad hoc' event. Watch for it to show up automatically on your [http://race-capture.com/home home event page]<br /> <br /> * Still having troubles? Let us know on the [http://www.autosportlabs.org forums] and we'll help you out!</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapturePro_mk2_QuickStart&diff=5752 2014-10-15T01:17:15Z

<p>Jstoezel: </p> <hr /> <div>==10 minute RaceCapture/Pro mk2 Quick Start==<br /> These quick start instructions will get you logging data in 10 minutes with 50Hz GPS and 30Hz accelerometer and Yaw sensor sampling rate. <br /> <br /> Let's begin!<br /> ==RaceCapture/Pro mk2 Quickstart Guide==<br /> <br /> ===Get a memory card===<br /> * Find yourself a memory card between 2 and 32GB in capacity. Not required, but bonus points for formatting and removing clutter.<br /> * Push it in to the slot until it's seated. <br /> ** The card slot is a &quot;push-in / &quot;push-out&quot; design like a clicky ball-point pen; the card is properly seated when it's in the innermost position.<br /> <br /> ===Secure===<br /> <br /> Mount RaceCapture/Pro securely to your car.<br /> <br /> * Ideally mount the unit flat and in the center of to get the best effect from the built-in Yaw Sensor.<br /> * If you're desperate for a quick test, there's no shame in bungie-ing / rubber-banding it to your arm rest!<br /> <br /> ===GPS===<br /> <br /> * Place the GPS antenna on the roof of the car via it's magnetic mount.<br /> * Connect the GPS antenna to the RaceCapture/Pro<br /> * For a quick test, just toss the GPS module onto the dash or the floor of the car!<br /> <br /> ===Power===<br /> <br /> Provide power to RaceCapture/Pro. You can do this in several ways:<br /> * Hard-wire it to a 9-24v power source, such as your car's electrical system.<br /> TBC** RaceCapture/Pro consumes very little power when running (about 100mA) so you can tap into most any existing circuit that has an ignition switched voltage source.<br /> <br /> * Power it from a USB charge port in your car<br /> ** Use the included USB cable to connect to a USB charge connection in your car.<br /> ** Since the USB cable can vibrate loose, this is a quick and dirty solution, and we only recommend it for ad-hoc testing!<br /> <br /> * Power it via USB from your computer<br /> ** It gets boring quickly, but this is good if you want to just 'bench test' the system.<br /> <br /> ===Verify===<br /> Turn the power on to the unit and wait until the lights on the front panel indicate the unit's state:<br /> * Lower Left LED: Steady green when the unit has power.<br /> * Lower Right LED: Flashes once per second when acquiring GPS lock.<br /> * Lower Right LED: Flashes ten times per second when GPS lock is acquired.<br /> <br /> ===Log===<br /> Once you have GPS lock, press the button on the front to start logging data!<br /> * The default configuration of RaceCapture/Pro is to log 50Hz GPS and 30Hz accelerometer and yaw.<br /> * There are ways to automatically start/stop logging! see our [[RaceCapturePro_HowTo|How-To guide]] for more information<br /> * You should see the upper right LED flashing rapidly, indicating data is being written to the card.<br /> ** If you see the red light appear, there was a problem writing to the SD card. Verify you have a card that's in good shape (you can read/write to it) and it's fully inserted.<br /> <br /> ===Rinse/Repeat===<br /> You can start stop logging as much as you want. Each time logging starts, a new numbered log file is created on the SD card.<br /> <br /> ===View / Analyze===<br /> Load the log file into the [[RaceCapturePro_SoftwareOperation|Race Analyzer]] software, or, you can manually analyse the raw data since the files are written in plain Comma Separated Values (CSV).</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapture-Pro_MK1&diff=5751 2014-10-15T01:11:59Z

<p>Jstoezel: /* Race Capture Pro MK2 Quick Links */</p> <hr /> <div>==Race Capture Pro MK2 Quick Links==<br /> * [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> <br /> *'''[[RaceCapturePro_V2_software|Version 2 BETA software and app]]<br /> <br /> *'''[[RaceCapturePro_mk2_QuickStart|Super Quick Start]]'''<br /> *'''[[RaceCapturePro_TelemetryQuickstart|Realtime Telemetry Quick Start]]'''<br /> *'''[[RaceCapturePro_Downloads|Software and Firmware downloads]]'''<br /> *'''[[RaceCapturePro_Sensors|Sensor Guide]]'''<br /> *'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''<br /> *[[RaceCapturePro_FAQ|FAQ / &quot;How Do I...?&quot;]]<br /> *[[RaceCapturePro_installation_guide|Installation Guide]]<br /> *[[RaceCapturePro_SoftwareOperation|Software Operation Guide]]<br /> *[https://github.com/autosportlabs Source code]<br /> *[[RaceCapture/Pro_Feature_List|Upcoming Features]]<br /> *[[RaceTracks|List of supported Race Tracks and Track Maps]]<br /> <br /> <br /> [[Image:RaceCapturePro_inforgraphic.jpg|800px|center]]<br /> <br /> &lt;br/&gt;<br /> <br /> ==Open Source Data Acquisition and Control==<br /> '''Autosport Labs is excited to announce our latest project: RaceCapture/Pro mk2 - a powerful, multi-channel data acquisition and control system for motorsport applications'''<br /> ==Impact==<br /> RaceCapture/Pro transcends most traditional &quot;Data Logging&quot; systems by virtue of its powerful processor, an emphasis on outputs as well as inputs, and on-board Lua scripting that lets you define custom behaviors. The ability to perform data acquisition while controlling other devices and systems, coupled with flexible end-user customization offers an unprecedented level of capability.<br /> <br /> ==Significance==<br /> While the primary application of RaceCapture/Pro mk2 is focused towards race car data acquisition, its powerful processor combined with a wealth of inputs and outputs also makes RaceCapture/Pro a general purpose automotive computer, one capable of handling many different tasks - limited only by your imagination. If the question is &quot;Can RaceCapture do ...?&quot; the answer will likely be 'Yes' and often with little to no external hardware support necessary.<br /> <br /> ==Flexibility==<br /> <br /> ===On-board scripting===<br /> We embedded the [http://www.lua.org Lua] scripting language right on board RaceCapture/Pro; with Lua you can control RaceCapture's behavior at run-time, no firmware programming required.<br /> <br /> Some Examples:<br /> ** Activate a warning light when an input threshold is exceeded, such as temperature or pressure, or a combination of both<br /> ** Log data at a higher rate when in range of a particular GPS coordinate, or when some other condition is met<br /> ** Auto-start/stop logging based on speed, RPM, or any other condition<br /> ** Experiment with active aerodynamics by adjusting a wing based on GPS velocity<br /> ** Define logic to control an intercooler sprayer<br /> ** Intercept and remap an OEM sensor<br /> ** Activate Smoke screens against your competitors :)<br /> <br /> ===Software Connectivity===<br /> RaceCapture/Pro features software to:<br /> * Customize logging channels<br /> * View Runtime Data<br /> * Edit custom scripting<br /> * Perform data analysis and replay<br /> <br /> ===Infinite Possibilities===<br /> * Far more than a data-logging system: flexible Inputs and Outputs coupled with a powerful processor offers endless customization<br /> * Share configurations, tips and ideas with our online community<br /> * '''Fully Open Source System - Open Standards, Open File format''' Frequent software updates and end-user customizable!<br /> * [https://github.com/autosportlabs Source code]<br /> <br /> ==Technical Specifications==<br /> <br /> &lt;font size=&quot;3&quot;&gt;Extreme flexibility comes with a powerful processor and a wealth of inputs and outputs. &lt;/font&gt;<br /> <br /> ===Input and Output Channels===<br /> RaceCapture mk2 offers 21 input and output channels and serial communication port, enough to handle complex logging and control tasks.<br /> <br /> * '''7 dedicated 0-5v analog input channels'''<br /> ** Measure sensors or process input from other devices.<br /> <br /> * '''3 dedicated 0-5v frequency input channels'''<br /> ** Measure RPM, wheel speed, or any kind of periodic pulse.<br /> <br /> * '''4 configurable 0-5v analog or frequency output (PWM) channels'''<br /> ** Control other systems or even override OEM sensors<br /> <br /> * '''3 configurable digital channels, settable for input or output'''<br /> ** Receive input from switches or digital signals; or configure as output and use to activate accessories or drive indicator lamps with on-board 1A self-protected mosfets<br /> <br /> * '''4 Axis Accelerometer: 3 channel accelerometer module plus Z-axis gyro (+/- 2G per axis, 3G optional)'''<br /> ** Measure and log 3D G-force in real-time with one of the industry's most accurate accelerometers.<br /> ** Z-axis gyroscope measures yaw/drift in real-time.<br /> <br /> * '''50Hz GPS module'''<br /> ** Internal state of the art GPS module<br /> *** Plot location, speed and time. Onboard detection of start/finish line for automatic lap count and lap time. Real time predictive timing.<br /> <br /> * '''Auxiliary Serial Port'''<br /> ** Interface to real time telemetry, bluetooth adapter, dashboard display or other interface<br /> <br /> * '''CAN Bus Expansion'''<br /> ** Two high speed CAN bus ports provide the ability to virtually interface with any type of CAN bus enabled equipment, from ECUs to tire temperature sensors.<br /> <br /> ===Logging===<br /> * '''SD Memory card slot for data acquisition'''<br /> ** Store up to 32GB of logging data<br /> <br /> ===CPU===<br /> * '''168MHz 32 bit ARM processor'''<br /> ** Enough juice to perform high resolution logging and running complex, user-defined logic<br /> <br /> ===Input/Output Protection===<br /> * '''40v protection''' on all input pins<br /> * Analog outputs protected by '''auto-resettable fuses'''<br /> * Digital outputs are rated at '''1A with self-protected mosfets'''<br /> * '''Over-current protection''' on 5V reference<br /> * '''2A''' internal switching power supply<br /> <br /> ===Mechanical===<br /> * '''Compact, rugged design '''<br /> ** Unit measures approximately 4 x 3 inches (100 x 82 mm) <br /> ** Weighs 8.4oz<br /> ** Real-Time module weighs 7oz<br /> * Easy to use screw terminal block for wiring<br /> * On-board 'action' switch to start/stop logging (or other use)<br /> * On-board Status LEDs<br /> <br /> ===Power===<br /> *** TODO ***<br /> * 9-17v power<br /> * &lt; 100mA for RaceCapture/Pro. <br /> * May burst to 2A temporarily when using RealTime Telemetry module<br /> <br /> ==Example Sensor Connectivity==<br /> &lt;center&gt;<br /> [[Image:RaceCapturePro_infographic_sensors.jpg]]<br /> <br /> <br /> [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> &lt;/center&gt;</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapturePro_mk2_QuickStart&diff=5750 2014-10-15T01:11:26Z

<p>Jstoezel: Created page with &quot;TODO&quot;</p> <hr /> <div>TODO</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapture-Pro_MK1&diff=5749 2014-10-15T01:10:11Z

<p>Jstoezel: </p> <hr /> <div>==Race Capture Pro MK2 Quick Links==<br /> * [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> <br /> *'''[[RaceCapturePro_V2_software|Version 2 BETA software and app]]<br /> <br /> *'''[[RaceCapturePro_QuickStart|Super Quick Start]]'''<br /> *'''[[RaceCapturePro_TelemetryQuickstart|Realtime Telemetry Quick Start]]'''<br /> *'''[[RaceCapturePro_Downloads|Software and Firmware downloads]]'''<br /> *'''[[RaceCapturePro_Sensors|Sensor Guide]]'''<br /> *'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''<br /> *[[RaceCapturePro_FAQ|FAQ / &quot;How Do I...?&quot;]]<br /> *[[RaceCapturePro_installation_guide|Installation Guide]]<br /> *[[RaceCapturePro_SoftwareOperation|Software Operation Guide]]<br /> *[https://github.com/autosportlabs Source code]<br /> *[[RaceCapture/Pro_Feature_List|Upcoming Features]]<br /> *[[RaceTracks|List of supported Race Tracks and Track Maps]]<br /> <br /> <br /> [[Image:RaceCapturePro_inforgraphic.jpg|800px|center]]<br /> <br /> &lt;br/&gt;<br /> <br /> ==Open Source Data Acquisition and Control==<br /> '''Autosport Labs is excited to announce our latest project: RaceCapture/Pro mk2 - a powerful, multi-channel data acquisition and control system for motorsport applications'''<br /> ==Impact==<br /> RaceCapture/Pro transcends most traditional &quot;Data Logging&quot; systems by virtue of its powerful processor, an emphasis on outputs as well as inputs, and on-board Lua scripting that lets you define custom behaviors. The ability to perform data acquisition while controlling other devices and systems, coupled with flexible end-user customization offers an unprecedented level of capability.<br /> <br /> ==Significance==<br /> While the primary application of RaceCapture/Pro mk2 is focused towards race car data acquisition, its powerful processor combined with a wealth of inputs and outputs also makes RaceCapture/Pro a general purpose automotive computer, one capable of handling many different tasks - limited only by your imagination. If the question is &quot;Can RaceCapture do ...?&quot; the answer will likely be 'Yes' and often with little to no external hardware support necessary.<br /> <br /> ==Flexibility==<br /> <br /> ===On-board scripting===<br /> We embedded the [http://www.lua.org Lua] scripting language right on board RaceCapture/Pro; with Lua you can control RaceCapture's behavior at run-time, no firmware programming required.<br /> <br /> Some Examples:<br /> ** Activate a warning light when an input threshold is exceeded, such as temperature or pressure, or a combination of both<br /> ** Log data at a higher rate when in range of a particular GPS coordinate, or when some other condition is met<br /> ** Auto-start/stop logging based on speed, RPM, or any other condition<br /> ** Experiment with active aerodynamics by adjusting a wing based on GPS velocity<br /> ** Define logic to control an intercooler sprayer<br /> ** Intercept and remap an OEM sensor<br /> ** Activate Smoke screens against your competitors :)<br /> <br /> ===Software Connectivity===<br /> RaceCapture/Pro features software to:<br /> * Customize logging channels<br /> * View Runtime Data<br /> * Edit custom scripting<br /> * Perform data analysis and replay<br /> <br /> ===Infinite Possibilities===<br /> * Far more than a data-logging system: flexible Inputs and Outputs coupled with a powerful processor offers endless customization<br /> * Share configurations, tips and ideas with our online community<br /> * '''Fully Open Source System - Open Standards, Open File format''' Frequent software updates and end-user customizable!<br /> * [https://github.com/autosportlabs Source code]<br /> <br /> ==Technical Specifications==<br /> <br /> &lt;font size=&quot;3&quot;&gt;Extreme flexibility comes with a powerful processor and a wealth of inputs and outputs. &lt;/font&gt;<br /> <br /> ===Input and Output Channels===<br /> RaceCapture mk2 offers 21 input and output channels and serial communication port, enough to handle complex logging and control tasks.<br /> <br /> * '''7 dedicated 0-5v analog input channels'''<br /> ** Measure sensors or process input from other devices.<br /> <br /> * '''3 dedicated 0-5v frequency input channels'''<br /> ** Measure RPM, wheel speed, or any kind of periodic pulse.<br /> <br /> * '''4 configurable 0-5v analog or frequency output (PWM) channels'''<br /> ** Control other systems or even override OEM sensors<br /> <br /> * '''3 configurable digital channels, settable for input or output'''<br /> ** Receive input from switches or digital signals; or configure as output and use to activate accessories or drive indicator lamps with on-board 1A self-protected mosfets<br /> <br /> * '''4 Axis Accelerometer: 3 channel accelerometer module plus Z-axis gyro (+/- 2G per axis, 3G optional)'''<br /> ** Measure and log 3D G-force in real-time with one of the industry's most accurate accelerometers.<br /> ** Z-axis gyroscope measures yaw/drift in real-time.<br /> <br /> * '''50Hz GPS module'''<br /> ** Internal state of the art GPS module<br /> *** Plot location, speed and time. Onboard detection of start/finish line for automatic lap count and lap time. Real time predictive timing.<br /> <br /> * '''Auxiliary Serial Port'''<br /> ** Interface to real time telemetry, bluetooth adapter, dashboard display or other interface<br /> <br /> * '''CAN Bus Expansion'''<br /> ** Two high speed CAN bus ports provide the ability to virtually interface with any type of CAN bus enabled equipment, from ECUs to tire temperature sensors.<br /> <br /> ===Logging===<br /> * '''SD Memory card slot for data acquisition'''<br /> ** Store up to 32GB of logging data<br /> <br /> ===CPU===<br /> * '''168MHz 32 bit ARM processor'''<br /> ** Enough juice to perform high resolution logging and running complex, user-defined logic<br /> <br /> ===Input/Output Protection===<br /> * '''40v protection''' on all input pins<br /> * Analog outputs protected by '''auto-resettable fuses'''<br /> * Digital outputs are rated at '''1A with self-protected mosfets'''<br /> * '''Over-current protection''' on 5V reference<br /> * '''2A''' internal switching power supply<br /> <br /> ===Mechanical===<br /> * '''Compact, rugged design '''<br /> ** Unit measures approximately 4 x 3 inches (100 x 82 mm) <br /> ** Weighs 8.4oz<br /> ** Real-Time module weighs 7oz<br /> * Easy to use screw terminal block for wiring<br /> * On-board 'action' switch to start/stop logging (or other use)<br /> * On-board Status LEDs<br /> <br /> ===Power===<br /> *** TODO ***<br /> * 9-17v power<br /> * &lt; 100mA for RaceCapture/Pro. <br /> * May burst to 2A temporarily when using RealTime Telemetry module<br /> <br /> ==Example Sensor Connectivity==<br /> &lt;center&gt;<br /> [[Image:RaceCapturePro_infographic_sensors.jpg]]<br /> <br /> <br /> [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> &lt;/center&gt;</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapture-Pro_MK1&diff=5748 2014-10-15T01:09:11Z

<p>Jstoezel: </p> <hr /> <div>==Race Capture Pro MK2 Quick Links==<br /> * [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> <br /> *'''[[RaceCapturePro_V2_software|Version 2 BETA software and app]]<br /> <br /> *'''[[RaceCapturePro_QuickStart|Super Quick Start]]'''<br /> *'''[[RaceCapturePro_TelemetryQuickstart|Realtime Telemetry Quick Start]]'''<br /> *'''[[RaceCapturePro_Downloads|Software and Firmware downloads]]'''<br /> *'''[[RaceCapturePro_Sensors|Sensor Guide]]'''<br /> *'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''<br /> *[[RaceCapturePro_FAQ|FAQ / &quot;How Do I...?&quot;]]<br /> *[[RaceCapturePro_installation_guide|Installation Guide]]<br /> *[[RaceCapturePro_SoftwareOperation|Software Operation Guide]]<br /> *[https://github.com/autosportlabs Source code]<br /> *[[RaceCapture/Pro_Feature_List|Upcoming Features]]<br /> *[[RaceTracks|List of supported Race Tracks and Track Maps]]<br /> <br /> <br /> [[Image:RaceCapturePro_inforgraphic.jpg|800px|center]]<br /> <br /> [[File:RaceCapturePro_RevF_with_gps.jpg|thumb|200px|right|10Hz GPS]]<br /> [[File:RaceCapturePro_main_board_small.jpg|thumb|200px|right|Rev F board]]<br /> [[File:RaceCapturePro_led_view_medium.jpg|thumb|200px|right|Connectors View]]<br /> [[File:raceCapture_terminal_block_view_small.jpg|thumb|200px|right|Terminal Block]]<br /> [[File:RCP_MK2_CAN_bus_pinout.png|thumb|200px|right|CAN Bus Expansion Connector]]<br /> [[File:RCP_MK2_RS232_pinout.png|thumb|200px|right|External Telemetry and Auxiliary Serial Ports]]<br /> &lt;br/&gt;<br /> <br /> ==Open Source Data Acquisition and Control==<br /> '''Autosport Labs is excited to announce our latest project: RaceCapture/Pro mk2 - a powerful, multi-channel data acquisition and control system for motorsport applications'''<br /> ==Impact==<br /> RaceCapture/Pro transcends most traditional &quot;Data Logging&quot; systems by virtue of its powerful processor, an emphasis on outputs as well as inputs, and on-board Lua scripting that lets you define custom behaviors. The ability to perform data acquisition while controlling other devices and systems, coupled with flexible end-user customization offers an unprecedented level of capability.<br /> <br /> ==Significance==<br /> While the primary application of RaceCapture/Pro mk2 is focused towards race car data acquisition, its powerful processor combined with a wealth of inputs and outputs also makes RaceCapture/Pro a general purpose automotive computer, one capable of handling many different tasks - limited only by your imagination. If the question is &quot;Can RaceCapture do ...?&quot; the answer will likely be 'Yes' and often with little to no external hardware support necessary.<br /> <br /> ==Flexibility==<br /> <br /> ===On-board scripting===<br /> We embedded the [http://www.lua.org Lua] scripting language right on board RaceCapture/Pro; with Lua you can control RaceCapture's behavior at run-time, no firmware programming required.<br /> <br /> Some Examples:<br /> ** Activate a warning light when an input threshold is exceeded, such as temperature or pressure, or a combination of both<br /> ** Log data at a higher rate when in range of a particular GPS coordinate, or when some other condition is met<br /> ** Auto-start/stop logging based on speed, RPM, or any other condition<br /> ** Experiment with active aerodynamics by adjusting a wing based on GPS velocity<br /> ** Define logic to control an intercooler sprayer<br /> ** Intercept and remap an OEM sensor<br /> ** Activate Smoke screens against your competitors :)<br /> <br /> ===Software Connectivity===<br /> RaceCapture/Pro features software to:<br /> * Customize logging channels<br /> * View Runtime Data<br /> * Edit custom scripting<br /> * Perform data analysis and replay<br /> <br /> ===Infinite Possibilities===<br /> * Far more than a data-logging system: flexible Inputs and Outputs coupled with a powerful processor offers endless customization<br /> * Share configurations, tips and ideas with our online community<br /> * '''Fully Open Source System - Open Standards, Open File format''' Frequent software updates and end-user customizable!<br /> * [https://github.com/autosportlabs Source code]<br /> <br /> ==Technical Specifications==<br /> <br /> &lt;font size=&quot;3&quot;&gt;Extreme flexibility comes with a powerful processor and a wealth of inputs and outputs. &lt;/font&gt;<br /> <br /> ===Input and Output Channels===<br /> RaceCapture mk2 offers 21 input and output channels and serial communication port, enough to handle complex logging and control tasks.<br /> <br /> * '''7 dedicated 0-5v analog input channels'''<br /> ** Measure sensors or process input from other devices.<br /> <br /> * '''3 dedicated 0-5v frequency input channels'''<br /> ** Measure RPM, wheel speed, or any kind of periodic pulse.<br /> <br /> * '''4 configurable 0-5v analog or frequency output (PWM) channels'''<br /> ** Control other systems or even override OEM sensors<br /> <br /> * '''3 configurable digital channels, settable for input or output'''<br /> ** Receive input from switches or digital signals; or configure as output and use to activate accessories or drive indicator lamps with on-board 1A self-protected mosfets<br /> <br /> * '''4 Axis Accelerometer: 3 channel accelerometer module plus Z-axis gyro (+/- 2G per axis, 3G optional)'''<br /> ** Measure and log 3D G-force in real-time with one of the industry's most accurate accelerometers.<br /> ** Z-axis gyroscope measures yaw/drift in real-time.<br /> <br /> * '''50Hz GPS module'''<br /> ** Internal state of the art GPS module<br /> *** Plot location, speed and time. Onboard detection of start/finish line for automatic lap count and lap time. Real time predictive timing.<br /> <br /> * '''Auxiliary Serial Port'''<br /> ** Interface to real time telemetry, bluetooth adapter, dashboard display or other interface<br /> <br /> * '''CAN Bus Expansion'''<br /> ** Two high speed CAN bus ports provide the ability to virtually interface with any type of CAN bus enabled equipment, from ECUs to tire temperature sensors.<br /> <br /> ===Logging===<br /> * '''SD Memory card slot for data acquisition'''<br /> ** Store up to 32GB of logging data<br /> <br /> ===CPU===<br /> * '''168MHz 32 bit ARM processor'''<br /> ** Enough juice to perform high resolution logging and running complex, user-defined logic<br /> <br /> ===Input/Output Protection===<br /> * '''40v protection''' on all input pins<br /> * Analog outputs protected by '''auto-resettable fuses'''<br /> * Digital outputs are rated at '''1A with self-protected mosfets'''<br /> * '''Over-current protection''' on 5V reference<br /> * '''2A''' internal switching power supply<br /> <br /> ===Mechanical===<br /> * '''Compact, rugged design '''<br /> ** Unit measures approximately 4 x 3 inches (100 x 82 mm) <br /> ** Weighs 8.4oz<br /> ** Real-Time module weighs 7oz<br /> * Easy to use screw terminal block for wiring<br /> * On-board 'action' switch to start/stop logging (or other use)<br /> * On-board Status LEDs<br /> <br /> ===Power===<br /> *** TODO ***<br /> * 9-17v power<br /> * &lt; 100mA for RaceCapture/Pro. <br /> * May burst to 2A temporarily when using RealTime Telemetry module<br /> <br /> ==Example Sensor Connectivity==<br /> &lt;center&gt;<br /> [[Image:RaceCapturePro_infographic_sensors.jpg]]<br /> <br /> <br /> [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> &lt;/center&gt;</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=RaceCapture-Pro_MK1&diff=5747 2014-10-14T14:00:41Z

<p>Jstoezel: </p> <hr /> <div>==Race Capture Pro MK2 Quick Links==<br /> * [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> <br /> *'''[[RaceCapturePro_V2_software|Version 2 BETA software and app]]<br /> <br /> *'''[[RaceCapturePro_QuickStart|Super Quick Start]]'''<br /> *'''[[RaceCapturePro_TelemetryQuickstart|Realtime Telemetry Quick Start]]'''<br /> *'''[[RaceCapturePro_Downloads|Software and Firmware downloads]]'''<br /> *'''[[RaceCapturePro_Sensors|Sensor Guide]]'''<br /> *'''[[RaceCapturePro_Lua_Scripting|Lua Scripting Guide]]'''<br /> *[[RaceCapturePro_FAQ|FAQ / &quot;How Do I...?&quot;]]<br /> *[[RaceCapturePro_installation_guide|Installation Guide]]<br /> *[[RaceCapturePro_SoftwareOperation|Software Operation Guide]]<br /> *[https://github.com/autosportlabs Source code]<br /> *[[RaceCapture/Pro_Feature_List|Upcoming Features]]<br /> *[[RaceTracks|List of supported Race Tracks and Track Maps]]<br /> <br /> <br /> [[Image:RaceCapturePro_inforgraphic.jpg|800px|center]]<br /> <br /> [[File:RaceCapturePro_RevF_with_gps.jpg|thumb|200px|right|10Hz GPS]]<br /> [[File:RaceCapturePro_main_board_small.jpg|thumb|200px|right|Rev F board]]<br /> [[File:RaceCapturePro_led_view_medium.jpg|thumb|200px|right|Connectors View]]<br /> [[File:raceCapture_terminal_block_view_small.jpg|thumb|200px|right|Terminal Block]]<br /> [[File:RCP_MK2_CAN_bus_pinout.png|thumb|200px|right|CAN Bus Expansion Connector]]<br /> [[File:RCP_MK2_RS232_pinout.png|thumb|200px|right|External Telemetry and Auxiliary Serial Ports]]<br /> &lt;br/&gt;<br /> <br /> ==Open Source Data Acquisition and Control==<br /> '''Autosport Labs is excited to announce our latest project: RaceCapture/Pro - a powerful, multi-channel data acquisition and control system for motorsport applications'''<br /> ==Impact==<br /> RaceCapture/Pro transcends most traditional &quot;Data Logging&quot; systems by virtue of its powerful processor, an emphasis on outputs as well as inputs, and on-board Lua scripting that lets you define custom behaviors. The ability to perform data acquisition while controlling other devices and systems, coupled with flexible end-user customization offers an unprecedented level of capability.<br /> <br /> ==Significance==<br /> While the primary application of RaceCapture/Pro is focused towards race car data acquisition, its powerful processor combined with a wealth of inputs and outputs also makes RaceCapture/Pro a general purpose automotive computer, one capable of handling many different tasks - limited only by your imagination. If the question is &quot;Can RaceCapture do ...?&quot; the answer will likely be 'Yes' and often with little to no external hardware support necessary.<br /> <br /> ==Flexibility==<br /> <br /> ===On-board scripting===<br /> We embedded the [http://www.lua.org Lua] scripting language right on board RaceCapture/Pro; with Lua you can control RaceCapture's behavior at run-time, no firmware programming required.<br /> <br /> Some Examples:<br /> ** Activate a warning light when an input threshold is exceeded, such as temperature or pressure, or a combination of both<br /> ** Log data at a higher rate when in range of a particular GPS coordinate, or when some other condition is met<br /> ** Auto-start/stop logging based on speed, RPM, or any other condition<br /> ** Experiment with active aerodynamics by adjusting a wing based on GPS velocity<br /> ** Define logic to control an intercooler sprayer<br /> ** Intercept and remap an OEM sensor<br /> ** Activate Smoke screens against your competitors :)<br /> <br /> ===Software Connectivity===<br /> RaceCapture/Pro will feature software to:<br /> * Customize logging channels<br /> * View Runtime Data<br /> * Edit custom scripting<br /> * Perform data analysis and replay<br /> <br /> ===Infinite Possibilities===<br /> * Far more than a data-logging system: flexible Inputs and Outputs coupled with a powerful processor offers endless customization<br /> * Share configurations, tips and ideas with our online community<br /> * '''Fully Open Source System - Open Standards, Open File format''' Frequent software updates and end-user customizable!<br /> * [https://github.com/autosportlabs Source code]<br /> <br /> ==Technical Specifications==<br /> <br /> &lt;font size=&quot;3&quot;&gt;Extreme flexibility comes with a powerful processor and a wealth of inputs and outputs. &lt;/font&gt;<br /> <br /> ===Input and Output Channels===<br /> RaceCapture offers 25 input and output channels, enough to handle complex logging and control tasks.<br /> <br /> * '''7 dedicated 0-5v analog input channels'''<br /> ** Measure sensors or process input from other devices.<br /> <br /> * '''3 dedicated 0-5v frequency input channels'''<br /> ** Measure RPM, wheel speed, or any kind of periodic pulse.<br /> <br /> * '''4 configurable 0-5v analog or frequency output (PWM) channels'''<br /> ** Control other systems or even override OEM sensors<br /> <br /> * '''3 configurable digital channels, settable for input or output'''<br /> ** Receive input from switches or digital signals; or configure as output and use to activate accessories or drive indicator lamps with on-board 1A self-protected mosfets<br /> <br /> * '''4 Axis Accelerometer: 3 channel accelerometer module plus Z-axis gyro (+/- 2G per axis, 3G optional)'''<br /> ** Measure and log 3D G-force in real-time with one of the industry's most accurate accelerometers.<br /> ** Z-axis gyroscope measures yaw/drift in real-time.<br /> <br /> * '''10Hz GPS module input'''<br /> ** Add an external GPS module for course mapping<br /> *** Plot location, speed and time. Onboard detection of start/finish line for automatic lap count and lap time<br /> <br /> * '''Auxiliary Serial Port'''<br /> ** Interface to real time telemetry, bluetooth adapter, dashboard display or other interface<br /> <br /> * '''Digital expansion port'''<br /> ** A high speed port provides the ability to add CAN bus expansion, more analog or digital channels, integrate specialty sensor hardware such as thermocouple amplifiers, and so on<br /> <br /> ===Logging===<br /> * '''SD Memory card slot for data acquisition'''<br /> ** Store up to 32GB of logging data<br /> <br /> ===CPU===<br /> * '''48MHz 32 bit ARM processor'''<br /> ** Enough juice to perform high resolution logging and running complex, user-defined logic<br /> <br /> ===Input/Output Protection===<br /> * '''40v protection''' on all input pins<br /> * Analog outputs protected by '''auto-resettable fuses'''<br /> * Digital outputs are rated at '''1A with self-protected mosfets'''<br /> * '''Over-current protection''' on 5V reference<br /> * '''2A''' internal switching power supply<br /> <br /> ===Mechanical===<br /> * '''Compact, rugged design '''<br /> ** Unit measures approximately 4 x 3 inches (100 x 82 mm) <br /> ** Weighs 8.4oz<br /> ** Real-Time module weighs 7oz<br /> * Easy to use screw terminal block for wiring<br /> * On-board 'action' switch to start/stop logging (or other use)<br /> * On-board Status LEDs<br /> <br /> ===Power===<br /> * 9-17v power<br /> * &lt; 100mA for RaceCapture/Pro. <br /> * May burst to 2A temporarily when using RealTime Telemetry module<br /> <br /> ==Example Sensor Connectivity==<br /> &lt;center&gt;<br /> [[Image:RaceCapturePro_infographic_sensors.jpg]]<br /> <br /> <br /> [[Image:add_to_cart.png|link=http://www.autosportlabs.com/product/racecapturepro/]]<br /> &lt;/center&gt;</div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=File:RCP_MK2_RS232_pinout.png&diff=5746 2014-10-14T13:57:43Z

<p>Jstoezel: </p> <hr /> <div></div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=File:RCP_MK2_CAN_bus_pinout.png&diff=5745 2014-10-14T13:57:28Z

<p>Jstoezel: </p> <hr /> <div></div>

Jstoezel https://wiki.autosportlabs.com/index.php?title=File:RCP_MK2_RS232_pinout.jpg&diff=5744 2014-10-14T13:55:35Z

<p>Jstoezel: </p> <hr /> <div></div>

Jstoezel