Beiträge von rui.saraiva
-
-
The e-208 has 109ps (80 kW), 210 Nm in normal drive mode. The 136ps (100 kW), 260 Nm are only available in Sport mode - and 82ps (60 kW), 190 Nm in Eco mode.
-
I'm assuming the first step "First install the firmware 42.03.33.42_NAC-r0 for NAC Wave 3 (UpdateID 00131503*)" had been done
Yes, that is clear. What I meant is, that after installing this version in a Wave3, I always became an error when trying to update it to a newer 4x.xx firmware version.
Do you have the VIN of any of those? Does the Majestic API return "NAC_EUR_WAVE4" as the ecuType after the 42.03.33.42_NAC-r0 update (Wave 3 to Wave 4) and before the update to a newer 4*.*.*.*?
-
edu_chirimoya I'm assuming the first step "First install the firmware 42.03.33.42_NAC-r0 for NAC Wave 3 (UpdateID 00131503*)" had been done. The Wave 4 specific versions only have this:
Code<EcuCompatibilityList> <EcuType>NAC_EUR_WAVE4</EcuType> <EcuType>NAC_EUR_WAVE4_B0</EcuType> </EcuCompatibilityList>
For instance, all the 67.*.*.* NAC AIO versions have both the "NAC_AIO_LATAM_WAVE1" and "NAC_AIO_LATAM_WAVE2" ecuTypes and you can do that direct conversion.
-
Code
{"vin":"VR7ECYHZRJJ883144","requestDate":"2023-08-01T02:58:58+0200","devices":[{"ecuType":"NAC_EUR_WAVE3"}]}
You don't need the TomTom traffic subscription to update maps or firmware, they are always free. In your case, with a obsolete NAC Wave 3, you first need to update the firmware to NAC Wave 4 and then use the maps for that Wave level. First install the firmware 42.03.33.42_NAC-r0 for NAC Wave 3 (UpdateID 00131503*) and ignore the European map (UpdateID 00231501*) included in the bundle. Then install the European map 14.0.0-r0 for NAC Wave 4 (released in Feb 2023). Optionally, you could upgrade the firmware to the latest NAC Wave 4, 44.07.05.22_NAC-r0.
-
-
edu_chirimoya AFAIK that only disables the alerts, and those doesn't work anyway...
-
Install a ferrite core in the cable, near the rear camera.
-
Probably, but I don't have that file here and it isn't available any more...
The "new" one has a SHA256 digest of: 30269fb41828510b2a69601f503e2f769b744be5b3498337741221726366efd0
BTW, delete that URL from your post, it links to unreleased/pre-prod versions...
-
Peugeot Update (Majestic API) returns the wrong URL
Codeds4emloty3shq.cloudfront.net/continental/NAC_EU/ovip-int-firmware-version/PSA_ovip-int-firmware-version_44-07-05-22_NAC-r0_NAC_EUR_WAVE4.tar
, the correct one is
Codeds4emloty3shq.cloudfront.net/CONTINENTAL/NAC_EU/ovip-int-firmware-version/PSA_ovip-int-firmware-version_44-07-05-22_NAC-r0_NAC_EUR_WAVE4.tar
Update has 6 312 099 840 bytes
-
There's a CD player for the 3008/5008 II on the accessories list, part number 1627155180. The frame is 98118828ZD. A CD player through USB doesn't work.
-
Here's a RCC Wave 3, "B" version: https://www.forum-peugeot.com/…sion.128392/#post-2668366
-
And no, it's not showing up in the "app overview".
Then you might have to get it activated.
Was sagt deine Firmwareversion? 0xxA, 0xxC oder 0xxD?
There's also the very rare "B" version, without GNSS but with DAB support.
-
Because the Majestic API doesn't know your current version 5_096_20.0H022.23- and all software that use that API (MyPeugeot, Peugeot Update and the Mittns Toolbox).
In the previous screen of that menu, you should see system version "096x".
BTW, what is that letter "x" (it should be A, B, C or D - the hardware subversion)?
Also if you see the tooltip of the latest version in my RCC Wave 3 page - https://sites.google.com/view/nac-rcc/system/rcc/wave-3 - you see that all versions (HMI, iMX and V850) are identical to your versions:
HMI: rcc2022.82.22.16.00
iMX: x0601048_220427_20.0H022.23
V850: RCC19_19.1S18.15
You might have to telecode your RCC to enable AA.
-
-
Hey edu_chirimoya!
European map 25.0.0-r0 for NAC Wave 2 has just been released.
-
Arminius : Anyone with the correct URL can download it... But, yes, it isn't publicly available.
-
Yes, version 25.0.0-r0 is in pre-production:
-
Mittns : There's also this: https://github.com/COVESA/dlt-viewer
But you have to compile it and it uses the Qt toolkit.
Edit: It seems they also release the binary, some time ago only the source code was available.
I just use grep with regexps, the timestamp has a fixed format
-
The "incompatible hardware" is a generic error, you need to read the car spylogs that gives much more information.
Right after the error, press and hold the vehicle logo button to create a new spylog entry. The .dlt files are in standard Diagnostic Log and Trace format, that you could read with the Visual Studio Code and the DLT-Logs extension for instance.