NEW Windows 64 bit AJP Diagnostic Software

[Dalamar]

I ended up trying the following: DSD Tech SH-B35

Amazon Link

But no joy either. I set it up to be a data stream to COM5 on my PC and MBE Tools saw it as an active port but no connection. Using AJP Diagnostics it didn't recognise the port and scanned past. I used the DSD Bluetooth set up tool to ensure all was working and that the baud rate was correct and a simple send/receive worked. I also used Putty to check the COM port received data.

Must be something simple and just trying to understand what the difference is between plugging in a serial to PL2303 chipset USB converter and these serial RS232 to Bluetooth adapters.

I just don't know enough about these communications protocols and interested to hear how you get on.

[jeremyc]

Do the RS232 to Bluetooth adaptors generate/detect valid RS232 signal voltages? It may be that the MBE is less tolerant of lower voltage signals.

Texas Instruments RS-232 FAQ said:

Valid RS-232 signals are either in the range of +3V to +15V or the range -3V to -15V with respect to the common ground (Figure 1-1). To be more specific, the driver output is Logic 0 when the voltage is between +5V and +15V and is Logic 1 when the voltage is between -5V to -15V.

[Juddder]

Dalamar said:

When using the 3-pin connector, is the connection made to the ECU in Byte mode or Broadcast? Just wondering if I need to faff around with resistors and plug directly into the ECU mainboard or just use my current adapter cable.

@dalamar In the Sticky Pages at the top is a complete guide to building your own 3 pin cable connector - you don't need any of the resistors etc. just GND, RX and TX

https://www.pistonheads.com/gassing/topic.asp?h=0&...

HTH

[Juddder]

Dalamar said:

Using AJP Diagnostics it didn't recognise the port and scanned past.

From Aide himself who wrote RS-AJP

There is no Bluetooth support in the app.

Wired serial connectivity via RS-232.

That's why I called it RS-AJP :smile:

[notaping]

VERSION 2 NOW AVAILABLE FOR DOWNLOAD - links in first post. ****

https://www.pistonheads.com/gassing/topic.asp?h=0&...

NB. If you have stored Adaptive data that you want to keep - backup the files Adaptives_Odd.dat & Adaptives_Even.dat in the AppData\Local\KCC\AJPDiagnostics folder. Restore them after the install.



. . . and you can now play with your own colours . . .



Enjoy!

Merry Xmas

[Byker28i]

Nice work sir, will grab a copy and try it sometime

Ah link not working - did you make it available for 1 hour?


Sorry, something went wrong
The access token has expired. It's valid from '12/5/2024 2:41:58 PM' and to '12/5/2024 3:41:58 PM'.
Technical Details

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: 279e6aa1-10d6-7000-2632-fa1bdcdb31dc

Date and Time: 12/5/2024 8:44:44 AM

[notaping]

Ok. Was trying to include direct download links, but Microsoft and OneDrive make it impossible.

Page links now updated.

G.

[Byker28i]

64bit link - no download - click the button does nothing


x86 downloads ok

[notaping]

Ok. I'll get there. Think that's it now.

[Byker28i]

Yup 64 bit downloads now - thanks.

[Modrich]

Thanks very much notaping this has proved very useful. Last time I used it I struggled to correctly change which com port it looks for, it seemed to keep changing each time I opened it, or defaulting. Is there a 'how to' guide for this that I'm missing?

[notaping]

Hi Modrich, It's the Windows operating system that assigns a COM port number and not the diagnostic software, that just lets you know which one Windows has assigned.

It won't make any difference so long as the application's connecting ok. There could be many reason that the number changes - using a different USB port, plugging another device into the same USB port that uses COM etc.

The connection logic hasn't changed in this version - so, if the last version worked, this version will as well. Cheers.

[Modrich]

sorry notaping I wasn't clear. I have the USB device set to com5 in device manager but AJP Diag. only looks at com3 & 4 then says device not connected, how do I change to com5 in your softare? I thought I'd manged to change this in the AJP settings but it has gone back to 3&4 again.

[notaping]

Hi Modrich, You were perfectly clear - let me explain how the application works . . .

When you plug device into a USB port, even without the application running, Windows assigns a COM number to it and if the device is recognized as a plug and play device - it is added to Windows PNP list.

When the software starts - it asks Windows for all entries in the PNP list and then tries to connect to each one, looking for a response that indicates it is the MBE. This is where you see "Searching for device . . . COM1" etc. If, as in your case, no attempt is made on COM5 - it is because Windows has not added COM5 to the PNP list. It can still appear in the Device Manager, but that does not mean it's recognized as a PNP device.

You can add a default COM port number in the application config file, but I'm fairly sure that will still not work since the communication library used in the code will still expect the selected port to be connected to a PNP device.

The only suggestion I have is to unplug the serial to USB converter, go to Device Manager and delete all COM devices, reboot Windows, and then plug the serial to USB device in again (perhaps in a different USB socket) and let Windows find the device. When Windows finds the device it should display a message stating "New device ... bla, bla" with the name or type of device. If it doesn't recognize the device the message will be something like - "Unrecognized device".

Hope that helps.

I might also ask those in the forum who have tried the new software if they have had any problems connecting?

Cheers

Gordon

[Car.Fool.James]

Hi,

I have just tried with my 98 4.5 cerb tonight as its smelling rather rich, as i drive adaptive hovering round -15 one one and +10 on the other. Borderline to wanting some faffing with throttle pot positions perhaps...

Anyway, i did have the original ish version downloaded, but on trying to connect it refused. Suspecting the update to windows 11 from 10 over Xmas to be the cause, downloaded your new version. Still the same, searching com5 and 6 then cant connect no matter the order or plugging unplugging etc. Head scratch or so later, looking in driver settings Com 5 and 6 are Bluetooth... im using a usb... so turned off the laptops bluetooth, retry, perfect! Working great. So, having bluetooth on is upsetting it.
FYI, Com 5 and 6 were the bluetooth ones, and Com 7 was the usb ports, but when connecting it would only say connecting to 5 and 6 at first, then strait to NO. no attempt to connect to Com 7. After turning off bluetooth it went strait to searching Com7 and strait away connected.

[notaping]

Glad you got it working.

Good info for others who are perhaps struggling to connect - Switch off Bluetooth.

[Modrich]

The laptop i was struggling with has bluetooth enabled, cheers guys

[Byker28i]

Have we got a new recommended source for the USB to serial that works with an android phone. One I have works with the laptop, not phone, the other burnt out in about 5 secs of being plugged in with the laptop and car, which was worrying.

Quite like having the phone app available to fault find if out and about. It's how I tracked down the dirty plug on the temp sender causing possible missfire and certainly the fans not coming on.

[notaping]

Don't know what's recommended for RSAJP on the phone, but you can go out for a run and log data on this app.

Interesting you found a fault with the temp sensor which caused a misfire. I found a problem with rough idle when hot and traced it back to a drop in voltage when the fans come on. The log shows it dropping down to 10.9v - I'll fix that in the next couple of weeks during spring service. Either dirty fan connectors or old fans drawing too much current.

[Byker28i]

I've had a random misfire for a while. It's usually fine, then sometimes a misfire under load...which then clears.

I found the water temp sender plug etc dirty, causing under reading, or changing values of the temp to the ECU, hence my fans sometimes wouldn't come on in traffic, when the car was hot etc. Since cleaning them I've not had the misfire so my thought is the ECU was confused?

I was seeing 60 and below, sometime flicking to 40, then back up, when the car was really at 100 according to the mechanical temp gauge