P32 paper project

• BiomechDocs BL Knee PFresearchE
• Biomech Documentation links:
• AKCPU2z BLMD6c BLFT6c PSER1c Imu_2010 Emg_2009 Ric Upd_pcb

• kknee1 knee2 P32_paper_project Pic32

• Wireless Radio (WIP2b)

• Microchip Tools For Coding, Programming

• Using the Powerfoot (Pf_users)

• Biomech Manual

Edit

LED status lights on P32

#define LED_BACKGROUND_TGL   0x80   // orange
#define LED_MSG_VALID        0x40   // green2
#define LED_UART_EVENT       0x20   // red
#define LED_UART_QUEUE_EVENT 0x10   // blue
#define LED_TIC_TIMER        0x08
#define LED_MAIN_LOOP        0x04
#define LED_MSG_ERR          0x02
#define LED_CLUTCH           0x01   // white : used by the solinoid!

Telemetry access (PSW1, PSW2)

• wifi_fast.py -i bmech4 -V ak_p32 -f xx -F
• details at Biomech_wireless

special commands

"do_command.py" can be used to query the SC and MC for specific information.

• There is a long list of commands - some are even documented!
• A short list:

1. 104 - get the demux state and SM state of the SC statemachine
2. 1101 - read the MC mode
3. 1106 - read the MC encoder
4. 1420 - get the of the MC statemachine

• example : do_command.py -i bmech4.media.mit.edu -s 104

with PSER2h

• PSW1 and PSW2 are not isolated, but also do NOT provide 3.3V. The PSER2h is isolated and needs 3.3V to power the isolator. Thus it may not be possible to connect to the PSER2h without modifications

firmware architecture

The old SVN server is now longer active. Efforts are underway to add the old SVN dump to a new lab maintained server.

• The temporary location of the firmware is:

https://bmech.media.mit.edu:8443/svn/ric_powerfoot/trunk

P32 user level

• The state controller operates in a mid priority level thread. This means that it will interrupt lower priority threads. Before and after calling the statemachine other actions are performed:

1. Receive and decode the 'dataport' message from the robot
2. Populate the remote sensors objects from the DP message
3. Calls the user statemachine (which can send a command to the robot)
4. Sends the dataport message.

• This mid priority level thead

• The main loop is used as a background thread. At present its doing printf and actually calls ms_delay(100)!

system level

• Upon power on:

P32

1. the P32 waits for the robot MC to signal "boot success";
2. after which it takes control of the MC and command current mode
3. then starts calling the user statemachine

MC

1. waits for commands either from the SC or the P32

SC

1. monitors sensors and commands MCs to commutate and retries if necessary
2. on success, enters an idle state (and remains there)

todo

1. are ADCs mapped as expected?
2. add command timeouts in MC firmware;
3. thread safe / mappable printf
4. DMA to RX robot dataport
5. DMA to TX SWIFI dataport

1. DONE make sure SC boots MC and then enters idle state
2. DONE mappable getchar
3. DONE : DMA to read ADCs

system integration

knee1.pcb 4-15-2010

• PSW1, PSW2 need TX/RX crossover cable. (Eg signals TX/RX needs to be switched)
• PSW1 (or 2) need supply voltage to pin (1??)
• PISP requires cross over for both PGC / PGD and TX/RX
• PMC1, PSC1 use normal straight calbles, however require 3.3V to power the isolated driver.

connections

Jst_1mm_connectors