NEW Windows 64 bit AJP Diagnostic Software

[notaping]

Looks good Juddder, and it's correctly identified the MBE as a Sp6 unit.

Wish I'd had that test rig when developing. Instead I wrote an MBE emulator in partnership with the app and linked them using com0com. A lot of learning on this project

[Juddder]

notaping said:

Looks good Juddder, and it's correctly identified the MBE as a Sp6 unit.

An interesting mistake I made when I got it is that I, incorrectly it now turns out, assumed that the ECU would be able to run the V8 EPROM as well as the SP6 EPROM.

After failing to get any version of the MBE software to get any response from the ECU (while having V8 ROMs installed) I as a last ditch effort switched back in the original SP6 ROM and the whole thing fired right up. One to watch for others playing with these in the future

notaping said:

Wish I'd had that test rig when developing. Instead I wrote an MBE emulator in partnership with the app and linked them using com0com. A lot of learning on this project

Sounds like it and the ECU is yours to borrow any time you might need it - although seeing as you wrote your own ECU emulator (hat's off!) I think you are way past that stage now

[Juddder]

BTW I doubt this will be on interest to many, but I did spy a spare Tuscan ECU on eBay that could be used with a SP6 engine I would think and / or testing

[classic105]

hi Judder,

I have a TVR Cerbera V8 4.5 i have wanted to try your AJP Diagnostic software on a windows 10 64b Version 22H2 and when it loads i have this screen that appear (see picture join below).

after i click ok, the only values displayed are the fault codes , baro pressure, rpm: 0 . rad fan 1 and 2, fuel pump off.
when i depress the gas pedal, some fault code status switched (don't remember which ones)
My MBE seems connected with the serial number displayed in green.

surely i have done something wrong but what?
i have try all the usb port.
it seems i run it on administrator mode.

Many thanks for your work and your help.

Best regards

[notaping]

Hi classic105.

I think this problem was reported once before. The software is initiated by reading comma separated config files. I believe you're located in France - in which case your decimal separator is a comma. This creates problems when trying to parse the config files.

Changing the locale of your PC to the UK should fix the problem. Not ideal I know, but not something I considered when writing the software.

Cheers.

[classic105]

i just try and always the same, below are the setting i have made.

thanks

[notaping]

Hi,

If you look at "Additional date, time & regional settings" --> "Change date, time or number formats" --> "Additional Settings" and check the number format. If it all looks ok - then I can only suggest a re-boot, so windows picks up the settings.

[classic105]

Hi judder, you are right, i'm amazed by your knowledge, stunning help.

i apply your specs and all is good, i'm very happy.

here a picture with the ignition on and engine not running.

Many thanks

Best regards.

[notaping]

Great news classic105.

PS. I'm NOT Juddder - but all's good

[classic105]

very sorry notaping, i'm confused.

[Byker28i]

Picked up an old surface pro tablet, Windows 10, works a treat, huge screen compared to using my phone.

Handy for workshop,home use.

[notaping]

That's great. Large screen, home use etc - that was my initial goal, but that was when I was using my laptop. Now with a tablet, I have it running every journey (day trips). The benefit there is that if a problem develops (and let's face it - they usually do) - you have a before and after recording of the engine. It makes diagnosing the problem a lot easier.

If you've been using your phone via a bluetooth adapter, there's a possibility it might work with the app. When you've paired the adapter with the tablet - go into "More Bluetooth Options" --> "COM Ports" and Add a virtual pair of ports for the bluetooth device. The app should pick up the outgoing port and connect as normal. Note - I've been unable to test this as I don't have a working bluetooth adapter, but according to all the bumf online - this should work.



G.

[Byker28i]

I have a usb to serial I've used since day 1, on an old XP laptop and the original software so just plugged that in. I might get a bluetooth one and try it.

[notaping]

If you're going for a bluetooth device - Windows won't create virtual COM ports for BLE devices. You need the older Bluetooth adapters.

The adapter I got was S2B5232E - as listed on RS-AJP site. This turns out to be a BLE device and while it obviously works using bluetooth (GATT) protocols, I can't communicate using old serial port protocols - which is what is written into the app. To communicate via BLE requires a bit of a re-write.

[Luckyone]

notaping said:

Glad it's of use. It's now got touch screen capabilities. Latest version ...

32bit & 64bit installers

AJPDiagnostics_x86.msi - https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...

AJPDiagnostics_x64.msi - https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...

Optimized for a windows tablet (but still runs fine on a laptop) - I've moved the menu from a top bar to a tab (middle left) which open a menu screen. Bigger buttons for fat fingers Also, gains a bit of headroom on the screens. Oh - and it has swipe left / right to move between screens (of limited use).

I'm guessing that should be x32.msi on your links there rather than x86.msi?

I wanted the 64bit version anyway so downloaded that & it's working nicely. I had been getting on fine with your last version (I realised I needed to at least have the cats bolted to the down pipes or the Lambdas can't work as they get far too much fresh air). The adaptives were displaying & staying there fine after that.

