Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2014 mazda 6
#1
I started out with crankshaft about 6 months ago, and just recently decided to transition to open auto pro, and have been very happy with it. It is snappier, less buggy, and supports more useful features to me. Over all a very polished product and well worth the cost.

I documented my build in a series of youtube videos. So while I don't have a photo album, I figure videos can be just as effective. I hope it can help out others.

My setup features -

- backup camera support w/ custom script

- automated delayed shutdown w/ custom script

- hands free calling & streaming w/ external bt module & microphone

- steering wheel controls using an arduino keyboard emulator

Along with a number of other features that come stanadard with open auto pro.

I tried to document everything in a step-by-step manner, which ended up with roughly 45 minutes of content! I thus split it into 2 videos -

Part 1 - Open Auto Pro Setup, Camera Script & Shutdown Script - https://www.youtube.com/watch?v=vMvMXd4RvdA

Part 2- BT Calls & Streaming, SWC, Wireless AA, Kodi - https://www.youtube.com/watch?v=Z-0post9HVo



Let me know if you have any questions or comments!
Reply
#2
Hello Hisma,

First of all thank you very much for posting your project. This is amazing! We watched the videos couple times and every time we were more impressed. Thanks for the effort to make a videos and describe everything in details. That is also really important for us because your project gives us suggestions what is still missing in OpenAuto Pro and where we can improve things to work better. We will definitely consider to improve the update process. We are very glad that you enjoyed OpenAuto Pro and could use it as a part of your amazing project.



Small hint to the setup of the steering wheel buttons:

