When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Yes, definitely. However it is looking like early to mid February for a new batch. I am building a lot more of them this time around, hopefully I can keep them in stock for a while.
Absolutely, a new DME for 16v engines (ML4.x) used in 944, 968 and 964 is on my project road map. Naturally, it would inherit the OBD functionality. However, because it is a huge investment of capitol and time I need to finish a few smaller projects first to finance it.
Absolutely, a new DME for 16v engines (ML4.x) used in 944, 968 and 964 is on my project road map. Naturally, it would inherit the OBD functionality. However, because it is a huge investment of capitol and time I need to finish a few smaller projects first to finance it.
Plenty to cover on this update, but the main announcement is I am now able to read out analog and digital sensors to a custom Windows application. This is a huge milestone. It means the basic structure for all the core features is in place and working.
FocusOBD Application
The screenshot below shows live sensor data being read out of my 1985.5 944 NA. At the moment, I am only reading 6 of 14 analog sensors and 1 of 11 digital sensors the OBD Module supports. This is the “Data Grid” and the most basic display of sensor data that will be available. Most of sensors are being read “raw” meaning they are displayed as their native 0 to 5 volt range. Sensors that read temperature and airflow will take some work to display as accurately scaled values of degrees and CFM. Once I implement reading out all the basic sensors as the scaled values, I will focus on more interesting and useful displays. This includes Graphing and Virtual Gauges plus more specialized software tools like Flywheel Sensor Diagnosis and Idle Speed Valve Adjustment.
Also, I haven’t forgot about iOS and Android, I should be able to use up to 80% of the code for the FocusOBD Application towards mobile/tablet apps. Once the Windows application is finished iOS and Android will not be far behind.
OBD Module Mark III
This is the third prototype OBD Module, and mark IV on the drawing board. The first significant change to this version is the board outline that was updated to provide enough room for your finger to adjust the configuration switches. Second, it has support for “Virtual” FQS adjustment. This will allow you to check and change the FQS setting from the FocusOBD Application. However, it will still allow you to adjust the mechanical FQS switch. Which ever you adjusted last, mechanical or virtual, will be the current setting. The FQS setting displayed in the Data Grid is the current setting, whether it was configured mechanically or virtually.
is there enough clearance between the dme lid and obd module? Most popular maf conversions have a taller mini chip board that replaces the 24/28 pin dme chip.
which also raises the question will maf conversions still work with the obd board? I currently use vmaf+ from vitesse racing with a ftech9 944 turbo dme and it works perfectly.
also,
The map sensor input to the obd data display should probably have an option for reading from the harness or from any other provisions you've added to the obd board. All map sensor inputs I've seen wired to the harness use dme pin #28 for map signal input. That way either can be used to get the map input signal.
Last edited by mahoney944; 02-10-2020 at 05:45 AM.
Enough Space for MAF Chipboards?
Yes, absolutely! There is more than enough clearance for a performance Chipboard. Even with the additional spacer socket needed to clear the 40pin microcontroller, the height of the chipboard is level with the black heat-sink protruding from the SPORT DME. The heat-sink still has clearance to the enclosure lid, so there is plenty of margin.
Do MAF conversion still work with the OBD Module?
Yes, absolutely! Any Performance chip or chipboard that works with the factory BOSCH DME will work with the F9T DME /w OBDModule. The OBDModule is a passive systems that does not interfere with normal DME functions.
MAP Sensor Support
By convention, the unused analog input on pin 28 (ADV28) of the DME system connector is used as a MAP sensor input. I will follow this convention and default this input for that purpose.
This most definitely won't be an "add on" to your F9T DME upgrades, correct? I'd really like the capability given I'm planning on E85 and my own tune for the new build this spring. I haven't enven taken the DME you did for me out of the shipping box yet.
This most definitely won't be an "add on" to your F9T DME upgrades, correct? I'd really like the capability given I'm planning on E85 and my own tune for the new build this spring. I haven't enven taken the DME you did for me out of the shipping box yet.
This upgrade will be available for every Focus 9 Technology and Rogue Tuning DME ever made. There are 5 generations of DMEs I have designed over the years, the OBD Module pictured in this thread will work on my last 3 generations (SPORT and STD 3.x & 4.x). Once I have finished the OBD Module for SPORT and STD 3.x & 4.x, I will adapt the design to support the earlier 2 generations. The main difference from the OBD Module standpoint is the injector driver is different, and the Rogue Tuning DME has more configuration switches that I will need to allow access to. It will not take very long to make these changes.
For this update I added support for a 3Bar MAP sensor. I also posted a video on YouTube of the FocusOBD Application reading out sensors from a SPORT DME. You can see the sensors change as I rev the engine on a stock 944 NA.
It was easy enough to add the MAP sensor, mostly for this update I have been concentrating on improving how fast the system reads sensors. Note at the bottom of the application I added a “PID” counter that calculates sensor updates per second. For the Windows Tablet used in this video, I am capturing between 1800 to 2000 sensor reads per second! For comparison, the fastest you can read sensors from the OBDII port of any modern car is only 200. I think I can say with reasonable confidence that I have the fastest OBD system in existence bar none.
If I let each sensor update at the full 271 times per second, it would be too fast for the human eye and just look like a blur. Because of this, I am averaging 25 updates for each sensor before I display it in the application. In this case, you are seeing about 11 updates a second for each sensor, but I will make this fully adjustable to your preference.
01-15-2020, 04:59 PM
