OVMS für den VW e-Up

[spoeh-man]

so habe die Firmware jetzt drauf meiner sagt jetzt immer dass er Standart charging macht mit -0.5km obwohl er nichtmal eingesteckt ist. Wenn ich das Laden aus der app stoppe pasiert folgendes

Code: Alles auswählen

I (495612) v-vweup: CommandStopCharge
I (495612) v-vweup: Charge turning OFF
E (495622) can: can3: intr=6421 rxpkt=6319 txpkt=104 errflags=0x80001080 rxerr=1 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=17 txfail=0 wdgreset=0 errreset=0
I (495622) v-vweup: Ring awake
I (499622) v-vweup: Sent Wakeup Command - stage 1
I (499722) v-vweup: Sent Wakeup Command - stage 2
I (499722) v-vweup: PollSetState: CHARGING -> CHARGING
I (499722) ovms-server-v2: Send MP-0 c12,0
I (500722) v-vweup: Profile0 request attempt 1...
I (500992) v-vweup: Profile0: 80 22 49 59 27 05 40 00
I (500992) v-vweup: Profile0: c0 01 00 06 00 10 64 ff
I (500992) v-vweup: Profile0: c1 ff 00 ff ff ff ff 01
I (500992) v-vweup: Profile0: c2 78 00 1e 1e 0a 00 00
I (500992) v-vweup: Profile0: c3 08 4f 70 74 69 6f 6e
I (500992) v-vweup: Profile0: c4 65 6e 00 00 00 00 00
I (500992) v-vweup: ReadProfile0: got mode: 6, charge_current: 16, cc_temp: 22
I (501992) v-vweup: Profile0 write attempt 1...
I (502262) v-vweup: ReadProfile0: got mode: 1, charge_current: 16, cc_temp: 22
I (502262) v-vweup: Profile0 value matches setting, ready to activate
I (502772) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:49:03.000+01:00) INFO: Standard charging
I (503592) webserver: HTTP GET /shell
I (507262) v-vweup: Profile0 switch attempt 1...
I (507262) v-vweup: Profile0 charge start attempt 1...
I (512262) v-vweup: Profile0 switch attempt 2...
I (512262) v-vweup: Profile0 charge start attempt 2...
I (512772) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:49:13.000+01:00) INFO: Standard charging
I (517262) v-vweup: Profile0 switch attempt 3...
I (517262) v-vweup: Profile0 charge start attempt 3...
I (522262) v-vweup: Profile0 switch attempt 4...
I (522262) v-vweup: Profile0 charge start attempt 4...
I (522792) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:49:23.000+01:00) INFO: Standard charging
I (527262) v-vweup: Profile0 switch attempt 5...
I (527262) v-vweup: Profile0 charge start attempt 5...
E (527262) v-vweup: Profile0 max. retries exceeded!
E (532262) v-vweup: Profile0_Retry_Callback in state PROFILE0_IDLE shouldn't happen!
E (532262) v-vweup: Profile0 max. retries exceeded!
I (532772) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:49:33.000+01:00) INFO: Standard charging
I (537862) v-vweup: Comfort CAN calls for sleep
I (537872) v-vweup: PollSetState: CHARGING -> CHARGING
I (540732) ovms-server-v2: Send MP-0 S76.5,K,0,0.00,charging,standard,198,129,16,532,0,0,2,1,0,1,0,0,120.00,66,0,0,80,-1,0,0,0,0,6,260,0,-0.17,331.25,0,0.00,0.00,0.50,-1.0
I (540742) ovms-server-v2: Send MP-0 D28,0,5,9.00001,2.9375,2.25,0,315280,0,49619,0,0,1,1,13.31,0,12.62,48,7,4.5,2
I (540742) ovms-server-v2: Send MP-0 L47.595757,7.790880,0,352.3,1,1,0.0,0,1,0.166,0.000,0.000,0,0,AA,11,0.9,0.0,100
I (542792) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:49:43.000+01:00) INFO: Standard charging
I (552772) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:49:53.000+01:00) INFO: Standard charging
I (562772) ovms-duk-util: [abrp.js:25:log] (2023-12-02 11:50:03.000+01:00) INFO: Standard charging
OVMS#

[sharkcow]

Danke für die Rückmeldung! Das hast du auch schon einen Bug gefunden: das "charge start attempt" sollte natürlich "charge stop attempt" heißen, habe ich gerade repariert und hochgeladen.

