[Ovmsdev] VEHICLE_POLL_TYPE_READSCALING @ VWUP.OBD

[Soko]

Ohhh... :(

So I really have to simulate the VW e-Up with OVMS for VCDS so I can see 
how the values translate.

I've already tried that but as soon as I unplug the Y-cable from the car 
VCDS says "Steuergerät reagiert nicht".

So I've ordered another OBD-cable-extension. I plan to put a hardware 
switch on the 2 CAN wires so I can just disconnect the CAN pins.

As VCDS is trying to read the values fast (10 times a second) I'm 
certain I cannot type that fast...

Is there an easy way in OVMS where I can store a list responses to the 
messages VCDS is sending and OVMS will send them back?

Any suggestions?

Thanks

Soko

On 08.09.2020 21:09, Michael Balzer wrote:
> Soko,
>
> you misinterpreted the error response: 7F is just the general error
> response type. The actual error code was 11 for all your attempts.
>
> See Annex A.1: 0x11 = …
>> serviceNotSupported
>> This response code indicates that the requested action will not be
>> taken because the
>> server does not support the requested service.
> So you've got no luck, the device doesn't support ReadScaling.
>
> Regards,
> Michael
>
>
> Am 08.09.20 um 19:53 schrieb Soko:
>> Hi,
>>
>> I've tried the new poller type "ReadScaling" with no luck.
>>
>> First I've tried it for the BatteryManager ECU (7E5) and the
>> voltage-PID (1E3B)  which should deliver just a division by 4 as
>> formula for the scaling:
>>
>> D (57865) vehicle: PollerSend(1): send [bus=1, type=24, pid=1E3B],
>> expecting 7e5/7ed-7ed
>> V (57865) canlog-monitor: 1599579609.443101 1T11 7E5 03 24 1e 3b 00 00
>> 00 00
>> V (57875) canlog-monitor: 1599579609.453040 1R11 7ED 03 7f 24 11 aa aa
>> aa aa
>> D (57875) vehicle: PollerReceive[7ED]: process OBD/UDS error 24(1E3B)
>> code=11
>>
>> So 7F is "serviceNotSupportedInActiveSession" as far as I can tell. So
>> I did swap to the Charger ECU (744) with efficiency-PID (15D6) and
>> loss-PID (15E1) as I'm already have there a extended diag session
>> working:
>>
>> EXTENDED DIAG SESSION:
>> D (24865) vehicle: PollerSend(1): send [bus=1, type=10, pid=3],
>> expecting 744/7ae-7ae
>> V (24865) canlog-monitor: 1599581491.143704 1T11 744 02 10 03 00 00 00
>> 00 00
>> V (24865) canlog-monitor: 1599581491.144423 1R11 7AE 06 50 03 00 32 01
>> f4 00
>> D (24865) vehicle: PollerReceive[7AE]: process OBD/UDS response 10(3)
>> frm=0 len=4 off=0 rem=0
>>
>> READING EFFICIENCY VALUE:
>> D (24865) vehicle: PollerSend(0): send [bus=1, type=22, pid=15D6],
>> expecting 744/7ae-7ae
>> V (24865) canlog-monitor: 1599581491.147379 1T11 744 03 22 15 d6 00 00
>> 00 00
>> V (24875) canlog-monitor: 1599581496.164030 1R11 7AE 04 62 15 d6 fe 74
>> 09 00
>> D (24875) vehicle: PollerReceive[7AE]: process OBD/UDS response
>> 22(15D6) frm=0 len=1 off=0 rem=0
>>
>> TRY READ SCALING FOR EFFICIENCY:
>> D (24875) vehicle: PollerSend(0): send [bus=1, type=24, pid=15D6],
>> expecting 744/7ae-7ae
>> V (24875) canlog-monitor: 1599581491.158798 1T11 744 03 24 15 d6 00 00
>> 00 00
>> V (24885) canlog-monitor: 1599581491.164311 1R11 7AE 03 7f 24 11 ae 74
>> 09 00
>> D (24885) vehicle: PollerReceive[7AE]: process OBD/UDS error 24(15D6)
>> code=11
>>
>> READING LOSS VALUE:
>> D (24885) vehicle: PollerSend(0): send [bus=1, type=22, pid=15E1],
>> expecting 744/7ae-7ae
>> V (24885) canlog-monitor: 1599581491.165854 1T11 744 03 22 15 e1 00 00
>> 00 00
>> V (24895) canlog-monitor: 1599581491.174851 1R11 7AE 04 62 15 e1 00 74
>> 09 00
>> D (24895) vehicle: PollerReceive[7AE]: process OBD/UDS response
>> 22(15E1) frm=0 len=1 off=0 rem=0
>>
>> TRY READ SCALING FOR LOSS:
>> D (24895) vehicle: PollerSend(0): send [bus=1, type=24, pid=15E1],
>> expecting 744/7ae-7ae
>> V (24895) canlog-monitor: 1599581491.178916 1T11 744 03 24 15 e1 00 00
>> 00 00
>> V (24905) canlog-monitor: 1599581491.184240 1R11 7AE 03 7f 24 11 ae 74
>> 09 00
>> D (24905) vehicle: PollerReceive[7AE]: process OBD/UDS error 24(15E1)
>> code=11
>>
>> It still says 7F :(
>>
>> Do I do something wrong here? Any suggestions?
>>
>> Thanks
>>
>> Soko
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev