PowerPCM_Flasher: my tool for E38 and E67

Programs / Tools / Scripts
User avatar
Posts: 25
Joined: Wed May 19, 2021 6:11 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby FriskyDingo » Thu Aug 19, 2021 1:13 am

@daniel2345 Will there ever be E37 support?

User avatar
Posts: 1392
Joined: Sat Dec 15, 2018 7:38 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby Gampy » Thu Aug 19, 2021 3:02 am

Somewhere in this thread he has specifically stated that he has no plans on developing for anything other then the E38 and E67, he did also state that could change!

However, he hasn't been on here in awhile, I suspect he has accomplished his own personal goal and moved on ... Unfortunately, as oh so many worthies do!

-Enjoy
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!

User avatar
Posts: 25
Joined: Wed May 19, 2021 6:11 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby FriskyDingo » Mon Aug 23, 2021 11:25 am

Tonight I tried to connect to my buddies 2010 Silverado 4.8l with E38 ecm using a VCX Nano GM and it initialises ok recognizing the device as a bosch MDI but when I try to connect to the ecm I keep getting this error. I see a few posts mentioning problems with the vcx nano and this program, has anyone gotten it to work? The VM I was using was Windows 7.
Image

Posts: 2
Joined: Thu Jun 17, 2021 11:58 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby 71403 » Mon Aug 23, 2021 1:04 pm

I updated the ftdi driver to 2.12.28.0 and it worked a little better it would consistently connect and pass seed/key but still fail on read flash. Tried it with the vx j2534 driver you posted a while back and PowerPCM would crash out when connecting.

Installed on a virgin Win7 box and no change. I've tried it on a few different PC's same result hoping that rules out the PC side.

User avatar
Posts: 25
Joined: Wed May 19, 2021 6:11 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby FriskyDingo » Tue Aug 24, 2021 5:12 am

