Hello, i have the problem when i will load some ecus with PIN 1 33.3kbaud then he don't load it and after there is no os sw on the ecu. A Friend means the vxdiag load too fast. What can i do for the problem? Many thanks

VXdiag is not perfect, no doubt.. But which DPS version are you using?
I have some bad luck with a cracked/modified 4.56... So I went back to 4.52/4.54

Replied to your DM. As pupu14 stated, I run 4.46 unless I need the newer version as I've had some issues with one of the versions (I can't remember). Although, as I responded, I have seen buffer issues. The best is always attach the DPS log file if you can so we can see the error. If it's timeouts you're seeing, it'll probably be either the wrong OS or buffer issue.

Hello,

ok next Time i send the Log File at First. What must be done in the File when that is the Buffer issue?

On 9/12/2025 at 1:55 AM, pupu14 said:

VXdiag is not perfect, no doubt.. But which DPS version are you using?
I have some bad luck with a cracked/modified 4.56... So I went back to 4.52/4.54

4.56 runs perfectly with VXdiag, MDI and MDI2 - I have programmed 100's of modules and never had an issue so would really like to know what "issues" you had and a screen shot would help.

I will say this and that is if your j2534 drivers are out of date and corrupt you will have issues with any version but especially the later versions. Regular users of Techline Connect would have noticed the j2534 drivers being updated multiple times this year and as a bonus of using Techline Connect you do not have to swap the type 4 drivers around anymore as they work fine as they are with v4.56.

If you don't have the latest drivers then that is most of your problem!

17 minutes ago, uglyoldbastard said:

4.56 runs perfectly with VXdiag, MDI and MDI2 - I have programmed 100's of modules and never had an issue so would really like to know what "issues" you had and a screen shot would help.

I will say this and that is if your j2534 drivers are out of date and corrupt you will have issues with any version but especially the later versions. Regular users of Techline Connect would have noticed the j2534 drivers being updated multiple times this year and as a bonus of using Techline Connect you do not have to swap the type 4 drivers around anymore as they work fine as they are with v4.56.

If you don't have the latest drivers then that is most of your problem!

I just responded quickly at the time, I already knew what the issue was (we got it fixed). There's a version of 4.48 floating around that has issues. I don't quite remember what it would do as I stopped using it over a year ago (I probably still have it somewhere) but 4.46 and 4.56 work great. I own a genuine MDI 2, VNCI and a VCX Nano. I've programmed hundreds too, wrote my own software for direct communication on the canbus networks, etc.

As far as the VCX.... I have it entirely isolated in a virtual machine if I use that. I have no trust in their software though lol. Something caught a bunch of my passwords about two years ago and that was the only questionable software I had on that system and some of the credentials captured, I know were only used on that system. I've found tons of my different logins on different sites (Leak Passwords for example) and I haven't pinpointed it exactly to the VCX but regardless, I'll only run it in a VM now. Those passwords shown they were captured by stealer type software. The VCX software already did flag as a virus for me but a lot of my programs flag too when I obfuscate them, so it's tough to say. I just thought I'd share that experience though.

55 minutes ago, codebuilder said:

I just responded quickly at the time, I already knew what the issue was (we got it fixed). There's a version of 4.48 floating around that has issues. I don't quite remember what it would do as I stopped using it over a year ago (I probably still have it somewhere) but 4.46 and 4.56 work great. I own a genuine MDI 2, VNCI and a VCX Nano. I've programmed hundreds too, wrote my own software for direct communication on the canbus networks, etc.

As far as the VCX.... I have it entirely isolated in a virtual machine if I use that. I have no trust in their software though lol. Something caught a bunch of my passwords about two years ago and that was the only questionable software I had on that system and some of the credentials captured, I know were only used on that system. I've found tons of my different logins on different sites (Leak Passwords for example) and I haven't pinpointed it exactly to the VCX but regardless, I'll only run it in a VM now. Those passwords shown they were captured by stealer type software. The VCX software already did flag as a virus for me but a lot of my programs flag too when I obfuscate them, so it's tough to say. I just thought I'd share that experience though.

All good I understand I only use VCX Nano as a j2534 device as just like you I don't trust there software but I use it in a VMware image that is date locked so I do not have to get it synced to update the license. I just update the other software on the image via a USB stick which does not seem to have any issues. Luckily I have not had any credentials stolen but I use a different password, user name, birth date and multiple email address's as I trust no one!

7 hours ago, uglyoldbastard said:

4.56 runs perfectly with VXdiag, MDI and MDI2 - I have programmed 100's of modules and never had an issue so would really like to know what "issues" you had and a screen shot would help.

I will say this and that is if your j2534 drivers are out of date and corrupt you will have issues with any version but especially the later versions. Regular users of Techline Connect would have noticed the j2534 drivers being updated multiple times this year and as a bonus of using Techline Connect you do not have to swap the type 4 drivers around anymore as they work fine as they are with v4.56.

If you don't have the latest drivers then that is most of your problem!

I don't have any VCX device, so your input was irrelevant to my case. I have commented just on seeing other people's experiences with VCX devices.

I had issue with 4.56 - there were nothing in the logs to analyze. It just didn't perform a task I was expecting it to do.
Issue was immediately fixed when I downgraded DPS version - same DPS archive, J2534 hardware/software and bench wiring setup.

Edited September 14, 2025Sep 14 by pupu14

51 minutes ago, pupu14 said:

