Das Blöde an der Sache ist ehr, dass die es nicht schaffen, kleine Updates rauszubringen, es wird immer die komplette Firmware installiert...
There are firmware patches in use for RCC_AIO_LATAM and NAC_AIO_LATAM systems - here's one: https://drive.google.com/file/…1g6SHrzt/view?usp=sharing (940KB). They should also work in the European RCC and NAC versions.
Ist kein Fehler, ich durchlaufe eine Schleife, die nur die Erste Zahl einer Version betrifft.
Bisher war ja nie eine 2. Stelle der Version notwendig.
Das implementiere ich dann später.
I did try that (also with(out) the "-r0" and the old "PxCNS" URL ) some time ago and I'm pretty sure I've found all map versions. NAC Wave 2 had "4.0.2" for instance - https://sites.google.com/view/nac-rcc/system/nac/wave-2 or Wave 3 "6.3.0-r0" - https://sites.google.com/view/nac-rcc/system/nac/wave-3
You could also use the "getUpdateStatus" from Majestic's API if you don't want to fill the TomTom webserver logs (it's akamai anyway)... 
Alles anzeigenOk, das kann ich verstehen.
Ich weiß aber auch nicht, warum immer noch bei so vielen Geräten auf FAT32 gesetzt wird. Ich vermute mal, daß die Software unter Linux o.ä. läuft. Da gibt es doch genügend Dateisysteme, die keine Probleme mit Partitionen >32GB haben, selbst exFAT und NTFS.
Erfahrungsgemäß werden Kartenupdates im Laufe der Zeit immer größer.
Schön, daß Dein Tool so oft genutzt wird.
Yes, the system is Linux based (GENIVI, it isn't Ubuntu related) and also have the NTFS and the "default" Linux filesystems (ext2/3/4) support in the kernel (modules in /lib/modules/*/kernel/fs/), but those filesystems were explicit excluded from USB flash drives (from /etc/udev/rules.d/50-mount-usb.rules):
# max_sectors configures the max. amount of transferred data. Most manufacturers
# test against WinXP, which uses "64" and therefore should be very stable.
ACTION=="add", SUBSYSTEMS=="scsi", ATTR{max_sectors}=="240", ATTR{max_sectors}="64"
KERNEL!="sd[a-z]*", GOTO="auto_mount_end"
# Set environment
ACTION=="add", IMPORT{program}="/usr/bin/timeout -t 10 /sbin/blkid -o udev -p %N"
# If the device is not a filesystem, skip
ENV{ID_FS_USAGE}!="filesystem", GOTO="auto_mount_end"
# WAVE 1 : FAT16 and FAT32 FS only supported
ENV{ID_FS_TYPE}!="vfat", GOTO="auto_mount_end"
# Global mount options
ACTION=="add", ENV{mount_options}="defaults,ro"
# Filesystem specific options
ACTION=="add", ENV{ID_FS_TYPE}=="vfat", ENV{mount_options}="%E{mount_options},showexec,iocharset=utf8"
ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", ENV{mount_options}="%E{mount_options},utf8,iocharset=utf8"
ACTION=="add", ENV{ID_FS_TYPE}=="ext2|ext3|ext4", ENV{mount_options}="%E{mount_options}"
# Get mount point : By UUID if not found then by LABEL else by usb-{devname}
# use basename to correctly handle labels such as ../media/foo
ACTION=="add", ENV{ID_FS_UUID}=="?*", PROGRAM="/usr/bin/basename '%E{ID_FS_UUID}'", ENV{dir_name}="%c"
ACTION=="add", ENV{dir_name}!="?*", ENV{ID_FS_LABEL}=="?*", PROGRAM="/usr/bin/basename '%E{ID_FS_LABEL}", ENV{dir_name}="%c"
ACTION=="add", ENV{dir_name}!="?*", ENV{dir_name}="usb-%k"
# Main action
ACTION=="add", RUN+="/bin/mkdir -p '/media/%E{dir_name}'", RUN+="/bin/mount -t %E{ID_FS_TYPE} -o umask=0,uid=stdOVIPuser,gid=stdOVIP,%E{mount_options} /dev/%k '/media/%E{dir_name}'", TAG+="mounted"
ACTION=="remove", RUN+="/bin/umount -l '/media/%E{dir_name}'", RUN+="/bin/rmdir '/media/%E{dir_name}'"
LABEL="auto_mount_end"When the 3008 II was released, it was announced a "sliding boot floor" option that was constantly postponed, until finally canceled. With that option, the boot had 2 lights, as you can see in this photo: Sliding boot floor
Also a video about that option (but you can't see the 2nd light): PEUGEOT 3008 SUV | 2 Position Sliding Boot Floor
There's already a TSB - Technical Service Bulletin about this problem - D6AW01HQQ0.
According to "bagou91" from the French forum-peugeot.com and the developer of the https://github.com/bagou9/Peug…date-logiciel-alternatif/ , the PSA server now requires TLS 1.2
Yes, the OEM version, part number 98131719 80. I also bought the 6541.T0 plug (with a small adaption) and two 6541.E6 terminals.
You don't need to remove any panel and there's enough space behind. You can also remove the cover in the lower right of the photo, the one to access the tail lights.
BTW, this are the mesures (in cm) to cut the panel:
Those files/logos are only for the FM band, that broadcasts the network and channel ID pair. With those IDs, it's easy to map to each file/logo.
For the DAB, its up to the station to broadcast its own logo, there aren't any in the firmware.
The NAC only supports FAT32 filesystems (only vfat is compiled in the Linux kernel, no ntfs/ntfs-3g/fuse support). As any other vfat, it can handle 2/8/16 TB partitions (it depends on the sector size). The 32 GB "limit" is only in the Windows UI, the format.exe command can format larger partitions.
The NAC itself can only list the first 3.999 media files, but can play all files in random mode.
You could also install the 98 179 561 80 (PSA part number) USB cable, to connect a 2nd USB port to the NAC infotainment system. There are some known problems with USB hubs, especially those that are unpowered.
You should give it a try.
I have also started translating partly into english.
I haven't translated everything yet as it's a lot of work.
I will. I need to use my own script so that it can automagically build all those tables in https://sites.google.com/view/nac-rcc/
Is there any collaboration effort to translate the messages (maybe .po/gettext files)?
You mean my old toolbox 1.0.0.34?
Then i have to check it because i haven't changed the id, just some bug fixes in terms of server queries because the response code from server has changed a while ago.
Try it out with a Wave 1 chassis number and my new toolbox version 2.0.0.0 or better send me a chassis number with a Wave 1, then I can see whether it works.
I don't know your toolbox, but it was a change in the recent Peugeot Update 1.2.1.
I've checked now with the old client_id (1ee...f54), and it does work with a NAC Wave 1 VIN. Some days ago, I had to use the new id (20a...0e5) from the "app.asar" file.
Alles anzeigenAs far as I know there are no other codes for the RCC.
At least none that have been made public.
Does the RCC not have an export function?
Otherwise there is only one look at the head unit.
You can also use the chassis number to check for updates with my toolbox.
If an update is available, it will show you the serial number.
Otherwise, send me your chassis number, then I can look it up in the toolbox.
In the Nac you can also see the serial number via one of the cheat code.
I mean to have seen something the other day while I was scrolling through the menus.
But I have to take a closer look to be sure.
The RCC doesn't have an export function (well, the Chinese and the AIO, both from Continental, does have one...). Or I didn't find it... The problem is when the system infotainment was replaced, the PSA Majestic API will reply with the old/factory UIN. And you need the UIN to download the certificate/license key to update the firmware (many of those systems doesn't have BTA with WiFi or any way of tethering the phone, so they need the file on the USB flash drive).
I'm assuming that your toolbox does the JSON query to the Majestic server to check for updates. BTW, the client_id was recently changed in the "Peugeot Update" software, and the old one doesn't work anymore with NAC Wave 1 systems.
Hello,
Does anyone know if it is possible to see the UIN (20-digit hexadecimal number, that usually start with x0D...) on the RCC system (from Bosch)? Couldn't find it in the "Engineering Mode".
On the NAC, (or RCC AIO from Continental) we could export the configuration in the "system info" screen, and that will create 2 files on the USB flash drive - "instkey_<UIN>.xml" and "packageslist_<UIN>.txt"...
