Doesn't work with Bluetooth Serial USB

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Connect a usb bluetooth dongle (I'm using Blue Radios 4.0 Low Energy) to my 
Windows 7 Laptop. Putty is able to see the bluetooth data just fine from the 
arduino (using COM4, baud 115200)
2. Install ths as3-arduino-connector ANE in Flash CS6 (and the dll of course).
3. The socketData event gets triggered only one time in Flash, and strangely, 
only after PUTTY was running. If I publish the flash app again, no data. Need 
to reopen PUTTY, see the data there, close PUTTY, then run the flash app again, 
and then get only one data event again.

What is the expected output? What do you see instead?
Expected to see continuous data events in Flash, not just the first one.

What version of the product are you using? On what operating system?
Windows 7, latest as3-arduino-connector on Flash CS6

Please provide any additional information below.

I got a usb bluetooth dongle (Blue Radios 4.0 Low Energy). When I use Putty, I 
am able to see the arduino data just fine via bluetooth (the usb dongle directs 
this data to the serial connection on com4 on my windows 7 laptop). But I 
cannot read this into Flash.  I can connect in Flash, but the socketData 
handler only triggers once (and strangely, only after I had PUTTY running, must 
rerun PUTTY each time, and then run Flash to get just one data trigger). From 
Putty, I do need to send the bluetooth dongle the commands "at", and then 
"atdmle,ecfe7e101354" which is to connect to my bluetooth device on the 
arduino. After that, the data comes through fine on Putty. So I thought I need 
to use the Ardunio send command from Flash to send these initial commands. 
Tried that but also doesn't work. I've tried using TinkerProxy, same exact 
issue (and I tried using the update of Tinkerproxy with a fix for bluetooth, 
doesn't work). Any ideas much appreciated. Thanks!

Original issue reported on code.google.com by andrexz...@gmail.com on 28 Mar 2013 at 12:34

[GoogleCodeExporter]

Just to mention, I've tried my setup with a USB serial cable instead of the 
bluetooth USB, and it works perfect. I get continous data events. So my arduino 
is working fine. For whatever bizzare reason, FLash does not see the bluetooth 
serial data in the same way as it sees serial data over a cable.

Original comment by andrexz...@gmail.com on 28 Mar 2013 at 12:36

[GoogleCodeExporter]

This should be fixed with the DTE controller.  Emulated USB serial ports don't 
support the DTE pin -- most likely the Bluetooth controller does (it would make 
sense -- you would want to use DTE for a shared medium like that).

In the recently released 1.5.0, there is a new parameter called "useDtrControl" 
in the connect function, which will set the DTR properly for the device.  Give 
that a shot and see if that makes a difference.

Original comment by Nicholas...@gmail.com on 23 Apr 2013 at 3:35

• Changed state: MoreInfoNeeded