The VCX passthrough driver has a logging feature, here's what it spit out.
Code: Select all
[14:07:40.321] LOG DATE  = 2015-09-02
[14:07:40.321] LOG PATH  = C:\ProgramData\VCX\Logs\PASSTHRU\VCXPT32.log
[14:07:40.321] LOG LEVEL = 0xff
[14:07:40.321] LOG FLAG  = 0x00
[14:07:40.321] J2534 DLL Version: 04.04.210328
[14:07:40.321] DLL_PROCESS_ATTACH TID = 0x00000fd0
[14:07:40.321] APP Name: C:\Users\VX DIAG\Desktop\PowerPCM_Flasher_0006.exe
[14:07:40.321] DLL Name: C:\ProgramData\VCX\Apps\PASSTHRU\VCXPT32.dll
[14:07:40.321] VCX Library: VCX.DLL
[14:07:40.321] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:40.321] PassThruOpen.
[14:07:42.836] J2534DeviceOpen: CommType = Default.
[14:07:45.008] J2534DeviceOpen: pInfo = 1.8.4.0 VCX-NANO
[14:07:45.008] pulDeviceID = 0x00000001
[14:07:45.008] [0x00000000] J2534_STATUS_OK
[14:07:45.008] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:45.008] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:45.008] PassThruReadVersion.
[14:07:45.008] ulDeviceID = 0x00000001
[14:07:45.008] pApiVersion = 04.04
[14:07:45.008] pDllVersion = 04.04.210328
[14:07:45.008] pFirmwareVersion = 1.8.4.0 VCX-NANO
[14:07:45.008] [0x00000000] J2534_STATUS_OK
[14:07:45.008] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:45.008] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:45.008] PassThruConnect.
[14:07:45.008] ulDeviceID = 0x00000001
[14:07:45.008] enumProtocolID = 0x00000005
[14:07:45.008] J2534 Protocol: [0x00000005] CAN
[14:07:45.008] ulFlags = 0x00000800
[14:07:45.008] CONNFLAG_CAN_ID_BOTH
[14:07:45.008] ulBaudRate = 500000
[14:07:45.696] *pulChannelID = 1
[14:07:45.696] VCX_PROTOCOL_ISO11898_CAN
[14:07:45.821] [0x00000000] J2534_STATUS_OK
[14:07:45.821] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:45.821] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:45.821] PassThruIoctl.
[14:07:45.821] ulChannelID = 1
[14:07:45.821] enumIoctlID = 0x00000002
[14:07:45.821] pChannel = 0x72654080
[14:07:45.821] SET_CONFIG
[14:07:45.821] ulNumOfParams = 3
[14:07:45.821] Config #0    DATA_RATE
[14:07:45.821] Parameter:   0x00000001
[14:07:45.821] ulValue:   0x0007a120(500000)
[14:07:45.821] Config #1    LOOPBACK
[14:07:45.821] Parameter:   0x00000003
[14:07:45.821] ulValue:   0x00000000(0)
[14:07:45.821] Config #2    BIT_SAMPLE_POINT
[14:07:45.821] Parameter:   0x00000017
[14:07:45.821] ulValue:   0x00000050(80)
[14:07:45.821] Save Config #0: Param = 00000001, Value = 0007a120, Set=0
[14:07:45.821] Save Config #1: Param = 00000003, Value = 00000000, Set=0
[14:07:45.821] Save Config #2: Param = 00000017, Value = 00000050, Set=0
[14:07:45.821] [0x00000000] J2534_STATUS_OK
[14:07:45.821] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:45.821] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:45.821] PassThruStartMsgFilter.
[14:07:45.821] ulChannelID = 1
[14:07:45.821] enumFilterType = 1
[14:07:45.821] pstructJ2534Mask = 0x0012d988
[14:07:45.821] pstructJ2534Pattern = 0x0012c950
[14:07:45.821] pstructJ2534FlowControl = 0x00000000
[14:07:45.821] pulFilterID = 0x0012c94c
[14:07:45.821] J2534Mask:
[14:07:45.821] Msg #0 :
[14:07:45.821] Msg->ulProtocolID: 0x00000005
[14:07:45.821] Msg->ulRxStatus: 0x00000000
[14:07:45.821] Msg->ulTxFlags: 0x00000800
[14:07:45.821] Msg->ulTimeStamp:          0
[14:07:45.821] Msg->ulDataSize: 4
[14:07:45.821] Msg->ulExtraDataIndex: 0
[14:07:45.821] Msg->ucData: 00 00 07 e8
[14:07:45.821] J2534Pattern:
[14:07:45.821] Msg #0 :
[14:07:45.821] Msg->ulProtocolID: 0x00000005
[14:07:45.821] Msg->ulRxStatus: 0x00000000
[14:07:45.821] Msg->ulTxFlags: 0x00000800
[14:07:45.821] Msg->ulTimeStamp:          0
[14:07:45.821] Msg->ulDataSize: 4
[14:07:45.821] Msg->ulExtraDataIndex: 0
[14:07:45.821] Msg->ucData: 00 00 07 e8
[14:07:45.821] J2534FlowControl:
[14:07:45.821] Msg #0 :
[14:07:45.821] Msg NULL!
[14:07:45.852] Info: VCX AddFilter Complete.
[14:07:45.852] *pulFilterID = 1
[14:07:45.852] [0x00000000] J2534_STATUS_OK
[14:07:45.852] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:50.196] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:50.196] PassThruStopPeriodicMsg.
[14:07:50.196] ulChannelID = 1
[14:07:50.196] ulMsgID = 0
[14:07:50.243] Info: VCX AddTimer Complete.
[14:07:50.243] [0x00000000] J2534_STATUS_OK
[14:07:50.243] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:50.243] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[14:07:50.243] PassThruStartPeriodicMsg.
[14:07:50.243] ulChannelID = 1
[14:07:50.243] pulMsgID = 0x00415d40
[14:07:50.243] ulTimeInterval = 1000
[14:07:50.243] PeriodicMsg:
[14:07:50.243] Msg #0 :
[14:07:50.243] Msg->ulProtocolID: 0x00000005
[14:07:50.243] Msg->ulRxStatus: 0x00000000
[14:07:50.243] Msg->ulTxFlags: 0x00000800
[14:07:50.243] Msg->ulTimeStamp:          0
[14:07:50.243] Msg->ulDataSize: 12
[14:07:50.243] Msg->ulExtraDataIndex: 0
[14:07:50.243] Msg->ucData: 00 00 07 df 01 3e 00 00 00 00 00 00
[14:07:50.243] error: J2534_ERR_EXCEEDED_LIMIT
[14:07:50.243] *pulMsgID = 0
[14:07:50.243] [0x0000000c] J2534_ERR_EXCEEDED_LIMIT
[14:07:50.243] <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[14:07:54.899] DLL_PROCESS_DETACH TID = 0x00000fd0

