Contenu récent par pepelxl

Has anyone managed to make friends with RCC/NAC old dashboards? I have CIROCCO for SMEG. I don't want to change it to a new one because of other graphic themes. The problem is that the dashboard accepts strings of track names with null-terminator, and RCC sends messages without null-terminator...

IVI has the same set of encodings as all other multimedia.

https://github.com/pepelxl/psa_coder I have uploaded the software, if you wish, then add a description via the Pull Request button.The reason for the creation of the software is the incorrect mask ratio in alternative programs.

maybe later, now there is no time to work on software.

or 360view

I can see the arguments for sorting the list, but I can't change the order to rcc w3. does anyone have any ideas?

It's already included in Ludwig's sketch.

Merci

Je cherche des photos des entrailles de RCC W2 W3. Particulièrement intéressé par wave 3. Mais les options wave 2 sont prêtes à regarder, il y en a 6. maintenant, il n'y a que des photos de single antenna. Nous avons besoin de bonne qualité pour que les marques de puces soient visibles.

I’ll ask here as the topic with the largest number of views and the presence of people who know how to juggle firmware, does anyone have a .cal file for smegIV2 with firmware 6.4? I need it from any car.

@VLud , 0e6 code can be optimized and reduced by half. I think your version will be cleaner and more practical.

@gusao10 I gave up developing my software because it has an incorrect structure and a problem with communication with the vcp driver. The biggest problem is the lack of SEED for esp90 blocks. The only known password was posted by Ludwig, but it does not fit most blocks. Also, new revisions have...

__u8 checksumm0E6(const __u8* frame) { /* Autors: organizer of the bacchanal: styleflava algorithm: Ilia code: Pepelxl */ static __u8 iter = 0; __u8 cursumm = 0; for (__u8 i = 0; i < 7; i++) { cursumm += (frame[i] >> 4) + (frame[i] & 0x0F)...

mask is not an xor, but the value of the bit indicating the encoding location.

I assume you have the second option, since the first byte in your encoding is 0x06 and this offset is called "CONFIG_INDICE_TELECODAGE". Such a byte is available in most modern ECUs, and I assume that the developers control the encoding string variant with it. The first option provided by me...