New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CanZE for R-Link #144
Comments
Just some added information: |
Interesting stuff! I had a quick peek but it seems to me there is nothing there that could help us any further. It seemed mostly the Android core system. It is a huge leap to get from there to a development chain. I stand by my statement above. |
I had a discussion with Renault about R-Link development. Won't go in more details but the essence of it is that it is not doable and totally depending on Renault France. Furthermore, R-Link does not have direct link to the main CANbus. |
Ok, if it's not connected to the main bus, it is probably really moot. I also found by disassable that the new firmware release 2094591 fixes at least some of the stagefright bugs. |
it is often suggested CanZE should be implemented on R-Link. Here is an early (and if I may say rather blunt) example from the German forum:
On the face of it, the argument is not unreasonable:
Then, there are also strong arguments and uncertainties against:
don'tknowifR-Link is not connected to the main CANbus, which is needed;most probablyhave to deal with the whims of both Renault and TomTom;My opinion is that I am not (yet) willing to either risk breaking R-Link or buying / learning / maintaining a specific tool chain and emulator / hardware for solely this project.
I can't see this happening really, unless there is explicit demand from Renault. I doubt they are interested and given the effort needed we'd have to even talk some sort of compensation. Given the free-beer nature of this project, I see us opening up a nasty can of worms between the team members.
This this will not happen. IMHO.
The text was updated successfully, but these errors were encountered: