rx7locost

I though I'd share this with the rest of the group. As I mentioned in my email to Ernest. I think his problem lies with identifying the COM port the bluetooth is occupying and adjusting Tuner Studio to communicate thru that COM port. I am awaiting his reply.

To close up one loose end, the only commands I have found to work with the module are:

AT
AT+NAMEanyname (I used the name MEGASQUIRT)
AT+VERSION (this queries the module for it’s firmware version. It replies OKlinvorV1.5)
AT+PINxxxx (where xxxx=1234 by default)
AT+BAUDx (where x= the lookup table for baud rate. 8=115,200)
AT+Px (where x= O, P or N for parity check ODD, EVEN or NONE. default is "none")


I'm not sure what the AT+NAMExxxx command actually does since no matter what I do, the module always shows up in my Bluetooth list as "Linvor"

ErnestChristley

I haven't got back to this in the past few days. I've been busy with my homebuilt CNC mill, carving my propeller.

My problem was not in the selection of the serial port. I had read a thread earlier where someone was having that problem, so I was being very careful with that part.

However, you provided several other commands and setting the flow control in particular may help. It seemed to be that sort of problem...like it was almost connecting but couldn't quite catch. I seem to remember that incorrect flow control could cause that sort of symptom. But it's been a long time since I played with modems. Dang internet. Making me feel old. 8*(

.::evil inside::.

Well my adaptor arrived, I think I got it set up right and managed to connect my Samsung Galaxy S to my MS via the adaptor. All the information displays on the screen, but it seems very jumpy and glitchy so I think I may have done something wrong with the set up.

I added the 3.3V to PIO11 jumper on the chipset to set the baud rate (thanks for the more detailed explanation, I would have been lost without it) but I had a lot of trouble setting up hyperterminal as I have no idea how to use it. I have never used it before and it was like trying to learn another language.
Anyhow, I stumbled through it and I think I set the baud rate correctly. I copy and pasted the appropriate command "AT+BAUD8" and from memory it replied with "AT+BAUD8115200", then I pasted the command again (because I couldn't believe it appeared to work haha) and it didn't respond. Is that because the baud rate was successfully updated and because hyperterm was set up for 9600, it now won't communicate? Or am I getting progressively more lost?

I'm also using a usb to serial converter as none of my pc's or laptops are equipped with true serial ports. I'm 100% certain on the appropriate com port too.

Can someone please help me understand how hyperterminal should be set up before and after baud rate change?
These are my current settings, is there anything silly about them?




Also, is it possible to connect my bluetooth adapter to the computer while the db9 pin 9 is jumpered to +V? will hyperterminal communicate with it in this state without the 3.3V to PIO11 jumper? if so, which commands may work - this last question is purely for diagnostic purposes so I can see if the thing is actually set to 115200 or not etc. I guess I need to set hyperterm to 115200 baud?

Oh, and if I wanted to reset it, is that what the little button is for? and I take it I would have to press it with the unit powered up yes?
I had a bit of a hunt on google for a crash course in using hyperterminal so I could understand what I am doing a bit better, but I was unsuccessful.

Any help you can give me will be very much appreciated.

Noob out

ErnestChristley

Yes, you will have to set Hyperterminal to 115,200 after you change the adapter.

I think the way the reset button works is that it will reset back to defaults on the next time that it is powered up.

rx7locost

"Oh you adventurous group! Have I lead you into the bowels of1960's and RS-232 terminal emulation programs? My how time flies and the serial communication technology of yore is not current common knowledge."

Once you have changed the Baud Rate of the module to 115200, you must now set Hyperterminal to the same baud rate, just as you suspected. Otherwise they will not be able to talk to each other.

That may depend on your USB-RS232 adapter or computer's serial port. Old pin assignments for RS-232 pin-9 was for the ring indicator, not +5V. It has been many times been a no-connect pin and sometimes used for a +5V source as in the MSII. If you were using the USB-serial cable to connect the MS to your computer before, you were connecting +5V to your computer. It should work fine. I verified this recently on both my old desktop computer (real RS-232 serial port) and thru a USB-serial adapter to my laptop.

I'm pretty sure that is the reset button. I never tried it. Of course, for it to work, the module must be powered.

To communicate the AT command set from your computer, to the BT adapter, I have always had 3.3v jumpered to PIO11. Some have indicated they have communicated after removing the jumper, but so far, I don't know of anybody but me that has successfully gotten the complete setup working.

If you PM me your e-mail, I will send you a more detailed writeup including screen captures. It is too big to post here, even in zipped form.

Chuck

.::evil inside::.

Thanks for that Chuck, much appreciated.

One question though, how do you paste the commands into hyperterminal? Do you need to have the function keys set to windows keys? or is there a way to do it with terminal keys that I'm not aware of? Will it cause problems if I have it set to windows keys?

rx7locost

I just used the the mouse to right click copy (from notepad) then right click paste (in hyperterminal) . If you are using Hyperterminal 6.3, you can set up macro keys within that program and not have to bother with copy/paste. My copy/paste technique was from when I was running my desktop computer which had hyperterminal V5.1, I think. My guess is you could also use <ctrl>c and <ctrl> v if you that floats your boat.

.::evil inside::.

That does float my boat. I normally use ctrl+c/v, but I just wanted to know if having it set to windows keys would upset it. Guess not, which is good to know

.::evil inside::.

Well I managed to do some more testing tonight.
I left my adapter set up with just the db9 to +v jumper and tested it with hyperterminal. All of the commands that are known to work tested fine! Good news.
So I then paired the adapter with my laptop, changed my TS communications settings to the bluetooth com port and accepted it, bingo! Solid red light instead of flashing. It works! But I kind of already knew this as I have already paired it with my phone and taken a log with shadow logger, but it was glitchy and I only had a second to test it. Next week I will be back with the car and I will be able to do some more testing.

It all looks promising so far. Thanks for the help chuck!
Here's a success video. In the vid I toggle TS from "work offline" to online and you can see the led go solid and back to flashing when I set it to work offline again.

https://www.youtube.com/watch?v=tppM...e_gdata_player

rx7locost

Congratulations on getting this far. I know it is a bit of work to get this to function. But I think you'll reap the benefits soon. Can't wait to hear the final review.

Chuck

.::evil inside::.

poop. It connects with my phone, but the information flickers and carries on. I wonder why... Doesn't want to connect to TS at all. The light is solid on the BT adapter when it's giving the above error messages.

rx7locost

I'll take a look at my adapter later today. I have not run into this. I suspect it has to do with a) the serial port selected in TS or possibly, 2) the data rate selected in TS. My TS is set for 15 fps. I don't know what the default is in TS.

I'll try things out this afternnoon and report on the results.

rx7locost

Got a chance to test some communications variables between TS and the MS. Of course I am starting with a functional BT setup. I tried a few variables hoping to fool the system. Unfortunately I could not get the same results as you. To reduce the flicker on your phone, you might try to reduce the data rate (not baud rate). Just a thought. I don't have a smart phone so can't test your setup. Here are the results from my testing. Maybe it might help.

I just don't know why it works for me and nobody else. You are the 2nd person I know that has gotten this far. There must be some underlying issue I don't know of. I might just try a fresh install of TS in my wife's laptop later in the week. Maybe there is something I am forgetting to mention. Have you tried adjusting the BT virtual Com port settings in the computer? 115,200 baud rate/8 bit/no parity/1 stop/ no flow control. I have my FIFO buffers maxed out.

TS/MS functions w/ BT adapter test

1) Status of adapter LED with TS offline - With the car Ignition on – MS powered up - TS set to “OFF LINE”: adapter LED is flashing

2) Status of adapter LED with TS online - Set TS to :ON LINE: : TS is responding to the MS - adapter LED is ON solid