Wenn das Auto nicht eingesteckt ist, kann die "Ladung" natürlich nicht gestoppt werden, daher sind die erfolglosen 5 "switch" Versuche am Ende normal. Dein Profil hat er ja korrekt gelesen und auf Lade-Start/Stop-Modus gesetzt.

Was "Standard-Charging mit -0,5km" bedeutet weiß ich nicht. Ist das eine Funktion von Maps&More? Kann es sein, dass das einer deiner Ladetimer ist? Dann müssten wir herausfinden, warum er den versucht hat zu aktivieren...

[spoeh-man]

Also bis jetzt hat er mir das OVMS dass charging so nie angezeigt. Ich frage mich woher ovms meint dass geladen wird?. Kann ich deine neue version wieder OTA laden ?

Danke für die Rückmeldung! Das hast du auch schon einen Bug gefunden: das "charge start attempt" sollte natürlich "charge stop attempt" heißen, habe ich gerade repariert und hochgeladen.

Wenn das Auto nicht eingesteckt ist, kann die "Ladung" natürlich nicht gestoppt werden, daher sind die erfolglosen 5 "switch" Versuche am Ende normal. Dein Profil hat er ja korrekt gelesen und auf Lade-Start/Stop-Modus gesetzt.

Was "Standard-Charging mit -0,5km" bedeutet weiß ich nicht. Ist das eine Funktion von Maps&More? Kann es sein, dass das einer deiner Ladetimer ist? Dann müssten wir herausfinden, warum er den versucht hat zu aktivieren...

[sharkcow]

Ja, dexter aktualisiert ja alle 10min, die sollte also bei ihm live sein.

[spoeh-man]

Also dass OVMS meint immer noch dass eine Ladung stattfindet wenn ich diese stoppe kommt

Code: Alles auswählen

I (59664) v-vweup: CommandStopCharge
I (59664) v-vweup: Charge turning OFF
E (59684) can: can3: intr=12183 rxpkt=11959 txpkt=232 errflags=0x80001080 rxerr=1 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=33 txfail=0 wdgreset=0 errreset=0
I (59684) v-vweup: Ring awake
I (59684) v-vweup: ODB AWAKE ist still blocked
I (62754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:07:53.000+01:00) INFO: Standard charging
I (63674) v-vweup: Sent Wakeup Command - stage 1
I (63774) v-vweup: Sent Wakeup Command - stage 2
I (63774) v-vweup: PollSetState: CHARGING -> CHARGING
I (63774) ovms-server-v2: Send MP-0 c12,0
I (64714) powermgmt: Charging 12V battery..
I (64714) ovms-server-v2: Send MP-0 D28,0,5,9.00001,0.921875,1.5,0,315280,0,61498,0,0,1,1,13.3,0,12.65,48,4,5.5,2
I (64774) v-vweup: Profile0 request attempt 1...
I (65034) v-vweup: Profile0: 80 22 49 59 27 05 40 00
I (65044) v-vweup: Profile0: c0 01 00 01 00 10 64 ff
I (65044) v-vweup: Profile0: c1 ff 00 ff ff ff ff 01
I (65044) v-vweup: Profile0: c2 78 00 1e 1e 0a 00 00
I (65044) v-vweup: Profile0: c3 08 4f 70 74 69 6f 6e
I (65044) v-vweup: Profile0: c4 65 6e 00 00 00 2e 40
I (65044) v-vweup: ReadProfile0: got mode: 1, charge_current: 16, cc_temp: 22
I (65044) v-vweup: Profile0 value matches setting, ready to activate
I (65714) ovms-server-v2: Send MP-0 S76.5,K,0,0.00,charging,standard,198,129,16,12412,0,0,2,1,0,1,0,0,120.00,66,0,0,80,-1,0,0,0,0,6,260,0,-0.17,331.00,0,0.00,0.00,0.50,-1.0
I (70044) v-vweup: Profile0 switch attempt 1...
I (70044) v-vweup: Profile0 charge stop attempt 1...
I (72764) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:08:03.000+01:00) INFO: Standard charging
I (75044) v-vweup: Profile0 switch attempt 2...
I (75044) v-vweup: Profile0 charge stop attempt 2...
I (75714) ovms-server-v2: Send MP-0 S76.5,K,0,0.00,charging,standard,198,129,16,12422,0,0,2,1,0,1,0,0,120.00,66,0,0,80,-1,0,0,0,0,6,260,0,-0.17,331.00,0,0.00,0.00,0.50,-1.0
I (75724) ovms-server-v2: Send MP-0 D28,0,5,9.00001,0.921875,1.5,0,315280,0,61509,0,0,1,1,13.3,0,12.65,48,4,7.5,2
I (75724) ovms-server-v2: Send MP-0 L47.595753,7.790983,0,364.8,1,1,0.0,0,1,0.166,0,0,0,0,AA,12,0.8,0.0,100
I (80044) v-vweup: Profile0 switch attempt 3...
I (80044) v-vweup: Profile0 charge stop attempt 3...
I (82754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:08:13.000+01:00) INFO: Standard charging
I (85044) v-vweup: Profile0 switch attempt 4...
I (85044) v-vweup: Profile0 charge stop attempt 4...
I (86734) cellular: Network Provider is: Telekom.de Hologram
I (90044) v-vweup: Profile0 switch attempt 5...
I (90044) v-vweup: Profile0 charge stop attempt 5...
E (90044) v-vweup: Profile0 max. retries exceeded!
I (92754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:08:23.000+01:00) INFO: Standard charging
E (95044) v-vweup: Profile0_Retry_Callback in state PROFILE0_IDLE shouldn't happen!
E (95044) v-vweup: Profile0 max. retries exceeded!
I (101054) v-vweup: Comfort CAN calls for sleep
I (101054) v-vweup: PollSetState: CHARGING -> CHARGING
I (102754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:08:33.000+01:00) INFO: Standard charging

