switchable bluetooth module via a tx aux channel, is it pos?
Posted: Tue Jan 17, 2012 10:41 pm
right read lots of stuff about multiwii gui over bluetooth and android, but not many about the gui over bluetooth and a pc/laptop.
so found out that it's not that easy, sumit to do with windows bluetooth drivers and something called a 'stack', found the toshiba driver thingy but that didnt work, saw the one post about widcomm drivers, but it was to hard to find them; found some obscure site via the multiwii forum that was dealing with an arduino/bluetooth problems.
well the fix that they had worked out worked like a charm, all you got to do is replace this file in 2 places and heypresto multiwii gui over bluetooth on a windows 7 netbook.
the HP netbook would find the bluetooth module, install 2 serial com ports
but then it all went to poo, the 2 ports it installed 1 was incomming and 1 outgoing but it needs to bridge the com ports but windows standard drivers cant do it (well i could not get them to do it) so replaced the .dll file in the two locations making sure to backup the originals and took the plunge.
hooked up the bt to my shield and powered it up, then loaded the gui and hoped, up it came with the 2 com ports showing so i clicked the bottom of the 2 and it went green (so far so good) clicked start and it sprang into life.
did a little check everything was there and configurable, worked just like it was hooked up via usb.
so thinking this was a fluke i closed the gui unpluged the power to my shield and then repowered it up and re-ran the gui just to see if it would work again.
as if by magic up comes the gui and the 2 com ports and so clicked the bottom one and it worked just like before.
i also restarted the netbook because i thougth that a reboot was needed to test if it wasn't real, hooked up my shield to the gui via usb and that worked fine, then tryed with the BT again and it still works.
now i can take my netbook with me to the field and make whatever changes i want.
sorry if this has been posted before but i could not find a simple fix, so here it is, tested with the dev version working fine.
this abbility to do some realtime debuging is great, with the addition of some windows screen grabber software, i can now video the gui and then play them back to see just what was going on during pid setup and tuning.
as long as you dont go out of range of the BT you should be fine.
Now i need a way of software switching the BT module on and off via my tx?,
as i dont code i will be relying on the experiance of others to help me with this problem.
not sure if this is poss but i dont see why not, all i need to have is it hooked up to vcc, gnd, rx, tx and be able to software switch the the vcc line.
i hope!!??
many thanks RCT
so found out that it's not that easy, sumit to do with windows bluetooth drivers and something called a 'stack', found the toshiba driver thingy but that didnt work, saw the one post about widcomm drivers, but it was to hard to find them; found some obscure site via the multiwii forum that was dealing with an arduino/bluetooth problems.
well the fix that they had worked out worked like a charm, all you got to do is replace this file in 2 places and heypresto multiwii gui over bluetooth on a windows 7 netbook.
the HP netbook would find the bluetooth module, install 2 serial com ports
but then it all went to poo, the 2 ports it installed 1 was incomming and 1 outgoing but it needs to bridge the com ports but windows standard drivers cant do it (well i could not get them to do it) so replaced the .dll file in the two locations making sure to backup the originals and took the plunge.
hooked up the bt to my shield and powered it up, then loaded the gui and hoped, up it came with the 2 com ports showing so i clicked the bottom of the 2 and it went green (so far so good) clicked start and it sprang into life.
did a little check everything was there and configurable, worked just like it was hooked up via usb.
so thinking this was a fluke i closed the gui unpluged the power to my shield and then repowered it up and re-ran the gui just to see if it would work again.
as if by magic up comes the gui and the 2 com ports and so clicked the bottom one and it worked just like before.
i also restarted the netbook because i thougth that a reboot was needed to test if it wasn't real, hooked up my shield to the gui via usb and that worked fine, then tryed with the BT again and it still works.
now i can take my netbook with me to the field and make whatever changes i want.
sorry if this has been posted before but i could not find a simple fix, so here it is, tested with the dev version working fine.
this abbility to do some realtime debuging is great, with the addition of some windows screen grabber software, i can now video the gui and then play them back to see just what was going on during pid setup and tuning.
as long as you dont go out of range of the BT you should be fine.
Now i need a way of software switching the BT module on and off via my tx?,
as i dont code i will be relying on the experiance of others to help me with this problem.
not sure if this is poss but i dont see why not, all i need to have is it hooked up to vcc, gnd, rx, tx and be able to software switch the the vcc line.
i hope!!??
many thanks RCT