I don't have any VCX device, so your input was irrelevant to my case. I have commented just on seeing other people's experiences with VCX devices.

I had issue with 4.56 - there were nothing in the logs to analyze. It just didn't perform a task I was expecting it to do.
Issue was immediately fixed when I downgraded DPS version - same DPS archive, J2534 hardware/software and bench wiring setup.

As I said J2534 drivers have been upgraded along the way so you did it by downgrading the software where as I fix the problems by upgrading the drivers on the system and not just j2534 drivers but all drivers on my laptops and computers are the latest available.

My point is this is how bullshit starts - one person has a problem but rather than working out why just blames the program and then proceeds to tell anyone who will listen that the software does not work how they expected and caused problems. What they fail to disclose is that they did nothing to analyze the problem or to see if it could be fixed instead they just complain that it does not work.
No mention of the issue on the forum to see if it could be fixed instead just complain to the next person and start the bullshit flowing.

That is the way I see it but you might see it from a different perspective and that is your right but I am still going to point out to the person you are telling that maybe there is a different reason and not the one you are saying it is.

Hello, the problem with my Vxdiag is only with ecus with PIN 1. I used the dps 4.52. Not all ecus have this problem with the Vxdiag. Very strange. Drivers are the newest. With another files from Codebuilder the software can be load.

27 minutes ago, uglyoldbastard said:

4.56 runs perfectly with VXdiag, MDI and MDI2 - I have programmed 100's of modules and never had an issue so would really like to know what "issues" you had and a screen shot would help.

I will say this and that is if your j2534 drivers are out of date and corrupt you will have issues with any version but especially the later versions. Regular users of Techline Connect would have noticed the j2534 drivers being updated multiple times this year and as a bonus of using Techline Connect you do not have to swap the type 4 drivers around anymore as they work fine as they are with v4.56.

If you don't have the latest drivers then that is most of your problem!

I should also add what the issue was :). There is an issue with the VCX in some cases where it can't buffer for ISO15765 properly if the buffer is too large... A genuine MDI works fine but some of the clones struggle if it's too large.

Just now, tobiasp said:

Hello, the problem with my Vxdiag is only with ecus with PIN 1. I used the dps 4.52. Not all ecus have this problem with the Vxdiag. Very strange. Drivers are the newest. With another files from Codebuilder the software can be load.

You'll run into that issue with other modules on the VCX... it struggles with the large buffer with ISO15765... I ran into it with a SDGM as well.

Yes i think that is that problem. Wirh the new file it works.

1 minute ago, tobiasp said:

Yes i think that is that problem. Wirh the new file it works.

I've helped a few people with that issue on various modules. It's only ISO15765 on the LS CAN and when GM has the buffer at max. And it's only for a large upload... so, if the OS is different, it'll break for sure as it's too large. VCX definitely has a bug in it but again, we were able to work around it. I first ran into it about two years ago :).

vxdiag for programming not works fine... programming a K109 Front camera, i have a lot of problems, with MDI2 genuine, no problems

Yes, big problem. I search for a mdi original but i don't found a mdi 2

On 9/14/2025 at 11:14 AM, uglyoldbastard said:

As I said J2534 drivers have been upgraded along the way so you did it by downgrading the software where as I fix the problems by upgrading the drivers on the system and not just j2534 drivers but all drivers on my laptops and computers are the latest available.

My point is this is how bullshit starts - one person has a problem but rather than working out why just blames the program and then proceeds to tell anyone who will listen that the software does not work how they expected and caused problems. What they fail to disclose is that they did nothing to analyze the problem or to see if it could be fixed instead they just complain that it does not work.
No mention of the issue on the forum to see if it could be fixed instead just complain to the next person and start the bullshit flowing.

That is the way I see it but you might see it from a different perspective and that is your right but I am still going to point out to the person you are telling that maybe there is a different reason and not the one you are saying it is.

1. My PC software/hardware is in top notch condition, no need to advise here. And I highly doubt that outdated VGA or WiFi driver, that get released every week, can cause problems with DPS...

2. I do understand, however, that newer DPS app may have updated DLLs which may conflict with some particular driver. And when all the drivers in system are current - I, nor anyone else, have time to rollback drivers one-by-one to try and see if it fixes the issue, when simply rolling back DPS version fixes everything. So the issue is 100% with DPS, and without knowing what OP is running, it is a valid suggestion.
   
   And I did documented my issue on this forum. But there won't be anything in the logs, as I have mentioned.

The bottom line really is that DPS 4.56 works perfectly but the VXdiag is a piece of shit and belongs in a bin but people want to run cheap Chinese rubbish. I run v4.56 everyday with a genuine MDI and MDI2 and have ZERO issues.

If you want to run clone/cheap/Chinese hardware then good luck to you but 99% of the issues is the hardware.

Here are some tips for all users running any version of DPS and cheap hardware interface or computer

Firstly go to options and Disable High Load UI Components as this helps dramatically with slow interfaces and slow laptops.

Secondly some modules want the DTC's cleared before programming so go to Program / Clear DTC's before programming.

Finally if you are having issues then do the above and then enable logging under options for the appropriate driver j2534/DOIP etc and then look at the logs after it fails.

I was able to work around the VX Nano buffer issues with LS-CAN using the utility file modification. There's a buffer size value at byte 17. It's usually set to FF, so I changed it to 30 or so, and voila, I flashed my K109 with VXNano. It just flashes slower because of a smaller buffer.