[spoeh-man]

Dass Passiert beim starten der Klima

Code: Alles auswählen

I (408814) v-vweup: CommandHomelink button=1 durationms=1000
I (408814) v-vweup: CommandClimateControl turning ON
E (408824) can: can3: intr=27088 rxpkt=26582 txpkt=513 errflags=0x80001080 rxerr=1 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=74 txfail=0 wdgreset=0 errreset=0
I (412754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:13:43.000+01:00) INFO: Standard charging
I (412824) v-vweup: Sent Wakeup Command - stage 1
I (412924) v-vweup: Sent Wakeup Command - stage 2
I (412924) v-vweup: PollSetState: CHARGING -> CHARGING
I (412924) ovms-server-v2: Send MP-0 c24,0
I (413924) v-vweup: Profile0 request attempt 1...
I (414194) v-vweup: Profile0: 80 22 49 59 27 05 40 00
I (414194) v-vweup: Profile0: c0 01 00 01 00 10 64 ff
I (414194) v-vweup: Profile0: c1 ff 00 ff ff ff ff 01
I (414194) v-vweup: Profile0: c2 78 00 1e 1e 0a 00 00
I (414194) v-vweup: Profile0: c3 08 4f 70 74 69 6f 6e
I (414194) v-vweup: Profile0: c4 65 6e 6e 0f 6b 80 00
I (414194) v-vweup: ReadProfile0: got mode: 1, charge_current: 16, cc_temp: 22
I (415194) v-vweup: Profile0 write attempt 1...
I (415464) v-vweup: ReadProfile0: got mode: 6, charge_current: 16, cc_temp: 22
I (415464) v-vweup: Profile0 value matches setting, ready to activate
I (420464) v-vweup: Profile0 switch attempt 1...
I (420464) v-vweup: Profile0 climatecontrol start attempt 1...
I (421724) ovms-server-v2: Send MP-0 D28,0,5,9.00001,0.96875,1.5,0,315280,0,61855,0,0,1,1,14.25,0,12.65,176,5,5.25,2
I (422754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:13:53.000+01:00) INFO: Standard charging
I (425464) v-vweup: Profile0 switch attempt 2...
I (425464) v-vweup: Profile0 climatecontrol successfully turned ON

[spoeh-man]

und dass bei Klima aus

Code: Alles auswählen

I (509614) v-vweup: CommandHomelink button=0 durationms=1000
I (509614) v-vweup: CommandClimateControl turning OFF
I (509614) ovms-server-v2: Send MP-0 c24,0
I (510614) v-vweup: Profile0 request attempt 1...
I (510884) v-vweup: Profile0: 80 22 49 59 27 05 40 00
I (510884) v-vweup: Profile0: c0 01 00 06 00 10 64 ff
I (510894) v-vweup: Profile0: c1 ff 00 ff ff ff ff 01
I (510894) v-vweup: Profile0: c2 78 00 1e 1e 0a 00 00
I (510894) v-vweup: Profile0: c3 08 4f 70 74 69 6f 6e
I (510894) v-vweup: Profile0: c4 65 6e 6e 0f 6b 80 00
I (510894) v-vweup: ReadProfile0: got mode: 6, charge_current: 16, cc_temp: 22
I (510894) v-vweup: Profile0 value matches setting, ready to activate
I (511714) ovms-server-v2: Send MP-0 D28,0,5,9.00001,1.01562,1.5,0,315280,0,61945,0,0,1,1,14.76,0,12.65,48,5,8.25,2
I (512754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:15:23.000+01:00) INFO: Significant telemetry change
I (512754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:15:23.000+01:00) INFO: Sending telemetry to ABRP {"utc":1701526523,"soc":76,"power":0,"speed":0,"lat":47.5958,"lon":7.79095,"is_charging":true,"is_dcfc":false,"is_parked":true,"kwh_charged":0,"soh":0,"heading":0,"elevation":358.2,"ext_temp":0,"batt_temp":2,"voltage":330,"current":0,"odometer":31528,"est_battery_range":198}
I (515894) v-vweup: Profile0 switch attempt 1...
I (515894) v-vweup: Profile0 climatecontrol successfully turned OFF

