Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • Cracked
    Participant
    Post count: 44

    Is it possible to connect a Bluetooth module to the osPID? I’ve seen a couple of projects which use the tx/rx pins on an Arduino, but being rather new to this, I’m not sure if there is an equivalent on the osPID, or if it is possible to configure some?

    Being able to monitor/log the input/output of the osPID without the need for a pc in close proximity would be brilliant!

    rhys
    Participant
    Post count: 20

    It could be done, but would likely require some modifications to the firmware and hardware to add in support for bluetooth serial comms. I’d have to look at the available arduino bluetooth modules and libraries to determine how extensive the modifications would be. My best guess without research would be that it would require a bluetooth serial comm library, some calls to setup the library, and switching out the serial comm commands to call to the bluetooth serial comm library instead of the standard serial I/O library. Shouldn’t be too difficult. On the hardware end, it would be a matter of whether the necessary pins are easily accessible on the osPID hardware.

    Alternatively, if there is a bluetooth module that supports two wire serial comm from the tx/rx pins without needing a library, it would only require gaining access to the serial tx/rx signals on the osPID. That might require a little hardware hacking, as if I remember correctly, the tx/rx signals are not broken out to any accessible pads/pins on the main PCB or I/O cards.

    I’ll investigate BT modules and reply again in a bit. I’m currently working on a custom firmware/hardware modification that would allow for dual PID loops, so I have some knowledge of how the whole thing works.

    rhys
    Participant
    Post count: 20

    Yep, found a bluetooth module on Spark Fun that would work, the RN-42. However, the hardware serial rx/tx pins are direct traces to the USB controller on the main PCB on the existing osPID design, so are not easily accessible. Even with access to the rx/tx pins, a custom daughtercard would need to be designed around the RN-42 module, as it runs on 3.3V and needs a bank of DIP switches for configuration.

    So, basically, you’re looking at a major hardware project, but few if any firmware changes are needed.

    I like the idea though. I could throw together a daughtercard design pretty quickly based on the RN-42, but I don’t have the necessary tools to assemble it at this time. That would still leave the issue of accessing the hardware rx/tx pins of the atMega on the osPID mainboard though.

    Cracked
    Participant
    Post count: 44

    Thanks for that Rhys. Probably beyond my skills at this point. Would their be any way to use the usb socket itself for access to the tx/rx? I’m guessing it’s not powered though.

    I was looking at something like this http://www.ecrater.com.au/p/12261343/arduino-bluetooth-module-slave-wireless?gps=1

    And this

    http://www.chetanpatil.info/1/post/2011/10/11th-post-testing-bluetooth-module-with-arduino-mega-2560.html

    rhys
    Participant
    Post count: 20

    That module would either require access to the RX/TX pins for the hardware serial, which you don’t have on the osPID mainboard, or modifying the firmware to use a software serial library attached to two of the free I/O pins. The firware is easier to modify than the software, but either way, it’s a chore.

    rocketscream
    Keymaster
    Post count: 65

    You definitely can use SoftSerial to communicate with the Bluetooth module preferably at lower baud rate (9600) to reduce the amount of interrupt that takes place.

    Cracked
    Participant
    Post count: 44

    would something like an xbee be easier?

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.