Br46 v1

From DIDEAS Wiki
Revision as of 00:43, 31 October 2010 by Ceb (talk | contribs)
Jump to: navigation, search

PF Users Navigation:

Edit

getting started

  • power the board with 10-25 volts. It should consume ~120mW. And when first powered, the red light flash indicating that it is discoverable by other BT devices.

Initial BT configuration

  • Can communicate directly with the BT module from the 'IMU1' port. With a virgin module, the baud rate is 9600, N, 8, 1. Or just 'do_serial.py <port> 9600' You can connect a PSER directly to this port.
  • Verify module communication with the command "AT" <CR>
  • Change the radio name with 'ATSN, radio_name'
  • may need to issue fast data mode to radio at boot
  • may want to ignore UART data until connected. (ATSW25)
  • The BT module baudrate needs to be configured to 115,200 to work with the robot. Issue this command:
    • ATSW20,472,0,0,1 <CR>
    • See section 3.6.7 for details.
    • will need to re-connect do serial at this point
  • May wish to change the passcode at some point. It is 'default'


wireless BT connection

  • Should be able to pair with the module with standard PC software. Using the pass code 'default'
  • When 'connected' the blue LED is visible.
  • When a BT connection is made or broken, the module reports over the serial port. These message could interfere with FUP command processing.

SC connection

  • Connect the robot FUP to the port labeled SC1
  • Use the port SC2 for programming and communication (with either PSER or SWIFI).
  • If no other device is connected to the SC2, then the BT module will be able to communicate with the robot connected at SC1


issues

  • when sending data wireless to the module, it appears to be very slow and only accept data periodically. (The TX signal shows bursts of data.)
  • when sending data wired to the module, it accepts and transmits it rapid. at 115k baud, not RTS negation, but at 921k there is RTS negation


development

46 class 2

40 class 1

mosfets

battery module


logic

note

  • PSer2hb leaves IO pins as NC. Will need to add pullup/pulldown
  • Pser1 probably also leaves IO as NC.
  • want to use FUP IP pin to disconnected on-board bluetooth Rx driver.


fuses and holders