944 OBD Project (On-Board Diagnostics)
#16
Wow. Thanks for all your efforts. I suspect this will prove a valuable addition to the DME
As for your initial post's question, of all the optional sensors on top of the basic "Internal Sensors", I vote:
Reference + RPM sensors waveforms
TPS
MAP
As for your initial post's question, of all the optional sensors on top of the basic "Internal Sensors", I vote:
Reference + RPM sensors waveforms
TPS
MAP
The following users liked this post:
Tiger03447 (04-21-2022)
#17
Very interesting. What's the reason for going with an external Bluetooth adapter, rather than incorporating one onto the OBD Module board (and presumably routing an antenna through the case)?
The following users liked this post:
Tiger03447 (04-21-2022)
#19
There are actually several reasons I decided to make the Bluetooth an option rather than integrating it:
Cost – Not everyone will want or use the feature.
Time to market – I don’t need to select the Bluetooth module at this point in development. It will actually take some time to test several options and get the best peformance.
Upgradeability – I can change the Bluetooth adapter with the latest version of what ever wireless technology exists in the future.
Cost – Not everyone will want or use the feature.
Time to market – I don’t need to select the Bluetooth module at this point in development. It will actually take some time to test several options and get the best peformance.
Upgradeability – I can change the Bluetooth adapter with the latest version of what ever wireless technology exists in the future.
Last edited by Ftech9; 03-25-2019 at 11:57 PM.
#20
968 DME Support
#22
Creating a DME for the next Generation of BOSCH Motronic computers has long been on my development list ... However, it is huge development effort ... huge expense ... Once I take the ML3.1 Motronic platform as far as I can go ...l port all of my technology to the ML4.x Motronic.
#23
My first post goes into specifics, but here are the main objectives for the custom Windows software I will create:
- Intuitive/Easy to use
- Tablet/Touchscreen Friendly
- Simple DVR Style Data-logging
- “Select your sensors then select record”
- Free Software, share and play back Data-logs with the 944/911(3.2L) community.
- Read Live Engine Data
- Graph Live Engine Data
- Self-Diagnostics
- Flywheel Sensors
- Oxygen Sensor
- Injectors
- Ignition
#24
OK, I'm most interested in the self-diagnosis part. In your previous posts you mentioned that your hardware will not support error codes - how to understand "self diagnostic" then? Just a simple check for open loop or short circuit?
Last but not least - will it be compatible with Rogue DME or it is a whole different animal?
Last but not least - will it be compatible with Rogue DME or it is a whole different animal?
#25
My first post goes into specifics, but here are the main objectives for the custom Windows software I will create:
- Intuitive/Easy to use
- Tablet/Touchscreen Friendly
- Simple DVR Style Data-logging
- “Select your sensors then select record”
- Free Software, share and play back Data-logs with the 944/911(3.2L) community.
- Read Live Engine Data
- Graph Live Engine Data
- Self-Diagnostics
- Flywheel Sensors
- Oxygen Sensor
- Injectors
- Ignition
#26
Self Diagnosis
OK, I'm most interested in the self-diagnosis part. In your previous posts you mentioned that your hardware will not support error codes - how to understand "self diagnostic" then? Just a simple check for open loop or short circuit?
Last but not least - will it be compatible with Rogue DME or it is a whole different animal?
Last but not least - will it be compatible with Rogue DME or it is a whole different animal?
For example, there are two flywheel sensors on a 944/911 (3.2L). One reads each and every tooth on the starter ring and the other reads a maker at top dead center (TDC). The when the OBD module reads the TDC marker it will start counting the number of flywheel teeth. When the OBD module reads TDC again it will expect that count to be exactly the number of physical teeth on the starter ring. If the count is higher or lower, then the sensor failed to read properly one or more times. The same logic also works in reverse. If the tooth count is higher than the physical number of teeth on the starter ring, TDC Sensor failed to read properly.
If ether of the above failures happens, I would highlight the sensor on the GUI and increment an error count. If bad wiring is suspected, you could shake the sensors harness/connector and see how that changes the frequency of errors.
The Rogue Tuning DME is a close “cousin” of my standard DME. I will create a version that is compatible with it. The main issue is getting access to the switches which would be covered the this version of the OBD Module.
#27
iOS Android Support
I completely agree. However, while I have strong skills developing firmware, electronics and Windows applications, I will need to learn a cross platform skillset using Xamerian. Basically, this will allow me to use the same base code for Android, iOS and Windows platforms. But this also means Windows will come first because I am already comfortable writing code on this platform.
#28
I completely agree. However, while I have strong skills developing firmware, electronics and Windows applications, I will need to learn a cross platform skillset using Xamerian. Basically, this will allow me to use the same base code for Android, iOS and Windows platforms. But this also means Windows will come first because I am already comfortable writing code on this platform.
Btw that new DME is working Beautifully
Dwayne
#30
Rogue DME Support
The OBD Module Prototype in the pictures above could plug directly into a Rogue Tuning DME and basically work. However, the Rogue Tuning DME has a different injection driver and several switches. I will need to create a slightly different design to read the injection current waveform and provide access to these switches.