May 08, 2007
Attention 4-Cycle Racers!
One cable, RPM and Power
A little known secret to the MyChron4 is it's ability to not only get a perfect RPM signal by connecting directly to a 4-cyle coil, but also to use excess power from the coil to completely power the gauge while the engine is running. This greatly increases the internal 9V battery life since the internal battery is only used for downloading or on screen data review while the engine is not running.
Straight to the Source for Perfect RPM Readings
The perfect RPM signal cannot be overlooked. Oval racers, in particular, know the importance of getting accurate low and high RPM readings. The difference in these two numbers, highlighted by the MyChron4, is critical in getting a good setup — there is no better indicator.
A Secret No More
Perfect RPM's and greatly extended battery life is no longer a secret, it's a $30 cable that plugs into the expansion port of your MyChron4.
Posted by Mike Jaynes at 08:50 PM
Even More ECU Support
Clearly, one of our greatest strengths is our systems' ability to connect directly to your car or motorcycle's ECU — and therefore record and monitor the ECU data in real time. We currently support more ECU's than anyone in our industry, many more! These ECU connection are often as simple as connecting two wires, or sometimes just one. Over this 2-wire connection streams 10, 20, 30, even up to 100 channels of data, good high-speed data. As most of our customers are racers, we have avoided OBDII communication because it's simply not fast enough. Where we have used a connection at the OBDII port, is with some of the OEM protocols; Mazda, Nissan, Audi, VW, Porsche, and BMW. Here, we simply use the OBDII port to gain easy access to the cars CAN-bus, where we can simply "listen" to the messages flying around the vehicles electronic system, and record the channels we are interested in. While we could develop a OBDII system to communicate with nearly every vehicles diagnostic system, the quality and data rate would be compromised.
Posted by Mike Jaynes at 06:36 AM
May 07, 2007
One of the most common tech questions rolling in, is about support for Windows Vista. Officially, Windows Vista is not yet supported. Full support is expected in July, a couple months away. Our DragAnalyzer software seem to be OK running under Vista, though driver installation requires a little more work than in XP. Race Studio 2, on the other hand, is a mixed bag. Most cannot get it successfully installed and running. The DaVid video configuration is surely an issue. Our technicians here will update to Windows Vista about the same time as the Race Studio 2 release. Until then, our support for Windows Vista is VERY limited.
Posted by Mike Jaynes at 11:15 PM
Race Studio 2 Update
Race Studio 2 reached version 2.21.25 today. Here in the USA, this is a combined update of v2.21.24 and .25. This release includes several bug fixes and improvements. It also adds support for four new ECU's; the HydraEMS Nemesis 2 ECU, the stock Nissan 350Z ECU, Marelli Toyota A, and Performance Electronics ECU-1. Continue reading for update details.
Race Studio Configuration
1. On MXL and EVO3 Pro systems, changing the ECU type will maintain the master channels settings
2. Added clock management on MXL / EVO3 Pro systems
3. Added a Shift light signal with threshold management to the available output signal pool
4. Updated Japanese language
5. On MXL and EVO3 Pro systems, in the “Online” window channels are ordered as shown in the Configuration Panel
6. On MXL and EVO3 Pro systems, the “Online” window can be resized
7. Improved data verification while downloading tests
8. Fixed bug – downloading some test can lead to a queued “ghost lap”
9. Fixed bug – Before CAN line identification, sometimes it was necessary to transmit a configuration with no expansion modules connected; lambda probes or David.
10. Fixed bug on maximum allowable frequency on ECU channels
11. Fixed bug on resetting the rpm values to default on David Standalone system
12. Added ECU management: HydraEMS Nemesis
13. Added ECU management: Nissan 350Z
14. Returned 100hz channels sampling frequency is available (on Mazda MX5 ECU)
15. Added ECU management: Marelli Toyota_A for EVO3 Pro
16. Added ECU management: Performance Electronics PE-ECU_1
Race Studio Analysis
1. In the Laps history bar, disabled laps are hidden in “snap on” mode
2. Fixed bug on calculating split times in the split time window
3. Fixed bug that could generate a software crash while opening or closing a .drk file keeping the engine analysis window open
4. Fixed bug in XY graph profiles management
5. Fixed software/firmware version string in the advanced info test window
6. Added a new algorythm to realign GPS data
7. Fixed indexing procedure and export of XML (Google KML) files
8. Improved filters management in Channels Optimization
9. Fixed bug on final time calculation in Time Compare function
10. Fixed cursor misalignment between map and time plot while zoomed
Posted by Mike Jaynes at 06:00 PM