NEW Windows 64 bit AJP Diagnostic Software
Discussion
Did you need to have the first version installed to get the updated version to work? Running it on a Win10 (64 Bit) and when I open the application nothing happens. Task Manager shows it running as a background process, using approx. 48Mb of memory. Any pointers to what I may be doing wrong please?
Hi, Thanks for giving this a try.
Does the application not open at all? It's not a situation I've come across.
Try - right click on shortcut, then RunAs Administrator. The app will run without this, however this is needed to provide write permission for event logging and data logging if you want to record engine data.
If there's still a problem, look in C:\Program Files\KCC\AJP Diagnostics\Logs\CerbDiags.log and PM me with the contents.
I've tested the app on multiple machines and have not come across this situation before. There have been other issues as you'll see if you look back through this thread, but I'm trying to address them, and with a bit of help and patience from the community - hopefully I'll be able to provide something useful.
G.
Does the application not open at all? It's not a situation I've come across.
Try - right click on shortcut, then RunAs Administrator. The app will run without this, however this is needed to provide write permission for event logging and data logging if you want to record engine data.
If there's still a problem, look in C:\Program Files\KCC\AJP Diagnostics\Logs\CerbDiags.log and PM me with the contents.
I've tested the app on multiple machines and have not come across this situation before. There have been other issues as you'll see if you look back through this thread, but I'm trying to address them, and with a bit of help and patience from the community - hopefully I'll be able to provide something useful.
G.
jeboa said:
Did you need to have the first version installed to get the updated version to work? Running it on a Win10 (64 Bit) and when I open the application nothing happens. Task Manager shows it running as a background process, using approx. 48Mb of memory. Any pointers to what I may be doing wrong please?
Brilliant job notaping thanks for all your hardwork. Unfortunately I'm having the same issue as jeboa, running in the background only, no app window opening. Dell laptop running win10 64bit.BTW, I have TVR MBETool installed on the same laptop and it starts-up fine, not connected it to the Tuscan yet, I thought this wasn't supposed to run on win10 64bit?
Hi, I tried AJPDiagnostics 1.0.8485.31017 this afternoon.
The result for me is the same as the original, application loads fine but doesn't detect the ECU - I tried three com ports. The logfile is saved if that would be useful, but just says ECU not found.
Oh this is on Windows 10 64 bit as before.
The result for me is the same as the original, application loads fine but doesn't detect the ECU - I tried three com ports. The logfile is saved if that would be useful, but just says ECU not found.
Oh this is on Windows 10 64 bit as before.
Whao! - we've got a raft of problems now. For some it won't run, for others it runs but won't connect. Why o why does it run of all my machines?? I've tried 3 different installations now. Arghh!!
Ok. For those who can't get the application started - I've received a log from jeboa which has given me some direction on that front. Working on it.
Englishman - you can start the app but not connect. Click the wee engine icon on the right of the menu bar - that should open the help screen. The last section provides instructions on how to access Dev mode. That should at least let you see if the application's finding the available COM ports in Windows - even if it's not subsequently connecting to the ECU. Let me know what you find. Ta.
Ok. For those who can't get the application started - I've received a log from jeboa which has given me some direction on that front. Working on it.
Englishman - you can start the app but not connect. Click the wee engine icon on the right of the menu bar - that should open the help screen. The last section provides instructions on how to access Dev mode. That should at least let you see if the application's finding the available COM ports in Windows - even if it's not subsequently connecting to the ECU. Let me know what you find. Ta.
notaping said:
Englishman - you can start the app but not connect. Click the wee engine icon on the right of the menu bar - that should open the help screen. The last section provides instructions on how to access Dev mode. That should at least let you see if the application's finding the available COM ports in Windows - even if it's not subsequently connecting to the ECU. Let me know what you find. Ta.
Attached are a couple of images, apologies for the quality. The first is running the application as admin, plus displaying Device Manager and the logfile.
The second is running the application as admin with Dev Mode set, displaying all Com port options available, plus displaying Device Manager.
As you can see, only Com 1 is listed in the application, not Com 2, to which my Serial to USB converter and MBE ECU is connected to. Both appear in device manager. Please let me know if I can help further with diagnosis.
Modrich said:
jeboa said:
Did you need to have the first version installed to get the updated version to work? Running it on a Win10 (64 Bit) and when I open the application nothing happens. Task Manager shows it running as a background process, using approx. 48Mb of memory. Any pointers to what I may be doing wrong please?
Brilliant job notaping thanks for all your hardwork. Unfortunately I'm having the same issue as jeboa, running in the background only, no app window opening. Dell laptop running win10 64bit.BTW, I have TVR MBETool installed on the same laptop and it starts-up fine, not connected it to the Tuscan yet, I thought this wasn't supposed to run on win10 64bit?
Windows 10 Pro - build 21H2 64 bit.
Edited by Byker28i on Thursday 6th April 13:13
Had problems recently with work laptops running Win10. A specific program I use requires a software dongle plugged in a usb port. Working fine until a service pack was rolled out and the laptops could no longer see the dongle. Could your issue be as straight forward as this?
In my case it did throw up an error message so may not be relevant but hope this helps.
In my case it did throw up an error message so may not be relevant but hope this helps.
All, I've made some progress with this and believe I now have something which will run and connect. Here's the new link . . .
https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...
This has been independently tested with some positive feedback - thanks jeboa for testing this for me.
And thanks to all on this forum that have tried the app and given feedback so far. All very valuable info. Keep it comping, and hopefully we'll have a few thumbs up this time
G.
https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...
This has been independently tested with some positive feedback - thanks jeboa for testing this for me.
And thanks to all on this forum that have tried the app and given feedback so far. All very valuable info. Keep it comping, and hopefully we'll have a few thumbs up this time
G.
notaping said:
All, I've made some progress with this and believe I now have something which will run and connect. Here's the new link . . .
https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...
This has been independently tested with some positive feedback - thanks jeboa for testing this for me.
And thanks to all on this forum that have tried the app and given feedback so far. All very valuable info. Keep it comping, and hopefully we'll have a few thumbs up this time
G.
Just given it a quick test. The application loads and I can now connect to the ECU https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...
This has been independently tested with some positive feedback - thanks jeboa for testing this for me.
And thanks to all on this forum that have tried the app and given feedback so far. All very valuable info. Keep it comping, and hopefully we'll have a few thumbs up this time
G.
The menu, diagnostic screen and real time display all now work for me
On the down side, resetting the fault codes and displaying either adaptive map don't work for me at present. I haven't tried resetting the adaptive maps or throttles yet as the car (S6 engine) is running fine. Happy to provide more info as needed.
Edited by Englishman on Friday 14th April 13:51
Almost there, well done on what you have done so far.
I only have 2 points to raise (which is good!)
The reset adaptives button doesn't work, the adaptives stay exactly as they were prior to pressing the button.
Also the adaptive pages don't sometimes load, i can see that it says to increase the time allowed to look for them (apologies for lack of tech speak) .. but how do I edit the config? Do I do it in notepad and save as txt file ?
I only have 2 points to raise (which is good!)
The reset adaptives button doesn't work, the adaptives stay exactly as they were prior to pressing the button.
Also the adaptive pages don't sometimes load, i can see that it says to increase the time allowed to look for them (apologies for lack of tech speak) .. but how do I edit the config? Do I do it in notepad and save as txt file ?
Thanks. At least there's some progress - which is encouraging.
I have noticed that the adaptives sometimes fail to load. The only source of info I have about the adaptive data is by recording traffic from a port sniffer while using the original software. Then trying to interpret that data. There is a possibility that I might have missed something. I'll revisit it when I have time. Meanwhile - run Notepad as Administrator, open AJPDiagnostics.exe.config and increase AdaptiveDataReadWaitTime from 200 to 300. Then click save. You'll need to restart the app to pick up the new value. (You need Administrator privileges to save files within the Program Files folder structure.)
The reset functionalities are tricky to test without splatting all your data - which I know is the point, but all my adaptive data has leaked away over winter - so I've nothing to test against. I know it worked last summer as did the reset logged data button. I can't test the reset throttles since I don't have access to a SP6, but I believe it's sending the correct message.
Perhaps - if there's anyone out there with knowledge of these procedures (in software) either in RS AJP or the MBE Tool (EvoOli) they could PM me with some hints/advice. Again - when I've time I'll get the port sniffer back on the old software and double check what it's doing.
Thanks for trying this app and putting up with it's teething issues. Hopefully I'll get it all stable before people run out of patience. Keep the feedback coming. Ta.
I have noticed that the adaptives sometimes fail to load. The only source of info I have about the adaptive data is by recording traffic from a port sniffer while using the original software. Then trying to interpret that data. There is a possibility that I might have missed something. I'll revisit it when I have time. Meanwhile - run Notepad as Administrator, open AJPDiagnostics.exe.config and increase AdaptiveDataReadWaitTime from 200 to 300. Then click save. You'll need to restart the app to pick up the new value. (You need Administrator privileges to save files within the Program Files folder structure.)
The reset functionalities are tricky to test without splatting all your data - which I know is the point, but all my adaptive data has leaked away over winter - so I've nothing to test against. I know it worked last summer as did the reset logged data button. I can't test the reset throttles since I don't have access to a SP6, but I believe it's sending the correct message.
Perhaps - if there's anyone out there with knowledge of these procedures (in software) either in RS AJP or the MBE Tool (EvoOli) they could PM me with some hints/advice. Again - when I've time I'll get the port sniffer back on the old software and double check what it's doing.
Thanks for trying this app and putting up with it's teething issues. Hopefully I'll get it all stable before people run out of patience. Keep the feedback coming. Ta.
Ok. Some more fixes.
The 'reset' buttons should now work & I've re-worked the logic that loads the adpative map data - so it should be more stable.
It's a slow process, but I think it's getting there. Once again - feedback appreciated.
https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...
The 'reset' buttons should now work & I've re-worked the logic that loads the adpative map data - so it should be more stable.
It's a slow process, but I think it's getting there. Once again - feedback appreciated.
https://api.onedrive.com/v1.0/shares/s!AuU8U8VUHEO...
Gassing Station | Cerbera | Top of Page | What's New | My Stuff