[sharkcow]

OK, Klima funktioniert (bitte mal checken ob deine Ladetimer unverändert geblieben sind).

Die Ladedetektion hab ich aber wohl verschlimmbessert... Kannst du in der Shell mal bitte eingeben:

Code: Alles auswählen

log level verbose canlog-monitor
can log start mon crtd 3:61C
wakeup

und dann posten was auf dem CAN kommt?

Danke!

[spoeh-man]

da kommt

Code: Alles auswählen

CAN logging to MONITOR active: Type:monitor Format:crtd(discard) Filter:3:61c  Vehicle:VWUP
Note: info logging is at debug log level, frame logging is at verbose, and errors as usual
I (845604) canlog-monitor: Now logging CAN messages to monitor
D (845604) canlog-monitor: 1701526856.104685 CXX OVMS CRTD
……: 1701526856.104685 CVR 3.1
I (852764) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:21:03.000+01:00) INFO: Standard charging
I (862754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:21:13.000+01:00) INFO: Standard charging
I (864214) webserver: HTTP POST /api/execute
I (864214) webcommand: HttpCommandStream[0x3f8b8b14]: 3466012 bytes free, executing: wakeup
E (864224) can: can3: intr=72894 rxpkt=71540 txpkt=1360 errflags=0x80001080 rxerr=1 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=198 txfail=0 wdgreset=0 errreset=0
E (864224) canlog-monitor: 1701526874.725450 3CER Error intr=72894 rxpkt=71540 txpkt=1360 errflags=0x80001080 rxerr=1 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=198 txfail=0 wdgreset=0 errreset=0
I (864224) v-vweup: Ring awake
V (864554) canlog-monitor: 1701526875.050756 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (865554) canlog-monitor: 1701526876.050570 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (866554) canlog-monitor: 1701526877.050671 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (867554) canlog-monitor: 1701526878.050588 3R11 61C 00 f0 0f 00 fe 03 00 0d
I (868214) v-vweup: Sent Wakeup Command - stage 1
I (868314) v-vweup: Sent Wakeup Command - stage 2
OVMS# wakeup
Vehicle has been woken
I (868314) v-vweup: PollSetState: CHARGING -> CHARGING
V (868554) canlog-monitor: 1701526879.050444 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (869554) canlog-monitor: 1701526880.050400 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (870554) canlog-monitor: 1701526881.050405 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (871554) canlog-monitor: 1701526882.050352 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (872554) canlog-monitor: 1701526883.051590 3R11 61C 00 f0 0f 00 fe 03 00 0d
I (872754) ovms-duk-util: [abrp.js:25:log] (2023-12-02 15:21:23.000+01:00) INFO: Standard charging
V (873554) canlog-monitor: 1701526884.050571 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (874554) canlog-monitor: 1701526885.050382 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (875554) canlog-monitor: 1701526886.050393 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (876554) canlog-monitor: 1701526887.051542 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (877554) canlog-monitor: 1701526888.050208 3R11 61C 00 f0 0f 00 fe 03 00 0d
V (878554) canlog-monitor: 1701526889.050225 3R11 61C 00 f0 0f 00 fe 03 00 0d
I (879414) v-vweup: Comfort CAN calls for sleep
I (879414) v-vweup: PollSetState: CHARGING -> CHARGING

[sharkcow]

OK, da scheint deine Karre anders zu sein als meine, die Lade-Bytes sind anders. Ich hoffe mal das liegt daran dass ich das alte Modell mit kleinem Akku habe...

Habe das mal im Code geändert, bitte nochmal testen (evtl. noch 10min warten bis Dexter aktualisiert hat).