What protocol do people want added next?

Current Status:

LinkECU:
Still waiting for there responce, last message was "Its going to the higher ups", Will phone call again end of next week.

Neptune:
Looks like they wont allow support if I have any other Honda tuning supported. Reverse engineering protocol be slow going.

CAN:
Have Adapter on its way as well an EGT to CAN ecumaster node thanks to "MjPower" on its way.
(ScanTool will only have basic read function, CANTool will have full control and support for CAN supporting aftermarket ECUs)

Holden/GM ALDL: Need hardware
Have all info on protocol for 85-98

Nissan Consult: Need hardware
Have all info on protocol for 90-96

Subaru OBD1: Need more research

Ok, yes, i think usb scan Will Works better than bluetooth one. i follow your YouTube channel. your work is amazing!

Posted by: Walter

what OBD2 scan are you using?

Chinese 1.5 works but slow.
Genuine 2.2 works full speed that cars ecu supports.
For example, 2002 Silverado Chinese scan tool will start having problems around 300ms. Genuine 2.2 scan tool will run at 180ms.
2013 Mazda, Chinese scan tool 300ms, Genuine 2.2 90ms.
Using a USB cabled scan tool, Blue tooth one you have to run even slower.
And the way it polls each sensor 1 at a time can mean logging gets really slow when every sensor logged.
Im in the middle of changing code so first 2 sensors on the list refresh twice as fast as the rest. And if its a ECT or IAT sensor then it refresh twice as slow as the rest since its a slow changing sensor anyway.

--------
And another demo video.
Line graph on multi-monitor.
https://www.youtube.com/watch?v=_T7vtDk4LC4

what OBD2 scan are you using?

Update #A13:

Changes to graph UI, (Line will not go above top of table anymore, Improved look of Max and Current value, Added label on graph.)
All protocols validated working on running cars.
Plugin changed from dialog to form. (will allow YourDyno to still be controlled with plugin still on screen. So line graph could be run on a 2nd screen or in corner of screen)
Bug fix to error report not working with ISR protocol.
PIDs can be added or removed with double click

**Wanted to get this version out since will be making a big change to sensor polling in OBD2 and QD2 in next build so it prioritize fast changing sensors, Such as RPM which can be a bit slow as seen in my video. Ill need to validate those protocols again on a running car afterwards.**

Known Bugs:
Live Data Max value not working with out clicking reset first.
QD2 injector duration formular wrong.
Spelling Mistakes.

Demo Video:
https://www.youtube.com/watch?v=G3ILAHj2r5M

Update #A12:

QD2 optimised so sensors with slower changes are refreshed less. (Need to validate no issues in real life usage *Tomorrow)
ISR Datalogging protocol added eCtune/BMTune (Need to validate on real ecu *Tomorrow)
UI changes (Form size changed to 1024X762, Live Graph tab added, Controlls moved and resized)
Line Graph (Logs any of the loggable sensors and dyno readings in 1 of 4 line graphs)
*To Do, Change from dialog to form so rest of YourDyno windows still work with ScanTool on a 2nd screen*

Update #A11:

Last of the DAT core conversion completed. (All text strings are stored with in it now. So re-writing different lanugage support can be done by anyone once I explain how to.)
3KB file size reduction (Dont expect any more size reductions since there is nothing left thats compressable)
QD2 Code tested in real life usage under Build A10, (Only issue is Inj calucations will need to try work them out since the INJHigh always returns 0 and its using RPM for some kind of multiplyer)
QD2 Code optimised datalogging calls to exclude infomation not useful (Will need to test again in real life usage but should improve responce by 30ms since its not polling sensors that arnt dyno logged, Auto gear stuff, ELD, Gear, AC and so on.)
Minor bug fixes to UI error catches that I found while finishing the Language call stuff.
Started writing ECU Sim for eCtune datalogging to finish dissecting its protocol. (Since for each supported protocol I need to validate each build against known values)
Decided to exclude CAN from this plugin, will start a seperate plugin as CANTool for it (Since some one might want to log a ECUs datalogging while using CAN EGT or Knock sensor, Which would get messy with in a single plugin.)

Update #A10:
QD2 code added.

QD2 start, idle and shut off with Error 20 present serial data capture to review tonight and add support for.

