pengaru_e6dash_spyshot.avi: This is a video taken of a development version of e6dash, NOT FINAL, running on Seva's Mazda RX-7 TurboII with a Haltech E6K. Seva is holding the camera, I am the one going in and out of the car, mumbling to Seva, sounding like a dork on the video. The computer hardware used to run the software is a old Compaq Armada 1120 pentium 100 laptop. The resolution being used is 800x600 so the laptop is struggling to keep up with things, the gauges are not so laggy on a faster machine that can handle the relatively high resolution easily. E6dash has native support for the Haltech E6K ECU (E6X support is partial at this time), and the TechEdge 2A0 wideband o2. In the video, there is no TechEdge controller connected, so you don't get to see valid Fuel level (uses aux input on the TechEdge) or O2 levels. In the beginning of the video, the software is in 2D map editing, on the base fuel map, in 'follow mode'. Follow mode causes the program to 'follow' the engines rpm range for you (like holding down the HOME key in the dos software). When follow mode is enabled, there is a small icon in the upper left corner visible, which is two arrows chasing one another. After Seva presses the F key, follow mode is toggled (off), and you get to see the arrows indicating the load cell being used stack on one another as the engine RPM goes further and further away from the current range being edited/displayed. The edited/displayed range doesnt change automatically anymore. This feature helps recognize when you are editing a range that is neighboring the current range, as the ECU interpolates between the ranges this is a useful thing to have visual help with. The arrows point up when the engine RPM is in a range above the current one, and point down when the engine RPM is below the current range. For every range between the current one and the engine RPM there is another arrow, so the height of the arrow stack tells you how far off the engine RPM is intuitively. When the range you are editing IS the range the engine RPM is in, the load cell arrow appears above the current bar/column, pointing down at the 'bar' representing the current cell. The numbers on the screen in the middle/left are bar: inj ms, since Seva is not moving the selection around or manipulating it in any way, it stays at "0 : 0.992", for bar 0, 0.922 inj ms. You can tell if you look closely at the video that the first bar, the one at the far left, is kindof whitish. That is because that bar is selected, a checker pattern is drawn over the selected bar so the overall color of the bar is still visible but the bar is given a white hue due to the checkered highlighting. It is hard to see in the video though, the tube monitor is not cooperating with the recording. On the top of the screen is the name of the map being edited, in this case, "Fuel". Seva never changes the map, you can tell this video was not really planned. All the maps are available for editing in this interface. He only had to hit to cycle through all the maps in the ECU, he didnt know that though ;). Below the map name is the current 'row', which is only present in 3D maps, which so far are just the fuel, ignition, and rotary split ignition maps. The rest are 2D maps (temperature correction, wastegate 1/2, etc..), which are displayed similarly but lack the 'row' label (theres only one) and don't have follow mode available (useless in a single row map). Also, while editing the maps in 2d mode, there is a horizontal "bar" gauge on the bottom of the screen. It spans the whole width of the screen, where it says WbO2: 1129 or Wb02: -40. Since Seva's car does not have a TechEdge 2A0 wide band O2 controller, this gauge is basically broken in the video. When the TechEdge is present, you have a solid colored bar representing the wbo2 voltage from 0-5v (if my memory serves me right, was it 0-4v? whatever) and it will also display the voltage numerically after the WbO2: This is pretty handy while tuning, I will be adding the AFR display to this gauge also, so you won't have to understand the voltage. After demonstrating the map editing, we hit the key and go to the driving gauges page. These driving gauges are for my car, the final version will not have the 1st/2nd/3rd/4th/5th numbers, this was a workaround to get me on the road. I had no road speed sensor, and no other speedo. So I added code to calculate the road speeds in all the gears and display them all at all times, using the engine RPM, gear ratios, and tire circumference to do it. As long as I knew what gear I was in, I knew how fast I was going. The gauges display is pretty unflattering, the laptop we used is too slow to render them fast enough, but you get the idea. Seva's car also had it's IAT disconnected, so the IAT gauge shows -40, if the sensor is connected the IAT gauge functions fine. Like I stated before, he also has no TechEdge, so the A/F and Fuel gauges are dead. Add the TechEdge and they are functional, the Fuel level gauge uses one of the extra inputs on the TechEdge, you must wire the sender into the TechEdge for it to work properly. The TechEdge actually has 3 extra inputs, so one could add things like oil pressure, fuel pressure, or extra temp sensors through these inputs and have gauges for them. In the final release, the gauges display will be easily customizable, by editing a text file that looks kindof like HTML for those of you who have experience editing web pages. So you can move around the gauges, add new ones, remove ones you don't want, change the fonts, sizes etc. Thats the plan anyways. That basically concludes this "spy shot" of the e6dash software I have been developing. I will be shooting a better planned video of a newer version of the software, running on my car, with the TechEdge connected, a faster laptop, and 7" LCD panel installed in the stock gauge cluster location, in the near future. Check the web site forums, I will surely announce it's release there. mvi*.avi: These show a development version of e6dash running on my NA FC3S RX-7. The gauge visible on the bottom of the screen is a horizontal bar gauge showing the voltage from a TechEdge 2A0 WBO2 controller. The map editing is in 2d follow mode, meaning the software follows the engines rpm range automatically while the wideband a/f is visible in realtime. The laptop being used is a p100 compaq armada 1120 laptop with a active matrix display, in 640x480. Basically everything is the same as the above described movie, but it's on a different car, has a TechEdge WBo2 connected, and is being displayed in a lower resolution directly on the armada's junk active matrix LCD screen.