Replies: 1 comment 2 replies
-
Hey! Thanks a ton for making this post, really nice to know there's still an interest. The goal is exactly what you outlined - eventually have the ability for deep customization on multiple levels - especially in terms of IO. Would love to see/chat a bit about the PCB you made! I need to buckle down and make a solid pass on the software to implement more modularity, customizability, and ease of install. Being the sole developer and with how big of an undertaking this project has proven to be I'm temporarily struggling with the motivational aspect of that, which explains the slower development here. But hoping to be able to be able to dive into it more soon! Would definitely love to hear more of your opinions about what OpenAuto got wrong & right though so I can continue to build this project out. Cheers! |
Beta Was this translation helpful? Give feedback.
-
Would love to help move this forward. I'm not terribly good with programming, but I have used many arduinos in the past. Currently running Openauto Pro but I really don't like the lack of customization. Aside from the steering wheel controls, I would have been better off to just grab an off-the-shelf android head unit from Amazon.
I did make my own PCB for 12v inputs and timer/shutdown circuit, program my own arduino micro to grab the resistance values from my steering wheel controls & push out button presses to the Openauto software. Works great and I can control the button rate this way (like to have volume down much much faster than volume up). My other issue is that the best way to get 12v to the GPIO is optocouplers but since they sink and Openauto doesn't offer pin down as a valid input you have to do a lot more yourself to flip the signal. Huge oversight IMO
Let me know if I can help in any way
Beta Was this translation helpful? Give feedback.
All reactions