Posts: 29
Joined: Tue Nov 26, 2019 5:29 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby PeterTremonti » Fri Oct 22, 2021 7:19 am

FriskyDingo wrote:Tonight I tried to connect to my buddies 2010 Silverado 4.8l with E38 ecm using a VCX Nano GM and it initialises ok recognizing the device as a bosch MDI but when I try to connect to the ecm I keep getting this error. I see a few posts mentioning problems with the vcx nano and this program, has anyone gotten it to work? The VM I was using was Windows 7.
Image


I see that you're using the GM version of the VCX Nano. Is it the wifi or cable only version? I'm curious how different each of the models are as I have the wifi version. I'd love to try out this software but i'm waiting on a BCM at the moment as my Yukon seems possessed at the moment. Can't communicate with anything and the dashboard thinks it's Christmas time already.
Available tools:
VCX Nano GM wifi (VXDIAG NANO-PLUS-V1.2 2020.10) (STM32F407 VTG6 ARM brand processor)
VAS 6154 Clone (VW6154-V1.0 1850) Looks like the VCX Nano but not as complicated.
Mongoose ISO/CAN
VAGcom HEX+CAN (HC8198369 Rev. B)
Maxidas DS708

User avatar
Posts: 25
Joined: Wed May 19, 2021 6:11 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby FriskyDingo » Fri Oct 22, 2021 7:20 am

PeterTremonti wrote:
FriskyDingo wrote:Tonight I tried to connect to my buddies 2010 Silverado 4.8l with E38 ecm using a VCX Nano GM and it initialises ok recognizing the device as a bosch MDI but when I try to connect to the ecm I keep getting this error. I see a few posts mentioning problems with the vcx nano and this program, has anyone gotten it to work? The VM I was using was Windows 7.
Image


I see that you're using the GM version of the VCX Nano. Is it the wifi or cable only version? I'm curious how different each of the models are as I have the wifi version. I'd love to try out this software but i'm waiting on a BCM at the moment as my Yukon seems possessed at the moment. Can't communicate with anything and the dashboard thinks it's Christmas time already.


It's the cable version but they're both the same minus a wifi module.

Posts: 51
Joined: Wed Feb 19, 2020 9:58 pm

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby daniel2345 » Wed Nov 03, 2021 6:12 am

Hi.

Im sorry not beeing around a while. We had a quite regular summer compared to the Corona Summer in 2020... So i had much more fun beeing outside with the Family and friends ;)

Last weekend we tested my friends G20 VAN with the LS3 and E67 after just standing still in the Garage for 8..9 months. i recognized some Bugs and made me some notes.

Also the log posted here Seems to be a good source for further debugging.

I will work on the Tool in the near future, probably dropping ELM Support...


So keep healthy, best regards, Daniel

Posts: 29
Joined: Tue Nov 26, 2019 5:29 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby PeterTremonti » Wed Nov 03, 2021 7:38 am

Welcome back! Glad you had a better summer this year. If I can help at all please let me know. I also have a VCX Nano to test with and an LMG on an E38. I'm not sure how much I can help, but I'm willing to try. I have a modified calibration to remove DOD ready to go but not a full BIN.
Available tools:
VCX Nano GM wifi (VXDIAG NANO-PLUS-V1.2 2020.10) (STM32F407 VTG6 ARM brand processor)
VAS 6154 Clone (VW6154-V1.0 1850) Looks like the VCX Nano but not as complicated.
Mongoose ISO/CAN
VAGcom HEX+CAN (HC8198369 Rev. B)
Maxidas DS708

User avatar
Posts: 25
Joined: Wed May 19, 2021 6:11 am

Re: PowerPCM_Flasher: my tool for E38 and E67

Postby FriskyDingo » Wed Nov 03, 2021 7:58 am

PeterTremonti wrote:Welcome back! Glad you had a better summer this year. If I can help at all please let me know. I also have a VCX Nano to test with and an LMG on an E38. I'm not sure how much I can help, but I'm willing to try. I have a modified calibration to remove DOD ready to go but not a full BIN.


If you need to do some logging like I did, open the VCX Log Manager app and click on the folder icon. It will open a folder then go to the "Logs" folder and then the PASSTHRU folder.
Image

PreviousNext

Return to Tools

Who is online

Users browsing this forum: No registered users and 3 guests