Skip to content
Nemo157 edited this page Oct 16, 2011 · 2 revisions

Present: Andrew, Henry, Simon, Wim, Zac

Agenda

  • Code list
  • Work out what peripheral code still needs working on
  • CIJoe
  • Follow up letter to Jeremy
  • CAN Bus protocol stack
  • DeviceNet
  • CANOpen
  • CANaerospace
  • MilCAN
  • SAD J1939
  • ISO1192
  • State Diagrams
  • Can we make a page with all diagrams on it?
  • CAN network data flow diagrams?
  • Mounts
  • Break LA
  • Speed Sensor

Notes

###Software Job checklist

  • CAN

  • Motor

  • USART to Student Board
  • Student Board
  • Brake
  • LA controller (half way done)
  • Comms
  • USB √
  • Sensor
  • Speed
  • Steering
  • Position √
  • Limit switch

CI Joe

CI server, spamming us! Can we get emails to the committer

CAN Bus Protocol

Wim is going to read up about them

State Diagrams

void main() {
    can_init();
    enter_init();
    this_init();
    wait_for_others();
    while(1)
        loopy_stuff();
   }
}

State diagram main points are:

  • All boards hold state
  • The state handling is very tightly integrated with the CAN
  • It's a shared module between all boards

The PID is in a while loop, incoming data is copied into a variable (or left in a mailbox) thin dealt with in the main loop.

Mounts.

  • Break should be done next week
  • Same with limit switches
  • Speed sensor hasn't been looked at

Deliverables

  • CAN Protocol feedback
  • Protocol Module concept
  • Finish low level code module
  • Zac's looking speed sensor