3) Try a higher data rate: under TS Communications - Data Rate - select MAX page per second: TS is still communicating – LED is still ON

4) Try to test the connection port – under Communications - Settings – select TEST PORT : TS temporarily goes OFF LINE then automatically reconnected ON LINE.

5) Change TS baud rate - under Communications - Settings – select 56K: TS still communicating

6) Check TS find command - Leave Baud at 56K – under TS Communications – Settings – Select DETECT – in about 30 sec found MS see pic ) – press accept : TS reconnected @ 115,200k baud. LED is ON _ see attached pic.

7) Determine how quickly the BT/TS reconnects - Turn off Car (MSII unpowered) wait until TS goes OFF LINE - Turn car back on : BT link automatically re-established connection within 4-5 seconds.

Verneuil

Im gonna try to use this setup with the ALDL port on a 1G DSM. And or use it on my MSII setup. Wont come in for a month damn shipping for china

.::evil inside::.

Well I did some more testing today. I tried stuffing around with the data rates and whatnot to no avail.

At the moment I have everything set to 115200 eg. Hardware manager (com ports), tunerstudio settings, no flow control etc.

Tried reducing the FPS in TS - no luck. It still gives the same errors.

I don't think it's a problem with the settings on the laptop, or my phone as it doesn't seem to want to cooperate with either. I think it may be something I have done, or am doing with the BT adapter. Even though all the commands come back happy, it just doesn't seem to be happy.

