$7 bluetooth WORKING on MS1!

[gndan]

Ok I have just tested it and no luck. Could this be due to my USB to Serial adaptor? I am seeing 1.97v on the RS-out pin with the adaptor plugged in and ~2.7v with it unplugged from the bluetooth. Im using the MS3 to supply the 5v source.

,Dan

[transaxel]

OK! Here´s my solution. I ordered this unit (looks the same as the cheap one from the US) but has the Serial Converter included to change the settings of the module. This module should also work on 5V. I´ve ordered two of them an they works perfect.

http://www.ebay.at/itm/250968195349?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649

[FricFrac]

Ah beat me to the punch! I've been playing around with this module off and on since January (lol ordered it in October - busy busy I found out that there are several different "configurations" for this device. Apparently they refer to them as a Slave and Master. The Slave can act as a DTE or DCE - apparently the Master version doesn't work for our application and is often sold as the cheaper version. These are often sold as a pair with a USB interface to the blue toothe adapter which also allows programing the device. Guess what was on my "to order list" ;P

[elaw]

Hey... has anyone successfully done a firmware update using this type of setup?

I tried to update my MS3 to the latest beta yesterday and it was NOT interested in working. The firmware uploader didn't recognize the bluetooth com port, either via autodetect or when I manually entered it.

Problem easily solved by hooking up a cable, but just wondering what others' experience has been with this?

[transaxel]

Hey... has anyone successfully done a firmware update using this type of setup?

I tried to update my MS3 to the latest beta yesterday and it was NOT interested in working. The firmware uploader didn't recognize the bluetooth com port, either via autodetect or when I manually entered it.

Problem easily solved by hooking up a cable, but just wondering what others' experience has been with this?

Yep, I´ve updatet several times via BT. But it is much slower than an update via adapter cable.
Firmware Uploader with autodetect?? TunerStudio works with yout BT adapter? If TS is working correct and only the FW Uploader has problems, i think that your
system settings of your virtual Com Port are not correct.

[Monzsta]

I've updated firmware several times, but when dabbling with an Alpha build I had a configuration error that the bluetooth wouldn't sync quickly enough in the beginning to catch. Toggle the switch, plug in the serial, open hyperterm, and voila! I had 90 degrees of map sampling when the firmware needed less. So after the diagnostic and the wayward config setting changed I was back on bluetooth.

[gndan]

I got mine up and running tonight, Using the USB-TTL convertor I bought it was a breeze and everything fell into place! As far as range goes I had my ECM on the stim and it was in my living room and I was getting 10 frames per second still in my neighbor's front yard! lol

Thanks, Dan

[Hardwyre]

It does indeed look like they come in master and slave modes. Now sure how to change the mode, but it should be possible. Seems like what mode it's in changes the way it handles data.

http://www.elechouse.com/elechouse/inde ... cts_id=602

[Hardwyre]

Here we go. These might be helpful:

http://www.bestelecs.com/wiki/index.php ... T_Commands

AT Commands

Users can use AT commands to setup the module with different configurations. Every AT command must be followed with <CR> and<LF> control character which is 0x0D and 0x0A in hexadecimal. Every AT command will followed with a response "OK". They will be some basic AT command you should know.

AT
AT command is use to test the module to see if it is OK.

AT+RESET
AT+RESET command is reset the module back to power up status.

AT+ROLE?
AT+ROLE? command inquiry the module's role, 0 = Slave, 1 = Master, 2 = Slave-loopback.

AT+ROLE=<param>
AT+ROLE command is used to set the module with master or slave, 0 = Slave, 1 = Master, 2 = Slave-loopback. You have to configure one module to master and the other to slave to become a pair.

AT+CMODE?
AT+CMODE? command inquiry the link mode. 0 = Specific bluetooth link address, 1 = Any bluetooth link address, 2 = Slave-loopback

AT+CMODE=<param>
AT+CMODE command is used to setup module link mode. 0 = Specific bluetooth link address, 1 = Any bluetooth link address, 2 = Slave-loopback. It is better to set the mode to 1 if you only have one pair device, because it is much easier to make them a pair.

AT+PSWD?
AT+PSWD? command inquiry the password of the module.

AT+PSWD=<param>
AT+PSWD command is used to set the pairing password.

AT+UART?
AT+UART? command inquiry the uart configurations.




http://www.seeedstudio.com/wiki/Grove_- ... figuration

Commands to change default configuration
1. Set working MODE
\r\n+STWMOD=0\r\n Set device working mode as client (slave). Save and Rest.
\r\n+STWMOD=1\r\n Set device working mode as server (master). Save and Rest.
Note: \r\n is necessary for operation and the value of are 0x0D 0x0A in Hex. \r and \n represent carriage-return and line-feed(or next line),

2.Set BAUDRATE
\r\n+STBD=115200\r\n Set baudrate 115200. Save and Rest.
Supported baudrate: 9600, 19200,38400,57600,115200,230400,460800.

