[Janssuuh]

Hi,

Could you specify the error the skin comes up with?
Also could you provide a scheme, or picture of your hardware / wiring?

Thanks,
Knd regards
Jeroen

[Janssuuh]

Hi Piotr,
If the script does not recognizes your car it should use default values.
Could you send me a candump?

Thanks,
Kind regards Jeroen

[Janssuuh]

Hi Dave,
It seems the trouble starts within the file “/etc/can.conf”
If you’ve installed the latest version (3.0.0) of hardbyte python (pip install python-can) you should safely be able to delete the config filr, because I added these settings withim the script.

Hope it’ll work!
Kind regards,
Jeroen

[Janssuuh]

Hi Piotr,

I asume Rui made a very good point with his previous posts.
It has happened before that the (Hardbytes) PyCan library changed the position of the actual message in it’s Can-String.
You won’t notice any difference in the canlog, because this is being saved directly using Pican modules (Say; Not using Python).

I can / will check this next Tuesday. I saw there should be a can.message() -like function now, which makes it no longer needed to cut a substring from the full detail output..

Kind regards,
Jeroen

[Janssuuh]

Hi Rui,

Thanks for your input!
I haven’t been able to check changes with the new hardbyte version offered at their website. Indeed it’s a good solution to use the version I once downloaded…

Also on the coolant temp there is some info available. I’ll quote an older post:

The ”settings.txt” at location ”/home/pi” per default contains this content:

#Coolant formula details

Coolant Order : 1
Coolant Amount: -32
Coolant Factor : 1.8

#End of Coolant formula details
#To restore defaults, just delete settings.txt and reboot

The Order parameter means 1: First execute Amount and then the Factor,
2: First execute Factor and then the Amount.

So for example (one of the forum members asked for) it’s editable to:

Coolant Order : 2
Coolant Amount: -48.2
Coolant Factor : 0.8

Now the hex value your car produces is factored by 0.8 and after that 48.2 is substracted.

(There is a [tab] after the [:]. Please leave this the way it is and only change the values)

The default -32 is probably because 0 degrees celcius = 32 degrees fahrenheit.
If your engine is of, it might send 0 degrees fahrenheid, which results in your -17 degrees celcius.

With kind regards,
Jeroen

[Janssuuh]

Hi Dietmar,

If you use Full version, you must not install script.service.JanssuuhRnseBediening and script.service.JanssuuhSendCanToFIS!
These functions are built in and would run twice… (resulting in weird behaviour)

Btw: If you own a vehicle which uses 2G or 3G protocol and could manage a candump, I’m very interested to examine it for usage with this project! (First part is going to be a challenge… Some cars use an optical connection! You won’t be able to just connect ‘our’ skpang module to this… Als data rates can be different and last but not least; Audi is coding / scrambling this data on purpose, to make it less easy to ‘speak’ to their systems. Though, it’s possible to add OEM hardware, so it must be possible to reconstruct that.)

Kind regards,
Jeroen

[Janssuuh]

Hi Piotr,

Thanks for your input!
I tested it (made a script which actually sends the exact same data as your car did during the specific log) but did not managed to break anything :S
Also I recorded the can-id pages while running your log/messages. Will post / share this tommorow.

I uploaded a new version of the skin (0.0.45) which should be more stable if something unexpected happens. Also if an error occurs it’ll be logged to a (new) ‘error log’ window (you can find this at ‘Settings’ / ‘Configure Audi Rns’ / ‘development mode’).

The raspberry with its can-module is a kind of a can scanner / logger.
If you’d connect it to your car and in terminal you type: [candump can0 -a] it will print all traffic (with -a as parameter for ascii values).

I hope with the errorlog page we’ll find out what is going on!
(If it does not find any errors, for a next step we could check if all settings are picked up correctly… You could btw check if ‘System Information’ window shows the correct model / year of your car!)

With kind regards,
Jeroen

[Janssuuh]

Hi Piotr,

It’s been a while 🙂
I actually had to reassamble the hardware and install Raspbian! But it’s all up and running again!
Tonight I made a little python script which could ‘fake’ send can messages, which were read from a can-log file…
Now I’m afraid with all the restoring backups of my website I lost your logs 🙁 Do you still have a copy of one of your logs?