In order to get volume controls working you can map F7 (volume down) and F8 (volume up) keys with your steering wheel buttons. Our user guide (http://bluewavestudio.io/resources/opena...de_2_0.pdf page 24) contains full list of keyboard keys that can be used with OpenAuto Pro.



Once again thank you for posting your project! In case of any further help do not hesitate to contact us.
Reply
#3
You're welcome! Thanks for providing a great solution, I hope the project continues to grow and improve. With the videos my goal was to show how far you can stretch a pi-based head unit replacement and inspire others to try. The reception to my videos has been good so far so I feel it was definitely worth the effort.

With the volume control, I don't think there is a standard ascii keyboard code for function keys (F7/F8), plus I have my rotary volume knob, so I didn't see the necessity. Though perhaps if you could modify your software to allow volume up/down using more standard keys somehow, I could link it with my SWC. I used this for reference -

https://theasciicode.com.ar/



Also, yes, if you could implement an update method that doesn't require re-flashing the sd card, that would be very useful. Some way to update over USB, and also back up certain files/folders so you don't have to re-do setup every time, would be sufficient. It's a pain to take my car apart just to perform software updates... and I am sure this problem would apply to most users that have a permanent installation.
Reply
#4
We analyzed a bit code that you provided in the video description (https://pastebin.com/W0BakXu4) and it looks like it uses standard Arduino library to simulate keyboard. Could you please try to use codes for F1-F12 from following link https://www.arduino.cc/reference/en/lang...modifiers/?



Also it might be useful to map "p" key (of course if there is room for it Smile ) to answer the phone call. in 3.0rc1 "p" works only from Android Auto but in the next release it will work in OpenAuto Pro as well.
Reply
#5
BlueWave Wrote:We analyzed a bit code that you provided in the video description (https://pastebin.com/W0BakXu4) and it looks like it uses standard Arduino library to simulate keyboard. Could you please try to use codes for F1-F12 from following link https://www.arduino.cc/reference/en/lang...modifiers/?
Also it might be useful to map "p" key (of course if there is room for it Smile ) to answer the phone call. in 3.0rc1 "p" works only from Android Auto but in the next release it will work in OpenAuto Pro as well.

These are great tips!  I will try them.  I also really like the idea of having the ability to answer phone calls as well, so I'll try your suggestions and report back.
Reply
#6
function keys for volume confirmed working!

ascii code 200 (F7) for volume down and 201 (F8) for volume up were updated and uploaded to the leonardo and now I can control volume from my steering wheel. I do actually like that change bc it's naturally easier to control from the wheel vs the rotary knob.

I can also see this being a great feature for users that don't have an external rotary knob like I do. Arduino keyboard emulator really makes a great pair for open auto.

Now I just need to tap an additional wire to access a few more buttons from my wheel... but I'm in no rush to go there Wink.
Reply
#7
hey I have encountered an issue. In regards to bluetooth phone calls, I found that call quality is just fine outside of openauto, as I demonstrated in my video. However, inside of openauto, voice input is choppy and the person on the other end can barely understand me. Supposedly this is an issue with the internal adapter, but I would think that if this was a hardware issue, it would happen all the time, just not in openauto.



I am willing to provide debug details. Do you have anything I can try? For now, the only solution for me is to make or answer phone calls outside of android auto, which is obviously not ideal. Thanks
Reply
#8
Hisma Wrote:hey I have encountered an issue.  In regards to bluetooth phone calls, I found that call quality is just fine outside of openauto, as I demonstrated in my video.  However, inside of openauto, voice input is choppy and the person on the other end can barely understand me.  Supposedly this is an issue with the internal adapter, but I would think that if this was a hardware issue, it would happen all the time, just not in openauto. 



I am willing to provide debug details.  Do you have anything I can try?  For now, the only solution for me is to make or answer phone calls outside of android auto, which is obviously not ideal.  Thanks
It may happen when you use external bluetooth adapter with internal settings (and vice-versa). Could you please post the output of lsusb command? Maybe your Bluetooth dongle is based on the Broadcom chip that may cause the same issue like for internal Bluetooth Adapter.
Just in case you can also try to toggle (sudo btswitch internal and then sudo btswitch external).
Reply
#9
BlueWave Wrote:
Hisma Wrote:hey I have encountered an issue.  In regards to bluetooth phone calls, I found that call quality is just fine outside of openauto, as I demonstrated in my video.  However, inside of openauto, voice input is choppy and the person on the other end can barely understand me.  Supposedly this is an issue with the internal adapter, but I would think that if this was a hardware issue, it would happen all the time, just not in openauto. 



I am willing to provide debug details.  Do you have anything I can try?  For now, the only solution for me is to make or answer phone calls outside of android auto, which is obviously not ideal.  Thanks

It my happen when you use external bluetooth adapter with internal settings (and vice-versa). Could you please post the output of lsusb command? Maybe your Bluetooth dongle is based on the Broadcom chip that may cause the same issue like for internal Bluetooth Adapter.



Just in case you can also try to toggle sudo btswitch internal and sudo btswitch external.

Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)



so it's not using the broadcom chipset.  So that shouldn't be the issue here. 

I have already done the "sudo btswitch external" command so that shouldn't be an issue either.  One thing I did notice though is that in "rc.local", I do not see one of the lines commented out that was bt-related.  I wonder if that might help?? I will see what kind of troubleshooting I can do here.  But I do not believe my issue here is related to my hardware, unless the cambridge silicon chip also has issues.  In which case I would ask which should is known to be reliable.
Reply
#10
Hisma Wrote:Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)



so it's not using the broadcom chipset.  So that shouldn't be the issue here. 

I have already done the "sudo btswitch external" command so that shouldn't be an issue either.  One thing I did notice though is that in "rc.local", I do not see one of the lines commented out that was bt-related.  I wonder if that might help?? I will see what kind of troubleshooting I can do here.  But I do not believe my issue here is related to my hardware, unless the cambridge silicon chip also has issues.  In which case I would ask which should is known to be reliable.

Line from rc.local is related to the internal bluetooth adapter only. Anyway, if you switch to the external bluetooth adapter, mentioned line should be commented-out. Do you have any idea why it disappeared?

Could you please post the output of the ls /usr/lib/pulse-10.0/modules/ command?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)