pcmhacking.net

latest logs

24b max 128b max 192b max 216b max again, could be still a power issue so next is to set up a battery supplying power, and or completely tearing apart bench harness and rebuilding to be sure there is absolutely no issues there, but cannot find anything in harness that seems like bad connections or bad grounds.

Cincinnatus wrote:Gampy, that link to modify the code on github seems like the key to pandora's box. I played around there, but having no experience with github or software development I'll wait until you get your godiag and test with hammer. I assume there's no folder on my PC that would permit changes to the buffer limits for hammer?

I would say it is pandora's box, and these are the ingredients to create the key to it ...

To modify and build the PCMHammer Suite you'll need, Microsoft Visual Studio (Community edition is fine) and .NET Framework v4.6.1 installed.

To build the kernels, you'll need GNU-m68k toolchain for Windows installed to C:\SysGCC
You can just grab them from a release version unless it's the Kernels specifically you're wanting to modify.

This How to Git with PcmHacks in Visual Studio might be helpful.

Building the PCM Hammer Suite is done within Visual Studio.
Building the PCM Hammer Kernel is done from the Command Prompt. (Or browse to and click, YUK)
1. Open a Command prompt.
2. Change to the PcmHacks\Kernels directory.
3. Type .\BuildAll.cmd

Modifying source code through the Github web interface is not available ...

No place to change the Buffer size in PCMHammer without recompiling.

@99zguy, I do not know if you have bad power or not, that's just it, we do not know ... And until you get a good read with a specific VCI, you will not know unless of course you have an oscilloscope to check the quality of power.
At least that's what I think one would use to test power condition?

I thought my godiag would have been here by now ... It's not!

-Enjoy

So recieved another reply from GoDiag. They of course will not produce firmware for the device as it is intellectual property. Go figure. Nor will they send any build sheets ect. Though, they are claiming that they will have the VPW issue corrected within a month. Shall see if they follow thru and if it will be a firmware upgrade or juat release of another device. So there is that.

Maybe try a smaller size, like 2, 4 or 6 bytes. See if it still errors out.

@Tazzi Here is log at 6 bytes. Still failing.

99zguy wrote:@Tazzi Here is log at 6 bytes. Still failing.

PcmHammer_debugLog_20230117@092056_6b_1x.txt

Its technically getting a response... but.. its being refused.

[09:20:19:208] TX: 6D 10 F0 36 00 00 06 FF 9E CC 4F EF 00 20 4E 75 04 90
[09:20:19:690] RX: 6C F0 10 7F 36 00 00 06 FF 9E 22

Code $22 - Conditions Not Correct or Request Sequence Error

DO you have another tool to monitor the bus. The nano migth not send, what needs to send. Only bus monitoring will debug the non working conditions.

I agree, this is likely a truncated packet being rejected.

antus wrote:I agree, this is likely a truncated packet being rejected.

^^I think your onto it here.

I don't think the device is able to send packets over the indicated J1850 standard size.

Tazzi wrote:the indicated J1850 standard size.

And may I ask what that is ??

-Enjoy