48 minutes ago, codebuilder said:

I meant to ask too, did it fail right away or after a long time?

I will grab the log file later tonight when I can. It failed right away, same as before.

9 hours ago, codebuilder said:

Hmm that should have worked, something else is wrong.  The XML will have nothing to do with the calibrations loading.  Can you post the programlog.txt file for the DPS archives?   it would help a lot.

 

Here is the log.txt from DPS when the programming failed.

ProgramLog.Txt

3 hours ago, NDCharlie said:

Here is the log.txt from DPS when the programming failed.

ProgramLog.Txt 11.17 kB · 1 download

It really doesn't like the bootloader....  that's for sure the original VIN for that cluster?  Can you do a "get info" in DPS and get me all of the calibrations programmed into it?  ECU ID 60, low-speed bus as you've been doing but get me a screenshot if you can.    It should have taken that...  Especially as I'm using a VXDiag too. 

8 hours ago, codebuilder said:

It really doesn't like the bootloader....  that's for sure the original VIN for that cluster?  Can you do a "get info" in DPS and get me all of the calibrations programmed into it?  ECU ID 60, low-speed bus as you've been doing but get me a screenshot if you can.    It should have taken that...  Especially as I'm using a VXDiag too. 

here is a screenshot of the "get info".  I double checked to confirm the vin is the original one but not sure if somthing has been done to in previously as there is some odd info in the shop section.

Some addition info, I'm wondering if it's an issue with my computer/software/VX. Anything I try to flash with DPS fails. I swapped to the locked IPC and that failed then I tried flashing the programming to the memory seat controller and also failed, all at the same point with same issues of ECU not responding

2 hours ago, NDCharlie said:

Some addition info, I'm wondering if it's an issue with my computer/software/VX. Anything I try to flash with DPS fails. I swapped to the locked IPC and that failed then I tried flashing the programming to the memory seat controller and also failed, all at the same point with same issues of ECU not responding

I'm actually thinking you are having issues with it.    You're using a VCX Nano which is the same as what I use?  I see you're on LS-CAN which is good, you're using 33.3kbps right?  It's like it didn't get a response back and then just went into a retry loop

 

Pull the log out of c:\programdata\vcx\logs\PASSTHRU after attempting and post it here if you can.  I'll see if it's actually getting responses.

Yes, using 33.3kbps.

 

I also noticed that my power mirrors are not working. Thinking back, at the very start of this when I finally got SPS working I went through and updated all of the ECU's in the pickup that needed it.  Kinda of a got it to work so using the crap out of it kinda think haha.  I remembered that the last one was the memory module for seats mirrors etc.  As it was starting my laptop gave me a low battery warning and i thought it had just finished as the laptop went down (my mistake for letting it go so low and not plugging it in) but wondered if it didn't finish.  I tried this evening to program it using SPS and it will download and program it to the end counting all the way down but then just jumps to retry 1 then 2 then stalls and I have to force it down.  Strongly thinking that all might have something to do with some of this.

 

Unfortunatly I don't have anything on my drive for programdata or vcx logs.

4 minutes ago, NDCharlie said:

Yes, using 33.3kbps.

 

I also noticed that my power mirrors are not working. Thinking back, at the very start of this when I finally got SPS working I went through and updated all of the ECU's in the pickup that needed it.  Kinda of a got it to work so using the crap out of it kinda think haha.  I remembered that the last one was the memory module for seats mirrors etc.  As it was starting my laptop gave me a low battery warning and i thought it had just finished as the laptop went down (my mistake for letting it go so low and not plugging it in) but wondered if it didn't finish.  I tried this evening to program it using SPS and it will download and program it to the end counting all the way down but then just jumps to retry 1 then 2 then stalls and I have to force it down.  Strongly thinking that all might have something to do with some of this.

 

Unfortunatly I don't have anything on my drive for programdata or vcx logs.

Its a hidden folder 🙂 

 

try clicking start, type run, then type c:\programdata and hit enter.   It should come up.  Otherwise you need to go into view options and show hidden files and folders.  

4 minutes ago, codebuilder said:

Its a hidden folder 🙂 

 

try clicking start, type run, then type c:\programdata and hit enter.   It should come up.  Otherwise you need to go into view options and show hidden files and folders.  

Ahhhh, dang sneaky computer stuff.

 

Here you go.

VCXPT32.log

7 minutes ago, NDCharlie said:

