Login  Register

RE: How-to/tutorial?

Posted by homerisback on Apr 02, 2016; 8:20am
URL: http://bluesaab-forum.90.s1.nabble.com/How-to-tutorial-tp106p313.html

My third module is back to life regarding bluetooth, RN52 chip had a few pins not enough soldered ; solved !
But, I remain stuck at selecting CDC as source in car. I downloaded one again the 2.1 release of Karlis code from Github but, even named 2.1, it displays SAAB-CDC v2.0 Feb 2016 in .ino code. Zip librairies are loaded.
When I do a "verify" in Arduino-IDE, I don't have any error message and the sum up shows "The sketch use 7 234 bytes (22%) of program storage space. Maximum is 32 256 bytes."
By the way, while uploading the code to 328, I got this message "avrdude: warning: cannot set sck period. please check for usbasp firmware update." more as information rather than a blocking message as uploading and verifying the ulpoad goes flawlessly and reports no error.
I tried to get rid of this message by setting (on USBasp) voltage to 5V instead of 3.3V but it's still there. Forums and wikis I read apparently said it doesn't prevent from successful uploads... I'm not enough sharp in chip programming to tell it is true or not, maybe Karlis would confirm or not this info ?

When my phone connects to a module, music over BT volume increases (cannot say if it goes to maximum) but autoplay doesn't start, would that say I'm running 2.0 code ? My Nexus 5 runs Android M latest release 6.0.1.
Didn't have time to revert to original VIN in DICE and try with a kind of virgin setup of CAN comms.

One last thing : today and yesterday morning I connected a module just after a night sleep for my car and CAN leds remained OFF until I started the car. Is there a kind of sleep mode in CAN comms after a time lapse ?
01' 9.3 SE Conv - AS3 - Nexus 5 Android M 6.0.1 - BlueSaab v4.2 + Amp - Latest CDC repo.