Universalpatcher with Logger & Analyzer

[Vampyre Profile]

thanks kur4o i was over complicating it and trying to fill in every field in j-console

[kur4o Profile]

Not all fields are needed, but some are very handy in other situations.

To open gmlan on pin1

set protocol->SW_CAN_PS
baud->33333
set pins->00000100 [setting is 0000xxyy xx=primary pin number in hex yy =secondary pin number in hex]

Usually when a protocol have _PS added[means=pin select it needs pins specified.

If the tool support pin configuration you can open high speed CAN on different than standard pins 7&14.

ON gm pcm and a good tool[mdi tested] you can monitor at the same time 2 protocols.

First set protocol1 ->connect than set protocol2 ->connect

tested on high and low speed can and all kind of other protocols.

[Vampyre Profile]

got nodda

[kur4o Profile]

The script you are trying to run is for class2 pcm, not sure why it crash, it may not like the message format.

Here is some other script that is for CAN ecm. you can give it a try.

[Vampyre Profile]

stillnodda.JPG (95.76 KiB) Viewed 329 times

yeah no idea what im doing wrong

ok so say I have everything plugged into my car and all i want to do is read and monitor the bus, how would i set the profile?

[kur4o Profile]

I can only guess you are using a vpw vehicle and try to connect to it via CAN, since there is no data comming after you connect to CAN.

You can use vpw console[tab]->connect mdi from settings got to vpw console tab mark all checkboxes and you should see data flowing, than you can send scripts and custom commands. I see battery voltage read is almost as zero. could be the mdi is not powered from obd2 connector.

[Vampyre Profile]

ive got it on my table hooked up to a e38 with a y splitter harness while programming, yeah my second obd plug isnt powered. i will power it and see what happens

[kur4o Profile]

Without bus power mdi will likely not log anything.

Here are some commands to use with e38, The one you tested works only on class-2[vpw] modules. CAN uses slightly different format.

this one will quiet modules on bus

00 00 01 01 FE 01 28

this is to keep bus quiet, the equivalent of vpw 3f message
00 00 01 01 FE 01 3E

to request key send this
00 00 07 E2 02 27 01 FF FF FF FF FF

to send key use
00 00 07 E2 04 27 02 [xx xx] FF FF FF ;xxxx=key

[Gampy]

I have found JConsole quits working if you connect/disconnect while trying different settings and you have to restart the logger to get it working again ...

-Enjoy

[kur4o Profile]

Hi, Gampy

Thanks for testing the logger, Can you give some more details about the conditions.
I may need program version protocol being used , type of changes being used. j-device being used.

I did some testing but current logic on changing protocol settings, should first disconnect[on button pressed] and than a manual connection should be done. Maybe it can get auto[connect/disconnect] later.