Ahhhh, dang sneaky computer stuff.

 

Here you go.

VCXPT32.log 153.41 kB · 0 downloads

This is really interesting...  When you have a chance, can you try the IPC Custom file, grab me the programlog.txt again and grab me this VCXPT32.log (it will be overwritten each time).  I want to see what it shows....  Just a quick glance, it almost looks like it's not even hearing your commands on the bus at all (transmit is broken).  But only after it sets up filters....  it does see the "Request Computer IDs" command and they respond back.  It's obviously partially working otherwise you wouldn't be able to do Get Info either.

 

 

6 minutes ago, codebuilder said:

This is really interesting...  When you have a chance, can you try the IPC Custom file, grab me the programlog.txt again and grab me this VCXPT32.log (it will be overwritten each time).  I want to see what it shows....  Just a quick glance, it almost looks like it's not even hearing your commands on the bus at all (transmit is broken).  But only after it sets up filters....  it does see the "Request Computer IDs" command and they respond back.  It's obviously partially working otherwise you wouldn't be able to do Get Info either.

 

 

logs from just now

VCXPT32.log ProgramLog.Txt

1 minute ago, NDCharlie said:

logs from just now

VCXPT32.log 133.11 kB · 0 downloads ProgramLog.Txt 11.11 kB · 0 downloads

Ok this is making more sense now.  Something is wrong with either your VCX Nano driver (pass-thru), I'd try reinstalling it.  When it goes to add message filters, or in this case, it's using a flow control protocol, it breaks!  I thought I saw this in your programlog last time too and now it's definitely what I'm seeing.  Initially, when the VCX connects it listens for any messages on the bus.  That's so that it can "Request Computer ID's" to find out what's on the bus then it sends a few others like Disable All DTC's and Disable all communications (to lower chatter on the network while programming).  After it does that, it sets up a flow control filter specifically for the module you're programming and it usually adds the diagnostics ID as another filter.  What's happening there is once that happens, your VCX stops communicating.  You could try updating the firmware but if I were to guess, it's related to your passthru driver.  Try re-installing the VCX software and see if it fixes it.

 

 

Preparing Controller
Utility File:  22854403.BIN
Utility File Step=01 Opcode=01
Utility File Step=02 Opcode=27
  21:06:04.306<[...L] 00 00 02 4C 27 01 [0006] FramePad 
  21:06:04.306>[...L] 00 00 01 01 FE [0005] ExtAddress TxDone TxMsgType 
  21:06:04.306>[...L] 00 00 02 4C [0004] TxDone TxMsgType 
>> * Timeout Condition:  ECU DID NOT RESPOND - Invoke RETRY LOGIC! <-- It was expecting a 06 4C response from the module, it never got it...  
  21:06:05.853<[...L] 00 00 02 4C 27 01 [0006] FramePad 
  21:06:05.853>[...L] 00 00 02 4C [0004] TxDone TxMsgType 
Utility File Step=03 Opcode=F1
Utility File Step=04 Opcode=34
  21:06:07.384<[...L] 00 00 02 4C 34 00 00 00 12 70 [0010] FramePad   <-- This should have never made it this far, that's what threw me off...  We never got security access....
  21:06:07.384>[...L] 00 00 02 4C [0004] TxDone TxMsgType 
 

 

In the other log I can see it too:

 

Msg->ucData: 00 00 02 4c
    Line 2390: [21:06:05.853] Msg->ucData: 00 00 02 4c 27 01
    Line 2412: [21:06:05.853] Msg->ucData: 00 00 02 4c
    Line 2443: [21:06:07.384] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2465: [21:06:07.384] Msg->ucData: 00 00 02 4c
    Line 2509: [21:06:08.916] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2531: [21:06:08.916] Msg->ucData: 00 00 02 4c
    Line 2617: [21:06:11.568] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2639: [21:06:11.568] Msg->ucData: 00 00 02 4c
    Line 2683: [21:06:13.099] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2705: [21:06:13.099] Msg->ucData: 00 00 02 4c
    Line 2791: [21:06:15.738] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2813: [21:06:15.738] Msg->ucData: 00 00 02 4c
    Line 2857: [21:06:17.269] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70

 

 

Your VCX is requesting commands to the cluster but it never responds back!  

 

I'm heavily leaning it's your driver.  

 

