I had an idea of directly connecting to the M100 over BT, but it sounds like it may not work with no hardware flow control...I recently purchased a Bluetooth 4.0 Console Adapter for Raspberry Pi (see http://www.mindsensors.com/rpi/75-bluetooth-40-console- adapter-for-raspberry-pi) and it works great for its intended use. It is essentially a BlueSmirf module soldered to a shield that snaps onto a Raspberry Pi computer. It is designed to allow a serial terminal connection to be created to the Raspi using an Android phone or other BT enabled device. No configuration is necessary on the Raspi side as it uses the GPIO serial port on the Raspi itself (Raspbian has ttyAMA0 configured by default for console connection).
My thought was, the BlueSmirf has an interesting AdHoc mode that I was thinking *might* be made to work with Steve's BlueM device. My hope was to create a "zero config" solution to connect the M100 to the Raspi (the "config" would be permanently saved inside of the two BlueSmirf modules). In theory, all that would be needed would be LaddieAlpha/DLPlus running on the Raspi (talking via ttyAMA0) and NEWDOS on the M100 talking via the BlueM. So far, I have not had any luck getting into the BlueSmirf configuration mode on either module (hitting the "$$$" on startup, etc). Tom Hoppe On Tue, Dec 22, 2015 at 10:17 AM, John R. Hogerhuis <[email protected]> wrote: > On Tue, Dec 22, 2015 at 10:09 AM, Jonathan Yuen <[email protected]> > wrote: > > Hello, > > > > Congratulations on your pi. You know that there IS a serial port built > in on the GPIO bus and you don't really need a USB-RS-232 converter. But > the signal levels on the GPIO need a converter from ttl to rs-232 signal > levels. Look for something with a MAX232 on it. That's how I connect my > m100 to a pi. > > > > Jonathan > > > > That's true... but FWIW, that won't give you flow control since the Pi > is a straight 3 wire affair for the built in serial port. HTERM uses > hardware flow control. > > -- John. >