3. Set Device NAME
\r\n+STNA=abcdefg Set device name as “abcdefg”. Save and Rest.

4. Auto-connect the last paired device on power
\r\n+STAUTO=0\r\n Auto-connect forbidden. Save and Rest.
\r\n+STAUTO=1\r\n Permit Auto-connect. Save and Rest.

5. Permit Paired device to connect me
\r\n+STOAUT=0\r\n Forbidden. Save and Rest.
\r\n+STOAUT=1\r\n Permit. Save and Rest.

6. Set PINCODE
\r\n +STPIN=2222\r\n Set pincode “2222”, Save and Rest.

7. Delete PINCODE(input PINCODE by MCU)
\r\n+DLPIN\r\n Delete pincode. Save and Rest.

8. Read local ADDRESS CODE
\r\n+RTADDR\r\n Return address of the device.

9. Auto-reconnecting when master device is beyond the valid range (slave device will auto-reconnect in 30 min when it is beyond the valid range)
\r\n+LOSSRECONN=0\r\n Forbid auto-reconnecting.
\r\n+LOSSRECONN=1\r\n Permit auto-reconnecting.

[Hardwyre]

The module's PIO11 (Pin32) is a mode selection pin to swith between normal mode and AT command mode. In the application schematic, it is connected to a button S1. When it is press down the module enter AT command mode, it come back to normal mode if the button is released. Note that, when the link is not established, once the module enter AT command mode, it will not come back to normal mode until link established or send a AT+RESET command or re-power the module.

For the people who have little buttons on their modules, this might explain why they have problems after pressing those buttons.

[Hardwyre]

This isn't the best news. I'm thinking the people who are having a lot of problems with connections have slave or slave-mode modules and probably need master-mode. I believe the little dongles that go into the computers/laptops are slaves, and the MS needs a master mode board. This is speculation, but it's a thought.

AT+ROLE? should tell you what mode your chip is in.

Edit: Maybe I have the slave/master relationship backwards:

Use the cheaper EGBT-046S if your application will
connect to a master Bluetooth device, such as PC
or laptops. Use the EGBT-045MS if your application
must connect to a slave Bluetooth device, such as
with EGBT-046S. Note that EGBT-045MS will work
as well as a slave Bluetooth device

http://www.e-gizmo.com/KIT/images/EGBT- ... %201r0.pdf

EGBT-045MS and EGBT-046S are generic Bluetooth Modules loaded with SPP firmware for UART
wireless cable replacement functions. The EGBT-
045MS can be configured by the user to work either
as a master or slave Bluetooth device using a set of
AT commands.

EGBT-046S, on the other hand, is permanently programmed as Bluetooth slave device. EGBT-046S,
because of its simpler function, is a lot easier to
use, and of course, costs less than EGBT-045MS.
You can use it straight out of the box as a UART
wireless cable replacement, without any need to
add set-up codes in your microcontroller application
firmware.

[Hardwyre]

Slave - EGBT-045MS acts as discoverable wireless
UART device ready for transparent data exchange.

Master - Scans for a remote bluetooth (slave) device,
pairs, and setup connection for a transparent
data exchange detween devices

Slave-Loop - Data loop-back Rx-Tx. Used mainly for
testing.

[chris_the_rat]

Recieved my unit, same as transaxel, but am having trouble with hyperterminal. when i send AT i get no OK. I type in AT and hit return and in the terminal window i get a linefeed. I played around with settings in hyperterminal but dont really understand anything... Tested downloading realterm and it indicates that I get connection via USB port 9 but also here I get no OK back when sending AT. Any clues to what I am doing wrong?

[Fabius72]

I received mine yesterday, but same problem. I was very frustrated.
This morning I have solved everything.

- Are you typing capital "AT"?
- Are you sure you are using right baud rate?

My bluetooth adapter was sell already programmed as 115200 baud, but connected to MS can't read anything!
Played a lot with miniterm/hyperterminal. No "OK" return.
After some attempts I have discovered that instead 9600 baud were correct.
At 9600 baud sent AT+BAUD8 to change the rate to 115200.

- Have you also changed "Flow control" to "none"? Mine was running after this.

Good luck!


Fabio

[PSIG]

It's been a while since I did some of these, but I have a few suggestions. Use a SLAVE version. Your laptop or phone is the master (configures the BT connection), and you just want a slave for MS.

I use H-Term http://www.der-hammer.info/terminal, as many of these modules cannot use CF/LF, but also cannot take HyperTerm's character-at-a-time mode. H-Term is one free program that allows you to enter your string, then click Send and it sends the whole string at once. It has worked with all the modules I have tried.

There are several versions of the modules with several firmware versions. Search the web for different BT module commands and try them until you find the ones that work with your module. You can also ask the seller for them. I most commonly find BT0417C HC06 modules that are named "linvor", but even those can have different firmwares and commands.

The others are right - most come programmed for 9600,8,N,1

Use a USB-to-TTL converter to program the modules. I did not find direct serial port programming to be reliable, although the USB/serial adapters like used for MS often work. Be sure to connect Tx to Rx and vice-versa.