For fun, could you do a "Get Info" then get me that VCX log?  I just want to see if it sets up filters.  Your VCX is definitely working or you wouldn't be able to do that.  Right now, I suspect it's when it tries to setup the flow control filters.

 

 

18 minutes ago, codebuilder said:

Ok this is making more sense now.  Something is wrong with either your VCX Nano driver (pass-thru), I'd try reinstalling it.  When it goes to add message filters, or in this case, it's using a flow control protocol, it breaks!  I thought I saw this in your programlog last time too and now it's definitely what I'm seeing.  Initially, when the VCX connects it listens for any messages on the bus.  That's so that it can "Request Computer ID's" to find out what's on the bus then it sends a few others like Disable All DTC's and Disable all communications (to lower chatter on the network while programming).  After it does that, it sets up a flow control filter specifically for the module you're programming and it usually adds the diagnostics ID as another filter.  What's happening there is once that happens, your VCX stops communicating.  You could try updating the firmware but if I were to guess, it's related to your passthru driver.  Try re-installing the VCX software and see if it fixes it.

 

 

Preparing Controller
Utility File:  22854403.BIN
Utility File Step=01 Opcode=01
Utility File Step=02 Opcode=27
  21:06:04.306<[...L] 00 00 02 4C 27 01 [0006] FramePad 
  21:06:04.306>[...L] 00 00 01 01 FE [0005] ExtAddress TxDone TxMsgType 
  21:06:04.306>[...L] 00 00 02 4C [0004] TxDone TxMsgType 
>> * Timeout Condition:  ECU DID NOT RESPOND - Invoke RETRY LOGIC! <-- It was expecting a 06 4C response from the module, it never got it...  
  21:06:05.853<[...L] 00 00 02 4C 27 01 [0006] FramePad 
  21:06:05.853>[...L] 00 00 02 4C [0004] TxDone TxMsgType 
Utility File Step=03 Opcode=F1
Utility File Step=04 Opcode=34
  21:06:07.384<[...L] 00 00 02 4C 34 00 00 00 12 70 [0010] FramePad   <-- This should have never made it this far, that's what threw me off...  We never got security access....
  21:06:07.384>[...L] 00 00 02 4C [0004] TxDone TxMsgType 
 

 

In the other log I can see it too:

 

Msg->ucData: 00 00 02 4c
    Line 2390: [21:06:05.853] Msg->ucData: 00 00 02 4c 27 01
    Line 2412: [21:06:05.853] Msg->ucData: 00 00 02 4c
    Line 2443: [21:06:07.384] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2465: [21:06:07.384] Msg->ucData: 00 00 02 4c
    Line 2509: [21:06:08.916] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2531: [21:06:08.916] Msg->ucData: 00 00 02 4c
    Line 2617: [21:06:11.568] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2639: [21:06:11.568] Msg->ucData: 00 00 02 4c
    Line 2683: [21:06:13.099] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2705: [21:06:13.099] Msg->ucData: 00 00 02 4c
    Line 2791: [21:06:15.738] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70
    Line 2813: [21:06:15.738] Msg->ucData: 00 00 02 4c
    Line 2857: [21:06:17.269] Msg->ucData: 00 00 02 4c 34 00 00 00 12 70

 

 

Your VCX is requesting commands to the cluster but it never responds back!  

 

I'm heavily leaning it's your driver.  

 

For fun, could you do a "Get Info" then get me that VCX log?  I just want to see if it sets up filters.  Your VCX is definitely working or you wouldn't be able to do that.  Right now, I suspect it's when it tries to setup the flow control filters.

 

 

after get info

VCXPT32.log

I'm also noticing that right as it's hitting the spot were it come back no responce the IPC and radio power cycle. Not sure if it's causing the issue or if it's being caused by the issue.

13 minutes ago, NDCharlie said:

after get info

VCXPT32.log 214.72 kB · 0 downloads

Ok, so that is using flow control as well, but it's working here....

 

This stood out to me on the programming one and it wasn't in the get info.  I'll try programming an IPC on the bench here after and look at mine.

 