I just tried your last version again but it seemed to stop finding my virtual com port 7. Then looking on here I found you had the fix in the new version ready & waiting for me.

Thanks very much again

[camel_landy]

notaping said:

Glad it's of use. It's now got touch screen capabilities. Latest version ...

32bit & 64bit installers

AJPDiagnostics_x86.msi - https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...

AJPDiagnostics_x64.msi - https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...

Optimized for a windows tablet (but still runs fine on a laptop) - I've moved the menu from a top bar to a tab (middle left) which open a menu screen. Bigger buttons for fat fingers Also, gains a bit of headroom on the screens. Oh - and it has swipe left / right to move between screens (of limited use).

Nice...

BTW - For belt & braces on the downloads, any chance you can publish what the SHA256 (and/or other) hash is?

Cheers,

M

[notaping]

Luckyone said:

I'm guessing that should be x32.msi on your links there rather than x86.msi?

Luckyone - Don't start on the illogical naming conventions of Microsoft , however - x86 refers to the processor architecture of the time. More info here . . .

https://you.com/search?q=%20%20%20%20%20why%20is%2...

Glad you're finding the app useful.

camel_landy - I'm not explicitly encrypting anything - just uploading to the cloud (OneDrive). I can only assume if you're having problems that it's something built into Microsoft OneDrive. More on their encryption here - but I'm not actively encrypting files or folders.

https://you.com/search?q=onedrive%20download%20enc...

G.

[camel_landy]

notaping said:

camel_landy - I'm not explicitly encrypting anything - just uploading to the cloud (OneDrive). I can only assume if you're having problems that it's something built into Microsoft OneDrive. More on their encryption here - but I'm not actively encrypting files or folders.

https://you.com/search?q=onedrive%20download%20enc...

G.

Hiya,

No problems with downloading or encryption. Publishing the file hash is an easy check to make sure the file hasn't been tampered with during the upload/download process. ie: If you calculate the file hash before uploading it, when I download it, it should be exactly the same and copying the hash into the chat here means we can quickly validate.

https://learn.microsoft.com/en-us/powershell/modul...

Get-FileHash AJPDiagnostics_x86.msi -Algorithm SHA256 | Format-List

M

[notaping]

Ah. Ok. Got you. Additional security check.

Hash values generated from the local build copies:

Algorithm : SHA256
Hash : 926FB7D17F38BFEF5E3D54AE86268E746EA02AA81280A2FDC8419D9954AA2C3B
Path : T:\AJP Diagnostics\builds\32bit\AJPDiagnostics_x86.msi


Algorithm : SHA256
Hash : 80DE5EE132A0632AF29A08882F6CE53035068E8F025724EA5B3D2A3091F47D02
Path : T:\AJP Diagnostics\builds\64bit\AJPDiagnostics_x64.msi

[Rufus Roughcut]

A massive thank you notaping, today I had the opportunity to try out your App and it worked flawlessly

I borrowed Judders idea of buying a cheap tablet (virtual machine software sometimes is a faff) ending up with a HP Pro x2 612 G2 with a 64bit Pentium 4410Y CPU, 4Gb RAM off of ebay for £80, really can't fault it.

I used a FTDI USB to serial, set the comm port to 5 and that was it, connected.

This is the first time my car has been started since September last year, I was pleased to see the temperature gauge was reading the same as the software, lambda' flicking as they should, adaptives recording, although no historic data, I'm guessing the Dallas is due for replacement.