Update #A9:
Fixed port listbox issues.
Keep Alive code removed from OBD2 protocols temporally. (Need to add it back to just ELM 1.0 and ELM 2.2 controllers since Chinese ones are too unpredictable)
Disabled ECU brick protection. (only really needed for flashing anyway so will limit it to just that set of commands)
Auto refresh delay code changed. (Each buffer overflow will slow the refresh rate down by 50ms.)
Fixed Error code list issues.
UI Change to Live Data tab. (PIDs can be added or removed by using enter key and arrows instead of pressing button and using mouse)
Found issue with VPW code. (Not tested yet) (Looking at the serial log first attempt it uses AT@1 sub timings. 2nd attempt AT@1 is set to AT@1.5 automatically by ELM controller, 3rd Attempt AT@2 is set automatically, Changed code so if it reads "ECU Unavaliable" it will try AT@2 and restart connection its self)

[Bug testing and bug list]
After a day of testing,
10 OBD2 adapter 8 different OBD2 cars.
3 Serial TTL adapters, 2 QD3 Hondas.
Here is my findings.

QD3
works perfectly on all 3 serial adapters and is 100% production use ready.
Hulog (prefered adapter, 20 updates a seconds no packet loss or check sum failures)
Generic ftdi adapter (2nd perfered adapter type, 10 updates a second no packet loss or check sum failure.)
Chinese pl2303 adapter (Not perfered adapter type, 10 updates a second no packet loss, 2 check sum failures over 15mins of logging)

OBD2 ELM
ISO9412 Works. (Need adjustment to Keep alive code since can cause buffer overflow when logging at full speed)
ISO14230 Works (Found no faults)
SAEJ1850 VPW (Connection difficulties, Takes 2-3 attemps to connect.)*Have serial log to review*

ELM 2.2 (Genuine) Works perfectly, 100-10 updates a seconds depending on ECU.
ELM 2.1 (Chinese fake) Has buffer overflow errors going any faster then 8 updates a second.
ELM 2.0 (Chinese fake) Has buffer overflow errors going any faster then 8 updates a second.
ELM 1.8 (Chinese fake) Has buffer overflow errors going any faster then 5 updates a second.
ELM 1.4/1.5 (Chinese Clone) Works 10-4 updates a second depending on ECU.
Bluetooth (Same as ELM 1.4/1.5) (Samples are 20ms delayed from bluetooth protocol)
Wifi (Same ELM 1.4/1.5 internal chip) Couldnt get it to connect as wifi serial port, Drives keept only showing as a UPNP device.
ELM 1.3 (Chinese Clone) Works up to 4 updates a second.
ELM 1.0 (Genuine) Works 10-4 updates a second depending on ECU. (Expected since its what ELM 1.4 and 1.5 is a clone of)

[Found Bugs]
Serial port list keeps adding same port number to its self each time the window is opened.
VPW code needs work.
Keep alive code should be disabled for Chinese adapters since it just adds more stress on a device thats already below whats recommended hardware wise.
Auto refresh rate delay needs more work and adjust ECU Brick protection to allow for more errors before it disconnects.
Error code list doesnt work if switching between QD3 and ELM in listbox with out restarting plugin.

Attaching serial capture data from SAE J1850 VPW OBD2 Commadore to analyze add support for while at home since dont have usb stick on me and my email only supports attachments of less then 1MB.

--- Note ---
Bug in port combo box doubling up port number to be fixed.

Posted by: Walter

Great! i Will try to test next time on dyno! ECtune and Neptune use QD3 too if used ostrich?

QD3 = Crome Gold only, (By far the fastest protocol since everything is sent in 1 packet, All the rest take a packet per sensor your logging like obd2.)
QD2 = Stock maps with datalogging plugin added (Crome free/pro, Uberdata, TunerPro)
ECD = ECTune and BMTune (Will be adding this protocol after QD2 since its basically QD2 with some location changes which BMTune dev has shared)
NTD = Neptune (Wont be adding since dev refuses to share any info on sensor locations)

Great! i Will try to test next time on dyno! ECtune and Neptune use QD3 too if used ostrich?

Update #A8:
QD3 Code 100% Complete
QD3 Added gauges for Battery voltage, Injector ms, Injector duty cycle % , Knock retard degree.
QD3 Print report button enabled.
OBD2 Added logging of Battery voltage.
OBD2 Change to keep alive code (some ecus dont support keep alive so instead on those ones it just polls voltage. 0V = lost connection lol)
Moved Report HTML template to the compressed DAT (Using a external DAT will allow for custom Error report screens.)
GUI changes improvements.
Lots of back end bug catches.
Another file size reduction of 32kb due to moving stuff into the compressed DAT.