[21:06:04.135] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[21:06:04.135] PassThruIoctl.
[21:06:04.135] ulChannelID = 1
[21:06:04.135] enumIoctlID = 0x00008000
[21:06:04.135] pChannel = 0x71314080
[21:06:04.135] Unknow IOCTL ID
[21:06:04.135] [0x0000000f] J2534_ERR_INVALID_IOCTL_ID
[21:06:04.135] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[21:06:04.135] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[21:06:04.135] PassThruIoctl.
[21:06:04.135] ulChannelID = 1
[21:06:04.135] enumIoctlID = 0x00000002
[21:06:04.135] pChannel = 0x71314080
[21:06:04.135] SET_CONFIG
[21:06:04.135] ulNumOfParams = 1
[21:06:04.135] Config #0     *CAN_MIXED_FORMAT
[21:06:04.135] Parameter:    0x00008000
[21:06:04.135] ulValue:    0x00000001(1)
[21:06:04.135] Save Config #0: Param = 00008000, Value = 00000001, Set=0
[21:06:04.135] [0x00000000] J2534_STATUS_OK
[21:06:04.135] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
 

 

 

10 minutes ago, NDCharlie said:

I'm also noticing that right as it's hitting the spot were it come back no responce the IPC and radio power cycle. Not sure if it's causing the issue or if it's being caused by the issue.

I'm trying one on the bench right now

2 minutes ago, codebuilder said:

I'm trying one on the bench right now

I think I know what's going on....  Which version of DPS are you using?  I had a problem with one on the low speed.

 

I'm programming a cluster right now, my version of DPS does not do this...  Note the 83333 baud rate....  I'm on DPS 4.53 and I had 4.46 before.  I had a version I think 4.48 that wouldn't work properly.

 

[21:06:04.135] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[21:06:04.135] PassThruIoctl.
[21:06:04.135] ulChannelID = 1
[21:06:04.135] enumIoctlID = 0x00000002
[21:06:04.135] pChannel = 0x71314080
[21:06:04.135] SET_CONFIG
[21:06:04.135] ulNumOfParams = 3
[21:06:04.135] Config #0     *SW_CAN_SPEEDCHANGE_ENABLE
[21:06:04.135] Parameter:    0x00008011
[21:06:04.135] ulValue:    0x00000001(1)
[21:06:04.135] Config #1     *SW_CAN_RES_SWITCH
[21:06:04.135] Parameter:    0x00008012
[21:06:04.135] ulValue:    0x00000002(2)
[21:06:04.135] Config #2     *SW_CAN_HS_DATA_RATE
[21:06:04.135] Parameter:    0x00008010
[21:06:04.135] ulValue:    0x00014585(83333)
[21:06:04.135] Save Config #0: Param = 00008011, Value = 00000001, Set=0
[21:06:04.135] Save Config #1: Param = 00008012, Value = 00000002, Set=0
[21:06:04.135] Save Config #2: Param = 00008010, Value = 00014585, Set=0
[21:06:04.135] [0x00000000] J2534_STATUS_OK
[21:06:04.135] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[21:06:04.135] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[21:06:04.135] PassThruIoctl.
[21:06:04.135] ulChannelID = 1
[21:06:04.135] enumIoctlID = 0x00008000
[21:06:04.135] pChannel = 0x71314080
[21:06:04.135] Unknow IOCTL ID
[21:06:04.135] [0x0000000f] J2534_ERR_INVALID_IOCTL_ID
[21:06:04.135] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
 

 

 

You’re on 4.52….   I think that may have been the one I had issues with.  Can you try 4.46? 

1 minute ago, codebuilder said:

You’re on 4.52….   I think that may have been the one I had issues with.  Can you try 4.46? 

I only have 4.52 but I can try reinstalling it. It did work before so wonder if something got out of line at some point

40 minutes ago, NDCharlie said:

I only have 4.52 but I can try reinstalling it. It did work before so wonder if something got out of line at some point

Give it a try and let me know.  If not, I'll get you 4.46.  I definitely had issues with one version....  I do feel we're getting close, the VCX log gave me the detail I needed to see.  I have applications that we could test if needed.  The mirrors should be able to be fixed once we get this communication issue sorted.  High speed probably works fine I'm sure, just the low speed stuff.

On 2/29/2024 at 10:52 PM, codebuilder said:

Give it a try and let me know.  If not, I'll get you 4.46.  I definitely had issues with one version....  I do feel we're getting close, the VCX log gave me the detail I needed to see.  I have applications that we could test if needed.  The mirrors should be able to be fixed once we get this communication issue sorted.  High speed probably works fine I'm sure, just the low speed stuff.

I tried reinstalling DPS and also tech line as that was also acting up. Unfortunately still a no go, same error