Hexnet functionality suggestion - standard measuring blocks

[burpod]

i have a suggestion that i would LOVE to see implemented - shouldn't be much effort i would think.

for hexnet/wifi VCDS over the browser - could the standard measuring blocks be made available? as far as i can tell, advanced measuring values is just a wrapper around standard measuring blocks - since only communication for data to the ecu is done with these (it's in the tune).

i define my own measuring blocks so i can get better data logging while maintaining the best possible sample rate. for normal VCDS with standard measuring blocks this is fine, because i know what blocks are what, and i can modify the LBL files so the data field names are correct which is nice. but with advanced measuring values, i don't see a way to change this, and makes logging with hexnet a pain because now i can't get the data logged that i want. eg, "fuel consumption" is now no longer fuel consumption. i want to log 011-014-015 as defined in the tune, but this seems to be impossible as it currently works.

please?

 

[Uwe]

as far as i can tell, advanced measuring values is just a wrapper around standard measuring blocks -

On non/pre-UDS modules, in VCDS on a PC, that is correct. But by the time we started developing VCDS-Mobile, it was clear that all newly developed control modules would henceforth be using UDS, which doesn't support Measuring Blocks at all. Thus Advanced Measuring Values is never a "wrapper" in VCDS-Mobile; it's the native way of doing things.

There should be some way to get the three "blocks" you want in VCDS-Mobile anyway. However, I don't have any old-school, non-UDS things handy to play with where I am at the moment. @Shaun may have some suggestions.

-Uwe-

 

[burpod]

ok. i guess i'm thinking mk4 BEW and ALH only - those are the only cars i ever deal with. i haven't really done anything with CR or gas cars.

so am i correct that for k-line mk4 tdi alh/bew cars - advance measuring values would be a wrapper around the standard measuring blocks?

thanks

 

[Uwe]

so am i correct that for k-line mk4 tdi alh/bew cars - advance measuring values would be a wrapper around the standard measuring blocks?

In VCDS, yes, In VCDS-Mobile, no.

FWIW, early CR ECUs did not use UDS either. UDS is always on CAN, so K-Line means no UDS, but CAN doesn't automatically mean UDS. CAN can still be KWP-2000, generally over TP2.0, but in some rare cases, it can be KW1281 over TP1.6! If you find this confusing, don't worry about it.

-Uwe-

 

[Shaun]

If I understand correctly, you are wanting to manually view a block by group number in a non-UDS controller? You can do this by typing the number like "11" into the search field on the measuring values selection page and then hit [submit] it should manually pull up the group even if that group is not displayed in the list.

 

[burpod]

i tried that and it doesn't work.

i simply want to be able to just log measuring blocks (as defined in edc15/edc16) by their number, not picking out of a list of pre-defined fields. so i have blocks i've defined that don't exist "stock" and changed some measuring blocks from stock. so for exmaple i have blocks defined:

014: IQ, pump voltage, spec timing, actual timing
015: IAT, coolant temp, speed, consumption

so i want to be able to log 011-014-015 with hexnet just like i would normally with regular vcds over kwp1281

 

[Shaun]

So what happens when you type 14 in the field and click submit?

 

[burpod]

i get some data for pump voltage and timing, but they're not the right fields that i have in my 014 block. i try 18 (i have an 018 block defined) and get nothing, same for the other blocks i define

 

[Shaun]

It sounds like maybe this isn't compatible with your tune. If you want to make a debug log for one of the blocks that's not working, say 18, the process would be like this: [Options] -> debug level:001f [Submit] then go to measuring values, put 18 in the field as described above and [Submit], let that run for a minute to make the log. Back out and go to [View Saved Files] and make sure that debug log is synced to cloud, then send us the docid. I will take a look at what is going on here, but I make no promises that this can be supported.

 

[burpod]

It sounds like maybe this isn't compatible with your tune. If you want to make a debug log for one of the blocks that's not working, say 18, the process would be like this: [Options] -> debug level:001f [Submit] then go to measuring values, put 18 in the field as described above and [Submit], let that run for a minute to make the log. Back out and go to [View Saved Files] and make sure that debug log is synced to cloud, then send us the docid. I will take a look at what is going on here, but I make no promises that this can be supported.

thanks, i'll try that. although my suggestion of functionality is fairly simple i thought - i just would like to see a "measuring block" functionality like there is with regular vcds (like on alh/bew/etc edc15/edc16 and probably other ecus) on the hexnet web form. so there would be the "advanced measuring values" working as it is, and then a "measuring blocks" button with just a listing of the blocks as determined by the LBL files. make sense?

 

[Shaun]

If entering the measuring block manually with the existing interface does not work, then there is an underlying problem perhaps with the way the interface is processing these values or perhaps a general communications issue with this control module. Presenting this info with a different user interface would not fix the underlying issue, first we must understand why those measuring blocks don't display correctly with mobile. If you make a debug log, I can take a look at this, but again since we are talking about a tuned module there is also the chance the module itself is doing something non-standard. I do not promise to be able to support this, but I will take a look.

 

[Andy]

FYI, I have a BEW ECU on my test bench: 038 906 016 H

As far as I know it's stock. I get no data from 014 in VCDS, just blank fields:

Monday,08,April,2024,14:10:49:29905
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 23.11.0.0 (x64)  HEX-NET CB: 0.4648.4
Data version: 20231027 DS351.0
www.Ross-Tech.com


VIN: 9BWFR61J044030906   License Plate:



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


                Address 01: Engine  (038 906 016 H)

14:10:47 Group 014
     
     
     
     

14:10:47 Group 018: Piezo Unit Injector Status
  128.0  Injector Status Cylinder 1
  128.0  Injector Status Cylinder 2
  128.0  Injector Status Cylinder 3
  128.0  Injector Status Cylinder 4

Here's a snippet from 015 using VCDS-Mobile:

Mon,Apr,08,2024,14:05:09 -VCID:19754E6780D1A3A3DDEF3E-51A8,VCDS Mobile: 0.4648
038 906 016 H,ADVMB,R4 1,9L EDC 0010AG   6327,
,,G015,F0,G015,F1,G015,F2,G015,F3,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,G000,F0,

Marker,TIME,Group 15 - Field 0,TIME,Group 15 - Field 1,TIME,Group 15 - Field 2,TIME,Group 15 - Field 3,,,,,,,,,,,,,,,,,
,STAMP,Engine Speed (G28),STAMP,Engine Torque ,STAMP,Fuel Consumption,STAMP,Torque Request (Driver),,,,,,,,,,,,,,,,,
,, /min,, Nm,, l/h,, Nm,,,,,,,,,,,,,,,,,
,1.59,0,1.59,242.0,1.59,0.00,1.59,112.0,,,,,,,,,,,,,,,,,
,1.79,0,1.79,242.0,1.79,0.00,1.79,112.0,,,,,,,,,,,,,,,,,
,2.00,0,2.00,242.0,2.00,0.00,2.00,112.0,,,,,,,,,,,,,,,,,
,2.20,0,2.20,242.0,2.20,0.00,2.20,112.0,,,,,,,,,,,,,,,,,
,2.40,0,2.40,242.0,2.40,0.00,2.40,112.0,,,,,,,,,,,,,,,,,

In VCDS-Mobile, I can only pick from groups that are defined in the 038-906-016-BEW label file (which skips from 013 to 015). @burpod Can you please provide an AutoScan or a log file from the vehicle so we can see what label is being used and whether it could use revising?

Edit: Also please email channel maps from each engine controller using these steps in VCDS:

Ross-Tech: VCDS Tour - Controller Channels Map