Some months ago, Gunter sent me a BlueSmirf Bluetooth module to assist with Ulytune... Being the lazy scrote I am, Ulytune has kinda taken a backseat in favour of Son of Grenade and the 2002 Parts Bin Special X1.
Since I had been sitting on Gunter's Bluetooth module for some months, I thought I ought to return it, but not before making my own. Instructions exist, I think I even translated them, but you never know how good they are until you try to validate them...
I bought a BlueSmirf module back in 2010, so all I needed to do was make an interface board. My interface board differs a little from Gunter's. I use a TS78L05CS with no additional filtering (cos the datasheet says you don't need it).
I built the board and connected it all up and I got the red light flashing on the module, so success. I got my Palm and went to connect, it connected fine but I couldn't get anything out of the EEPROM.
Disaster I thought, so I went back to the instructions and read them again and saw that I had neglected to set up the flow control (a blob of solder on two pads on the PCB) and I had also neglected to set up the baud rate between Bluetooth module and ECM.
The instructions are a bit scant on setting up communication between the Bluetooth module and, in my case, a laptop, referencing the use of Hyperterm...
So, I looked to see what COM port I was connected to with the Bluetooth module:
Attachment:
Bluetooth a.jpg [ 28.13 KiB | Viewed 4126 times ]
Here was my first confusion, surely it was only connected to one COM port
- if you haven't realised already, I am a bit computer illiterate...I opened Hyperterm (I am using Windows XP) and connected to the first COM port. Typed some stuff, but nothing. Did a search and found some guy with a 'How To', but I was French Connection UKed if I could make my PC do what he was showing - maybe he was on Windows 7 or Vista or something posh like that.
Back to the ECMSpy site and I found a reference to LynxTerm, so I downloaded it and fired it up... Select my COM port (the first one):
Attachment:
Bluetooth 1.jpg [ 36.81 KiB | Viewed 4126 times ]
Connected power to Bluetooth dongle, with the red light flashing quickly, pressed connect on LynxTerm. The green LED on the module lit up and the red one flashed even more furiously (like When Harry Met Sally). I then, as instructed by the ECMSpy site, typed '$$$'. Before I could press return, the Bluetooth module responded by putting a question mark at the end (I didn't have a clue what was going on, but it was OK as you will see):
Attachment:
Bluetooth 3.jpg [ 41.86 KiB | Viewed 4126 times ]
This told the Bluetooth module to 'listen up' and await further instructions. Typing 'd' then [return] pulled up the configuration:
Attachment:
bluetooth 4.jpg [ 50.53 KiB | Viewed 4126 times ]
Baudrt = 115K was not what we wanted. The baud rate should be 9600 (not 115000). So, with the command 'su,96' followed by [return] this set the speed to 9600:
Attachment:
bluetooth 5.jpg [ 48.56 KiB | Viewed 4126 times ]
And, just to check it had done its job properly, 'd' followed by [return] shows its config:
Attachment:
Bluetooth 6.jpg [ 50.52 KiB | Viewed 4126 times ]
All good, so reboot the device with 'r,1' followed by [return]:
Attachment:
Bluetooth 7.jpg [ 47.8 KiB | Viewed 4126 times ]
Then, as if by magic, the Palm can read the ECM over Bluetooth...
[I'll put some pictures of the Palm screens if I can get everything to work on the Palm emulator on the PC]
Next job is to get a Bluetooth module made up for the the up and coming ECMSpy hero, WillyBuell.