Most eBay modules reply to AT programming commands:
AT (send) should respond with "OK"

AT+BAUDx (send) will set baud rate, where x =
1---------1200
2---------2400
3---------4800
4---------9600
5---------19200
6---------38400
7---------57600
8---------115200 (usually max stable)
9---------230400
A---------460800
B---------921600
C---------1382400
So, AT+BAUD4 (send) will respond with OK9600. When you change baud, communication will be lost until you change H-term to the new speed.

AT+PINxxxx (send) sets any 4 numbers as PIN or passkey for pairing. Responds OKsetpin

AT+NAMExxxxxxxxx (send) sets the broadcast module name. I think it's limited to 20 letters/numbers. Responds with OKxxxxxxxx

I have used these BT modules with MS, Honda OBD0, OBD1 and OBDII, and Ford EEC-IV (OBD1)and EEC-V (OBDv) ECMs with appropriate software. The speed is fine for most uses, but is a bit slower than a cable.

HTH,
David

[87quest-TSI]

Hi,

Has anyone got this to work on a MS2 3.57 board?
This is what I picked up and going to try to use.
http://www.ebay.com/itm/Bluetooth-Module-USB-6Pin-Serial-Port-Adapter-fr-Multiwii-Quadcopter-Tuning-/150756438977?pt=LH_DefaultDomain_0&hash=item2319c8b3c1

Thanks

[PSIG]

Those are the types I've used, though I have not used one programmed by a seller with the broadcast name "japanboxz". I have not done a v3.57 with one internally. While you can get single BT modules for $7-8 (under $5 in quantity) and $2-3 for the USB to TTL converter with cable, that seller is charging double for the convenience of both together, but also they are in the US and shipping will be much faster than Asia. It's probably a reconfigured 'linvor' BT0417, in which case the AT commands I listed will work fine. Remember, you cannot connect this type of bluetooth module directly to the serial port of the MS. It can be wired directly into the MS using the 232 chip's power and ground, and the processor's Tx and Rx (bypass the MS board 232) - I recommend this method. Or, build the circuit at the beginning of the thread. Or connect a MAX232 chip between the BT module and the MS serial port and add a 470 ohm resistor in the Tx out. Or buy the type of module that already has serial port capability built-in, and plug it into your MS serial port.

David

While most of the BT modules in this thread can only communicate directly to the MS processor without an added circuit (an internal installation), this type BT module has an on-board 232 serial chip to talk through the MS serial port. No circuits to build. About $15 online. Remove the connector you don't use to make it smaller. A small jumper is needed to feed the 5v from MS correctly. I put one on the end of a 3-foot serial cable and positioned it at the corner of the windshield for better range:

[Rick Finsta]

PSIG:

I've got one of those adapters with the Male and Female DB9s on them coming, and I had a question. I read the more detailed writeup on the RX7 forum that you posted, and was wondering if perhaps this mod needed to be done for those who's boards aren't working? I realize that doing this means that you wouldn't need to mod the adapter (other than for programming it, obviously) as this would supply power to the adapter instead of the mod you pictured on the other forum, but could it be this handshaking trick that is causing others' adapters to not work?

Just a thought, and I'm thinking of trying this mod from the megamanual first...

[PSIG]

I don't recall posting to the other board, so that may not have been me. However, yes, the mod you linked to is to feed the 5v power through the DB-9 as I stated in my last post. Rather than multiple jumpers, I just lifted Pin 9 and fed 5v to it. Then you need to verify the module you get receives power through Pin 9. A jumper on the module may be required. Yes, there are different versions of each module type, and that is confusing the situation. The handshake mod may be required with certain modules, and I would certainly try it if the module is powered properly but there is no commo. You may be on it - that may be the hiccup some are having. I found that same mod worked for the mini-USB Tx-Rx module on a v3.0 board.

This is why I also suggested bypassing the 232 in the MS for the other modules, as trying to do a "plug 'n play" through the port is considerably more involved. As there are so many techniques that work, I think people are getting confused between them. I would suggest to others to pick either internal hookup or DB-9 plug-in, and follow one set of instructions for that method.

The primary considerations for a plug-in module is that MS needs to port power through the DB-9, and the module needs to have a 'translator' transistor circuit or MAX232 chip added so it can communicate with the MS 232 chip, and handshaking must obviously be functional, or the board modded to allow it.

An internal hookup bypassing the port needs none of these mods as it talks directly to the processor, and can have it's own plug or port for external mounting if desired, or simply a slot in the end-plate to poke the antenna section outside the box for improved range. The only connections for internal hookup are +5V, GND, Tx and Rx.

Once the parameters to each type are understood, the process is rather simple. Have fun!

David

[Rick Finsta]

Oops- I thought you were also RX7locost on that board; I must've gotten the link from somewhere else and just assumed it had come from this thread.

So the mod I linked is the DB9 plugin method, correct? If so I'll just do that and see if it works...