If so, I could reconstruct your case and see why / where there could be an issue…

Thanks and kind regards,
Jeroen

[Janssuuh]

Hi Piotr,

I got your latest can-dump, thanks for that!
I’ve read you disconnect can-bus from your Raspberry because of the FIS flickering.

Actually in the latest Version (44) the script will listen to can-id 65F, which carries your Audi’s model and year.
I add an image of what the script (snippet) would do in your case;

So it says ‘8P5’ year of build ‘2013’. This would make the script write FIS messages to 667 and 66B (like your carkit does).
If you disconnect the raspberry from the bus, it would not ‘hear’ the 65F message and picks it’s defaults (265 / 267).
This seems to be what has happend in your log…
(I need to examen your log a bit further to actually see how your carkit behaves.)

Then the Development pages;
I picked 2×6 Id’s which seem to be used a lot in your dumps. These I’d wil show up ‘live’ as soon as they are received.
Now the first received messages will be printed in the more grey color. As soon as a message is received on the same Id, with different bytes, those bytes will turn red.
It’s going to be really hard to actually find out what this all means, but it’s for example how I found out where my speed signal is sent (Just because it only starts changing when you start moving! Also you could check these measures when you open doors, move forward / backward, filled up the gas, turning on / off anything…

Of course, this will only work with connected can-bus.

Kind regards,
Jeroen

[Janssuuh]

Hi Piotr,

Yes, actually I tried to backup the website which somehow corrupted the database… couldn’t restore latest backup either, so finally my hosting provider helped te restore a 2 weeks old backup :-S

I did make some changes to the function which determines car model / year based on can message (and prints it on settings page).
This is what caused some issues in the previous (test) version.
I’ll try to package this version this week.
It should now send FIS messages to the ID which is also is used by your carkit.
Probably not solving all issues, but should provide some new details in the log.

Best regards,
Jeroen

[Janssuuh]

Hi David,

The ”settings.txt” at location ”/home/pi” per default contains this content:

#Coolant formula details

Coolant Order : 1
Coolant Amount: -32
Coolant Factor : 1.8

#End of Coolant formula details

#To restore defaults, just delete settings.txt and reboot

The Order parameter means 1: First execute Amount and then the Factor,
2: First execute Factor and then the Amount.

So for example (one of the forum members asked for) it’s editable to:

Coolant Order : 2
Coolant Amount: -48.2
Coolant Factor : 0.8

Now the hex value your car produces is factored by 0.8 and after that 48.2 is substracted.

(There is a [tab] after the [:]. Please leave this the way it is and only change the values)

The default -32 is probably because 0 degrees celcius = 32 degrees fahrenheit.
If you engine is of, it might send 0 degrees fahrenheid, which results in your -17 degrees celcius.

With kind regards,
Jeroen

[Janssuuh]

David Ziller said:

Hey Jeroen,
can u tell me something about the settings.txt?

Coolant Order : 1
Coolant Amount : -32
Coolant Factor : 1.8

What can i adjust? When my igniton is off the coolant temp is -17
Can i fix this with the settings?

Thank you 🙂

[Janssuuh]

Hallo Stefan,

Ich habe in der Vergangenheit versucht, den Fokus auf den aktiven Titel zu verlagern. Leider hat sich dies bisher als unmöglich erwiesen.

Mit freundlichen Grüßen,
Jeroen

[Janssuuh]

Hallo Stefan,

Ich habe eine neue Version verfügbar gemacht (V0.0.40). Die Auto-Video-Freigabe ist darin enthalten (nur wenn sich der rns-e im VIDEO-Modus befindet)

Gruß, Jeroen

[Janssuuh]

Hallo Stefan,
Es ist einfach, die Raspberry die Entsperrings Nachricht senden zu lassen.
Ich werde es diese Woche (wählbar) einbauen.

Kann ich Sie fragen, welche Lösung Sie gefunden haben, um das HDMI- / oder Tulp-Videosignal zu konvertieren in das Videosignal das der RNS-E verwendet? (Ich denke, das erfordert RGB- und “Sync” -Signal, wie SCART auch hat).

Mit freundlichen Grüßen,
Jeroen

[Auteur]

Berichten