rx7locost

Sorry things aren't working out for you. I believe that the BT light being on is just an indication that the BT has paired with your laptop, not that it has made contact with the MS. This is supported by your video of the module connected to nothing but the battery. Not to insult you or anything like that, Do you know that the com port number and settings used to do the initial setup of the BT module is different than the com port number used for normal communication with the MS? I think you do, but no harm in asking.

What do you get if you ask TS to auto find your BT virtual com port?

You might try uninstalling the BT connection on the PC and re-establishing it. You need to use the "outgoing" port with "SPP" service. It seemed to work for some. See this thread: http://www.msextra.com/forums/viewto...?f=122&t=43317

You have gotten about as far as Ernest has gotten. BT connection to the host computer (running Tuner Studio) but no solid connection to the MS. There must be an answer to this.

.::evil inside::.

Haha, no offence taken. I am certain I have the com port settings right and I do realise the solid light is only when the device pairs with the laptop/phone. Thanks for clarifying though. (I'm not computer dumb, just hyperterminal dumb)

I'm definitely using the outgoing com port (Com5 in my case), I definitely have the baud rate set correctly, the adapter is definitely pairing with the laptop/phone, I'm running out of ideas. Wait, I ran out of ideas a long time ago haha.

I'll try asking TS to auto find it, but I don't like my chances of success. I have tried both incoming and outgoing bluetooth com ports too (com 5 and com 11) and only com 5(outgoing) gives me a solid light on the BT adapter.
Thanks again for the help Chuck.

.::evil inside::.

Ok, so been doing some more playing and I have just realised that I am using the DB9 F to connect to my USB-Serial cable, that shouldn't be any problem should it?

This is how my bluetooth adapter is configured. Is it a problem that the unsoldered pins on the DB9F aren't insulated?



I tried pressing the button as well and it seems to do nothing. I tried assigning the outgoing port with different com ports - no luck.

when asking TS to auto detect it just searches and searches and comes back with nothing.

I connected the BT adapter to my USB-Serial cable again and communicated with hyperterminal without a problem - changed baud back to 9600, changed the device name etc. All good, and that was without the jumper.

I might have to sit back and wait for someone else to come up with a solution

rx7locost

The unsoldered pins are OK.

the DB-9F end of the module normally would pug directly into a computer's serial port for setup. Via the USB-serial adapter is OK. The DB9-M end of the module plugs into the MS. make sure you are not plugged into the computer with the other end (DB9-F) at the same time you are trying the bluetooth.

Are you connecting the module to the MS via a cable? Unless you know the cable, there are several kinds. Some cross the tx and rx wires some do not. Some have gender changing etc. The way I connected it was to plug the module directly into the MS. This may be your issue.

.::evil inside::.

I'm plugged directly into the MS and haven't connected MS and laptop at the same time so we can rule that out

ErnestChristley

I did some testing last night using ShadowLogger. I know I have the module set up correctly now. I've change the name to mgsqrt or some such, and ShadowLogger pairs with it and picks up the name. The Bluetooth end of the comm channel is good.

ShadowLogger lets you log the serial data that comes across. What I got looks like:

Log Start Time: Mon Jan 16 21:26:29 EST 2012Shadow Logger MS 1.05
Firmware Signature: MS
Android Version: 2.2
Between Read Wait: 5
Additional Read Wait: 25


wb:true
bbb:false

Time:8.464s. new request
Time:8.465s. SENT 1 bytes
x51 Q

Time:8.902s. s:500
Time:8.903s. READ 0 bytes
Time:8.904s. s:5
Time:8.971s. s:500
Time:8.972s. READ 0 bytes
Time:8.972s. new request
Time:8.974s. SENT 1 bytes
x51 Q

Time:9.479s. s:500
Time:9.48s. READ 0 bytes
Time:9.48s. new request
Time:9.483s. SENT 1 bytes
x53 S

Time:9.986s. s:500
Time:9.987s. READ 71 bytes
x32 x0D x0A x53 x65 x72 x69 x61 x6C x20 x70 x72 x6F x62 x6C x65 2..Serial.proble
x6D x20 x2D x20 x6E x6F x69 x73 x65 x20 x2D x20 x70 x6F x73 x73 m.-.noise.-.poss
x69 x62 x6C x65 x20 x63 x61 x62 x6C x65 x20 x6F x72 x20 x63 x6F ible.cable.or.co
x6D x70 x75 x74 x65 x72 x20 x68 x61 x72 x64 x77 x61 x72 x65 x20 mputer.hardware.
x70 x72 x6F x62 x6C x65 x6D problem

Time:10.021s. new request
Time:10.031s. SENT 1 bytes
x51 Q

Time:10.539s. s:500
Time:10.54s. READ 2 bytes
x4D x53 MS

Time:10.544s. new request
Time:10.548s. SENT 1 bytes
x53 S

Time:11.052s. s:500
Time:11.054s. READ 0 bytes
Time:11.055s. new request
Time:11.058s. SENT 1 bytes
x53 S

Time:11.561s. s:500
Time:11.562s. READ 0 bytes
Time:11.563s. new request
Time:11.566s. SENT 1 bytes
x41 A

Time:12.319s. s:750
Time:12.32s. READ 0 bytes
Time:12.337s. new request
Time:12.338s. SENT 1 bytes
x41 A

Time:12.841s. s:500
Time:12.843s. READ 0 bytes
Time:12.844s. s:5
Time:12.849s. new request
Time:12.851s. SENT 1 bytes
x41 A

Time:13.355s. s:500
Time:13.355s. READ 0 bytes
Time:13.356s. s:5
Time:13.362s. new request
Time:13.363s. SENT 1 bytes
x41 A

Time:13.528s. new request
Time:13.529s. SENT 1 bytes
x51 Q

Time:13.867s. s:500
Time:13.867s. READ 0 bytes
Time:13.868s. s:5
Time:13.874s. new request
Time:13.876s. SENT 1 bytes
x41 A

Time:14.032s. s:500
Time:14.033s. READ 0 bytes
Time:14.033s. new request
Time:14.035s. SENT 1 bytes
x51 Q

Time:14.378s. s:500
Time:14.379s. READ 0 bytes
Time:14.38s. s:5
Time:14.386s. new request
Time:14.387s. SENT 1 bytes
x41 A

Time:14.539s. s:500
Time:14.54s. READ 0 bytes
Time:14.541s. new request
Time:14.544s. SENT 1 bytes
x53 S

Time:14.891s. s:500
Time:14.891s. READ 0 bytes
Time:14.892s. s:5
Time:14.898s. new request
Time:14.899s. SENT 1 bytes
x41 A

Time:15.053s. s:500
Time:15.054s. READ 0 bytes
Time:15.402s. s:500
Time:15.404s. READ 71 bytes
x32 x0D x0A x53 x65 x72 x69 x61 x6C x20 x70 x72 x6F x62 x6C x65 2..Serial.proble
x6D x20 x2D x20 x6E x6F x69 x73 x65 x20 x2D x20 x70 x6F x73 x73 m.-.noise.-.poss
x69 x62 x6C x65 x20 x63 x61 x62 x6C x65 x20 x6F x72 x20 x63 x6F ible.cable.or.co
x6D x70 x75 x74 x65 x72 x20 x68 x61 x72 x64 x77 x61 x72 x65 x20 mputer.hardware.
x70 x72 x6F x62 x6C x65 x6D problem

Time:15.531s. s:5
Time:17.493s. new request
Time:17.494s. SENT 1 bytes
x51 Q

Time:17.996s. s:500
Time:17.997s. READ 2 bytes
x4D x53 MS

Time:18.005s. new request
Time:18.009s. SENT 1 bytes
x53 S

Time:18.514s. s:500
Time:18.515s. READ 0 bytes
Time:18.516s. new request
Time:18.518s. SENT 1 bytes
x53 S

Time:19.021s. s:500
Time:19.022s. READ 0 bytes
Time:19.023s. new request
Time:19.025s. SENT 1 bytes
x41 A

Time:19.778s. s:750
Time:19.779s. READ 0 bytes
Time:19.793s. new request
Time:19.794s. SENT 1 bytes
x41 A

Time:20.297s. s:500
Time:20.298s. READ 0 bytes
Time:20.299s. s:5
Time:20.306s. new request
Time:20.308s. SENT 1 bytes
x41 A

Time:20.811s. s:500
Time:20.812s. READ 0 bytes
Time:20.813s. s:5
Time:20.819s. new request
Time:20.82s. SENT 1 bytes
x41 A

Time:21.323s. s:500
Time:21.324s. READ 0 bytes
Time:21.325s. s:5
Time:21.33s. new request
Time:21.332s. SENT 1 bytes
x41 A

Time:21.836s. s:500
Time:21.837s. READ 0 bytes
Time:21.837s. s:5
Time:21.843s. new request
Time:21.844s. SENT 1 bytes
x41 A

ErnestChristley

WAIT A DANG MINUTE!!

Shadowlogger IS getting data back from the MS. The MS is saying, "Serial.problem.-.noise.-.possible.cable.or.computer.hardware.problem". That is the data that Shadowlogger is recording. The only way Shadowlogger could be seeing that is if:
1) MS sent it.
and
2) The Bluetooth connection was actually working.

Something is wrong with the bluetooth adapter's serial TX line. The serial RX line HAS to be working, or I wouldn't be getting the message from the MS.

Does this sound right?

evil, I don't think TS can log the data going through the serial port. Could you possibly try connecting with an Android device using ShadowLogger or connecting to your COM5 with Hyperterminal so that you can see if the MS is sending you the same message?

ErnestChristley

Just got a message from Phil Tobin. His suggestion is to make sure HW flow control is off. Sounds to me like that could be the trick.

rx7locost

Yeah, if you have flow control on the bluetooth's virtual com port set to anything but "none", It will not communicate propery if at all.

Sorry if this was one detail I left out. I hope this is the issue. My fingers are crossed.

ErnestChristley

Verified the flow control. Didn't help.

Neither did slowing the baud rate.

Shadowlogger is sending the command to tell the MS to send a log ('Q' or 0x51). And there is definitely readable data coming through from the MS.

I hypothesize that the adapter is sending a 3.3V signal, and the MS is expecting 5V.