Mech - User contributions [en]

ME333 Unofficial Sample Code

2013-02-25T06:35:20Z

AlexAnsari: /* Extra PIC32 Code */

'''DO NOT USE SAMPLE CODE ON THIS PAGE! IT IS STILL IN TESTING MODE. USE [[ME333_Sample_Code|THIS PAGE]] INSTEAD.'''

Code for ME333 instructors to test before it goes live.

Code with '''TESTED''' has been tested and is ready to go live.

Code with '''EDITS''' has been updated but not fully test.

Code without any marking has not been looked at yet.

== PIC32 Code ==

'''Bootloader Project'''
* '''1/30/2013''' [[Media:NU32_bootloader.zip|NU32_bootloader.zip]]: (Updated 1/30 to make it jump to the noncacheable virtual address, not cacheable, just for conceptual clarity.) All files in one folder. Kevin's version building on Nick's. Jumps to application at new jump location that doesn't waste flash. Also sets config bits for Shadow Register Set.
* '''1/20/2013''' [[Media:NU32_old_bootloader.zip|Nick's bootloader app as of Jan 20, that doesn't compile]]

'''Simple PIC'''
* '''TESTED 1/16/2013''' [[Media:simplePIC.c|simplePIC.c]]: Flashes LEDs on the NU32 unless the USER button is pressed.
* '''TESTED 1/16/2013''' [[Media:simplePIC_standalone.c|simplePIC_standalone.c]]: Standalone version of simplePIC.c.

'''NU32 library, header file, procdefs, and terminal comm test'''
* '''1/17/2013''' [[Media:talkingPIC.c|talkingPIC.c]]: echoes strings sent from keyboard back to computer screen
* '''1/21/2013''' [[Media:NU32bootloaded.ld|NU32bootloaded.ld]]: Use this linker script when creating executables to be bootloaded on NU32 (not app.ld). Kevin's version which puts the program starting at 0x9D000000, allowing access to full amount of flash.
* '''1/20/2013''' [[Media:NU32.c|NU32.c]]: NU32 board library.
* '''1/28/2013''' [[Media:NU32.h|NU32.h]]: NU32 header file, updated to have config bits for Shadow Register Set and to include <plib.h>.
* [[Media:NU32_serial_comm.c|NU32_serial_comm.c]]: Serial communication test with the terminal.
* [[Media:NU32_serial_plot.c|NU32_serial_plot.c]]: Plot data with serial communication in NU32_Utility.

'''LCD code (to be moved into NU32.c)'''
* [[Media:LCD.c|LCD.c]]: LCD library.
* [[Media:LCD.h|LCD.h]]: LCD header file.
* [[Media:LCDtest.c|LCDtest.c]]: Test program for LCD library.

'''Serial Sample code for Invest.c'''
* [[Media:NU32_serial_for_invest.c|NU32_serial_for_invest.c]]: An example of serial communication, useful for converting invest.c to the PIC32.

'''Communication Examples'''
* Serial to a terminal
* Serial to MATLAB
* Serial to Processing
* Output to the LCD

'''Digital I/O'''
* [[Media:DIGIO_sfrs.c|DIGIO_sfrs.c]]: Digital I/O and change notification using SFR manipulation.
* [[Media:DIGI0_plib.c|DIGIO_plib.c]]: Digital I/O and change notification using the peripheral library.

'''Counter/timer'''
* [[Media:TMR_16bit.c|TMR_16bit.c]]: Set up a 16-bit timer to count the PBCLK.
* [[Media:TMR_16bit_external_clocks.c|TMR_16bit_external_clocks.c]]: Count two external clock sources, such as the A and B channel from a motor encoder.

'''Interrupts'''
* [[Media:INT_core_timer.c|INT_core_timer.c]]: Interrupt on core timer period match.
* [[Media:INT_ext_int.c|INT_ext_int.c]]: Interrupt on rising edge of external interrupt line INT0.
* Peripheral timer interrupt.

'''Output compare (PWM)'''
* [[Media:OC_PWM_nolib.c|OC_PWM_nolib.c]]: Set up PWM by setting SFRs.
* [[Media:OC_PWM_lib.c|OC_PWM_lib.c]]: Set up PWM using peripheral library functions.
* [[Media:OC_square_wave.c|OC_square_wave.c]]: Alternate between two different PWM duty cycles at 1 Hz. PWM is at 100 kHz and can be low-pass filtered to get a square wave analog output.

'''Analog to digital'''
* [[Media:ADC_Read2.c|ADC_Read2.c]]: Reads two analog inputs repetitively and prints the results to the user's terminal.
* [[Media:ADC_Read2_LCD.c|ADC_Read2_LCD.c]] Reads two analog inputs repetitively and prints the results to the LCD.
* Something else, scanning mode, asynchronous results check on the buffer, and/or interrupt generated when some results are ready.

'''Using the UART'''
* '''TESTED 2/6/2013''' [[Media:Uart_loop.c|Uart_loop.c]]: Simple RS232 communication: one UART to another on the same PIC
* '''TESTED 2/7/2013''' [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* '''TESTED 2/7/2013''' [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* '''TESTED 2/10/2013''' [[Media:Uart_ftdi.c|Uart_ftdi.c]]: Talking to a PC with an FTDI cable

'''Using I2C'''
* '''TESTED 2/20/2013''' [[Media:NU32_I2C.c|NU32_I2C.c]], [[Media:NU32_I2C.h|NU32_I2C.h]]: Library files.
* I2C1 to I2C2 on one PIC
* PIC to PIC
* '''TESTED 2/20/2013''' [[Media:I2C_DAC.c|I2C_DAC.c]]: MAX518 8bit I2C DAC
* '''TESTED 2/20/2013''' [[Media:I2C_ADC.c|I2C_ADC.c]]: NAU7802 24bit I2C ADC
* '''TESTED 2/20/2013''' [[Media:I2C_RAM.c|I2C_RAM.c]]: PCF8570 2kbit I2C SRAM

'''Using SPI'''
* '''TESTED 2/7/2013''' [[Media:SPILoopback.c|SPILoopback.c]]: SPI4 to SPI1 on one PIC
* PIC to PIC
* MCP4922 12bit SPI DAC
* MCP3008 10bit SPI ADC
* Microchip 23k256 256kbit SPI SRAM

'''Comparator'''
* '''TESTED 2/7/2013''' [[Media:Comparator.c‎|Comparator.c‎]]: Toggle an LED based on the relative state of two pins
* '''TESTED 2/7/2013''' [[Media:ComparatorOutput.c‎|ComparatorOutput.c‎]]: Output analogue ref voltage based on the difference between source pins
* turn a light on or off based on potentiometer reading

'''Input Capture'''
* '''TESTED 2/7/2013''' [[Media:Input_capture.c|Input_capture.c]]: Create a PWM signal (duty cycle controlled by a potentiometer) and read in to an input capture, display the pulse width or duty cycle

== Applications ==

'''DSP and FFT'''
* [[Media:DSP_sample_square_wave.zip|DSP_sample_square_wave.zip]]: Examples of FIR and FFT in both MATLAB and on the PIC32.
* [[Media:DSP_mips32_fft.zip|DSP_mips32_fft.zip]]: Example of using the Q31 mips library for FFT. Contains a C source file and a header file.

'''Reading a quadrature encoder with the dsPIC33FJ12MC201 breakout board'''
* [[Media:NU32_dsPIC_QEI_example.c | NU32_dsPIC_QEI_example.c]]: Read the encoder count at 250Hz, send to the computer at 5Hz

'''Controlling a stepper motor with the TB6612'''
* [[Media:NU32_stepper_example.c | NU32_stepper_example.c]]: Use the TB6612 to step the motor at 25 Hz steps (1 rev in 16s)

'''Controlling an RC servo motor'''
* [[Media:NU32_rcservo_pwm_example.c|NU32_rcservo_pwm_example.c]]: Use a PWM pin to set the position of the servo (note you only have 5 PWM pins)
* [[Media:NU32_rcservo_digio_example.c|NU32_rcservo_digio_example.c]]: Use any digital IO pin and a timer to set the position of the servo

== Extra PIC32 Code ==

'''USB'''
* '''TESTED 2/17/2013''' [[Media:USBHost-MassStorage.zip|USBHost-MassStorage.zip]]: Writes the voltage on an analog pin to a ADC.csv file on an external USB stick approx. 5 times per second. Writing starts when the USB is inserted and stops when the USER button is pressed. Remember to press the USER button to stop writing data before removing the USB stick. View the README.txt file to build
* HID to Processing on a PC
* CDC to PC

'''Watchdog Timer'''
* '''TESTED 2/7/2013''' [[Media:WatchdogTimer.c|WatchdogTimer.c]]: User button turns on LED the LED turns off again when PIC restarts due to watchdog timer
* Press a button every so often or watch the PIC reset itself (and perhaps a light stays off until you manually reset it or something)

'''Using the RTCC'''
* Keeping time: set time from a PC, display current time on same PC
* alarm clock demo?

'''Programming the onboard flash'''
* Flash self programming: displays saved data at power on, allows user to enter new data (button presses, whatever), displays the new data, and when you power cycle, PIC displays the most recent data on startup

'''Sleep, Idle, Freeze'''
* config bits?
* demonstrate little current usage in sleep mode; wake up at predefined intervals or on certain signals and do something (and see the spike in current usage?)

'''Using CAN'''
* Three PICs establishing a CAN bus: each PIC has a button and the state of the LEDs on each NU32 changes depending on which buttons are pressed (confirm communication between PICs)
* PC to PIC (Peak card?)
* some CAN chip? sensor?

'''DIP PIC32 with reconfigurable pins (1/2xx)''' (11/21)

* Reconfiguring the pins.

'''Data logging on a uSD card'''
* Using the Microchip FAT32 library, AN1045

File:USBHost-MassStorage.zip

2013-02-25T06:28:37Z

AlexAnsari:

ME333 Unofficial Sample Code

2013-02-07T23:41:34Z

AlexAnsari: /* PIC32 Code */

'''DO NOT USE SAMPLE CODE ON THIS PAGE! IT IS STILL IN TESTING MODE. USE [[ME333_Sample_Code|THIS PAGE]] INSTEAD.'''

Code for ME333 instructors to test before it goes live.

Code with '''TESTED''' has been tested and is ready to go live.

Code with '''EDITS''' has been updated but not fully test.

Code without any marking has not been looked at yet.

== PIC32 Code ==

'''Bootloader Project'''
* '''1/30/2013''' [[Media:NU32_bootloader.zip|NU32_bootloader.zip]]: (Updated 1/30 to make it jump to the noncacheable virtual address, not cacheable, just for conceptual clarity.) All files in one folder. Kevin's version building on Nick's. Jumps to application at new jump location that doesn't waste flash. Also sets config bits for Shadow Register Set.
* '''1/20/2013''' [[Media:NU32_old_bootloader.zip|Nick's bootloader app as of Jan 20, that doesn't compile]]

'''Simple PIC'''
* '''TESTED 1/16/2013''' [[Media:simplePIC.c|simplePIC.c]]: Flashes LEDs on the NU32 unless the USER button is pressed.
* '''TESTED 1/16/2013''' [[Media:simplePIC_standalone.c|simplePIC_standalone.c]]: Standalone version of simplePIC.c.

'''NU32 library, header file, procdefs, and terminal comm test'''
* '''1/17/2013''' [[Media:talkingPIC.c|talkingPIC.c]]: echoes strings sent from keyboard back to computer screen
* '''1/21/2013''' [[Media:NU32bootloaded.ld|NU32bootloaded.ld]]: Use this linker script when creating executables to be bootloaded on NU32 (not app.ld). Kevin's version which puts the program starting at 0x9D000000, allowing access to full amount of flash.
* '''1/20/2013''' [[Media:NU32.c|NU32.c]]: NU32 board library.
* '''1/28/2013''' [[Media:NU32.h|NU32.h]]: NU32 header file, updated to have config bits for Shadow Register Set and to include <plib.h>.
* [[Media:NU32_serial_comm.c|NU32_serial_comm.c]]: Serial communication test with the terminal.
* [[Media:NU32_serial_plot.c|NU32_serial_plot.c]]: Plot data with serial communication in NU32_Utility.

'''LCD code (to be moved into NU32.c)'''
* [[Media:LCD.c|LCD.c]]: LCD library.
* [[Media:LCD.h|LCD.h]]: LCD header file.
* [[Media:LCDtest.c|LCDtest.c]]: Test program for LCD library.

'''Serial Sample code for Invest.c'''
* [[Media:NU32_serial_for_invest.c|NU32_serial_for_invest.c]]: An example of serial communication, useful for converting invest.c to the PIC32.

'''Communication Examples'''
* Serial to a terminal
* Serial to MATLAB
* Serial to Processing
* Output to the LCD

'''Digital I/O'''
* [[Media:DIGIO_sfrs.c|DIGIO_sfrs.c]]: Digital I/O and change notification using SFR manipulation.
* [[Media:DIGI0_plib.c|DIGIO_plib.c]]: Digital I/O and change notification using the peripheral library.

'''Counter/timer'''
* [[Media:TMR_16bit.c|TMR_16bit.c]]: Set up a 16-bit timer to count the PBCLK.
* [[Media:TMR_16bit_external_clocks.c|TMR_16bit_external_clocks.c]]: Count two external clock sources, such as the A and B channel from a motor encoder.

'''Interrupts'''
* [[Media:INT_core_timer.c|INT_core_timer.c]]: Interrupt on core timer period match.
* [[Media:INT_ext_int.c|INT_ext_int.c]]: Interrupt on rising edge of external interrupt line INT0.
* Peripheral timer interrupt.

'''Output compare (PWM)'''
* [[Media:OC_PWM_nolib.c|OC_PWM_nolib.c]]: Set up PWM by setting SFRs.
* [[Media:OC_PWM_lib.c|OC_PWM_lib.c]]: Set up PWM using peripheral library functions.
* [[Media:OC_square_wave.c|OC_square_wave.c]]: Alternate between two different PWM duty cycles at 1 Hz. PWM is at 100 kHz and can be low-pass filtered to get a square wave analog output.

'''Analog to digital'''
* [[Media:ADC_Read2.c|ADC_Read2.c]]: Reads two analog inputs repetitively and prints the results to the user's terminal.
* [[Media:ADC_Read2_LCD.c|ADC_Read2_LCD.c]] Reads two analog inputs repetitively and prints the results to the LCD.
* Something else, scanning mode, asynchronous results check on the buffer, and/or interrupt generated when some results are ready.

'''Using the UART'''
* Simple RS232 communication: one UART to another on the same PIC
* [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* Talking to a PC with an FTDI cable

'''Using I2C'''
* I2C1 to I2C2 on one PIC
* PIC to PIC
* MAX518 8bit I2C DAC
* NAU7802 24bit I2C ADC
* PCF8570 2kbit I2C SRAM

'''Using SPI'''
* '''TESTED 2/7/2013''' [[Media:SPILoopback.c|SPILoopback.c]]: SPI4 to SPI1 on one PIC
* PIC to PIC
* MCP4922 12bit SPI DAC
* MCP3008 10bit SPI ADC
* Microchip 23k256 256kbit SPI SRAM

'''Comparator'''
* '''TESTED 2/7/2013''' [[Media:Comparator.c‎|Comparator.c‎]]: Toggle an LED based on the relative state of two pins
* '''TESTED 2/7/2013''' [[Media:ComparatorOutput.c‎|ComparatorOutput.c‎]]: Output analogue ref voltage based on the difference between source pins
* turn a light on or off based on potentiometer reading

'''Input Capture'''
* '''TESTED 2/7/2013''' [[Media:Input_capture.c|Input_capture.c]]: Create a PWM signal (duty cycle controlled by a potentiometer) and read in to an input capture, display the pulse width or duty cycle

== Applications ==

'''DSP and FFT'''
* [[Media:DSP_sample_square_wave.zip|DSP_sample_square_wave.zip]]: Examples of FIR and FFT in both MATLAB and on the PIC32.
* [[Media:DSP_mips32_fft.zip|DSP_mips32_fft.zip]]: Example of using the Q31 mips library for FFT. Contains a C source file and a header file.

'''Reading a quadrature encoder with the dsPIC33FJ12MC201 breakout board'''
* [[Media:NU32_dsPIC_QEI_example.c | NU32_dsPIC_QEI_example.c]]: Read the encoder count at 250Hz, send to the computer at 5Hz

'''Controlling a stepper motor with the TB6612'''
* [[Media:NU32_stepper_example.c | NU32_stepper_example.c]]: Use the TB6612 to step the motor at 25 Hz steps (1 rev in 16s)

'''Controlling an RC servo motor'''
* [[Media:NU32_rcservo_pwm_example.c|NU32_rcservo_pwm_example.c]]: Use a PWM pin to set the position of the servo (note you only have 5 PWM pins)
* [[Media:NU32_rcservo_digio_example.c|NU32_rcservo_digio_example.c]]: Use any digital IO pin and a timer to set the position of the servo

== Extra PIC32 Code ==

'''USB'''
* HID to Processing on a PC
* CDC to PC

'''Watchdog Timer'''
* '''TESTED 2/7/2013''' [[Media:WatchdogTimer.c|WatchdogTimer.c]]: User button turns on LED the LED turns off again when PIC restarts due to watchdog timer
* Press a button every so often or watch the PIC reset itself (and perhaps a light stays off until you manually reset it or something)

'''Using the RTCC'''
* Keeping time: set time from a PC, display current time on same PC
* alarm clock demo?

'''Programming the onboard flash'''
* Flash self programming: displays saved data at power on, allows user to enter new data (button presses, whatever), displays the new data, and when you power cycle, PIC displays the most recent data on startup

'''Sleep, Idle, Freeze'''
* config bits?
* demonstrate little current usage in sleep mode; wake up at predefined intervals or on certain signals and do something (and see the spike in current usage?)

'''Using CAN'''
* Three PICs establishing a CAN bus: each PIC has a button and the state of the LEDs on each NU32 changes depending on which buttons are pressed (confirm communication between PICs)
* PC to PIC (Peak card?)
* some CAN chip? sensor?

'''DIP PIC32 with reconfigurable pins (1/2xx)''' (11/21)

* Reconfiguring the pins.

'''Data logging on a uSD card'''
* Using the Microchip FAT32 library, AN1045

File:Input capture.c

2013-02-07T23:39:37Z

AlexAnsari:

ME333 Unofficial Sample Code

2013-02-07T21:59:02Z

AlexAnsari: /* PIC32 Code */

'''DO NOT USE SAMPLE CODE ON THIS PAGE! IT IS STILL IN TESTING MODE. USE [[ME333_Sample_Code|THIS PAGE]] INSTEAD.'''

Code for ME333 instructors to test before it goes live.

Code with '''TESTED''' has been tested and is ready to go live.

Code with '''EDITS''' has been updated but not fully test.

Code without any marking has not been looked at yet.

== PIC32 Code ==

'''Bootloader Project'''
* '''1/30/2013''' [[Media:NU32_bootloader.zip|NU32_bootloader.zip]]: (Updated 1/30 to make it jump to the noncacheable virtual address, not cacheable, just for conceptual clarity.) All files in one folder. Kevin's version building on Nick's. Jumps to application at new jump location that doesn't waste flash. Also sets config bits for Shadow Register Set.
* '''1/20/2013''' [[Media:NU32_old_bootloader.zip|Nick's bootloader app as of Jan 20, that doesn't compile]]

'''Simple PIC'''
* '''TESTED 1/16/2013''' [[Media:simplePIC.c|simplePIC.c]]: Flashes LEDs on the NU32 unless the USER button is pressed.
* '''TESTED 1/16/2013''' [[Media:simplePIC_standalone.c|simplePIC_standalone.c]]: Standalone version of simplePIC.c.

'''NU32 library, header file, procdefs, and terminal comm test'''
* '''1/17/2013''' [[Media:talkingPIC.c|talkingPIC.c]]: echoes strings sent from keyboard back to computer screen
* '''1/21/2013''' [[Media:NU32bootloaded.ld|NU32bootloaded.ld]]: Use this linker script when creating executables to be bootloaded on NU32 (not app.ld). Kevin's version which puts the program starting at 0x9D000000, allowing access to full amount of flash.
* '''1/20/2013''' [[Media:NU32.c|NU32.c]]: NU32 board library.
* '''1/28/2013''' [[Media:NU32.h|NU32.h]]: NU32 header file, updated to have config bits for Shadow Register Set and to include <plib.h>.
* [[Media:NU32_serial_comm.c|NU32_serial_comm.c]]: Serial communication test with the terminal.
* [[Media:NU32_serial_plot.c|NU32_serial_plot.c]]: Plot data with serial communication in NU32_Utility.

'''LCD code (to be moved into NU32.c)'''
* [[Media:LCD.c|LCD.c]]: LCD library.
* [[Media:LCD.h|LCD.h]]: LCD header file.
* [[Media:LCDtest.c|LCDtest.c]]: Test program for LCD library.

'''Serial Sample code for Invest.c'''
* [[Media:NU32_serial_for_invest.c|NU32_serial_for_invest.c]]: An example of serial communication, useful for converting invest.c to the PIC32.

'''Communication Examples'''
* Serial to a terminal
* Serial to MATLAB
* Serial to Processing
* Output to the LCD

'''Digital I/O'''
* [[Media:DIGIO_sfrs.c|DIGIO_sfrs.c]]: Digital I/O and change notification using SFR manipulation.
* [[Media:DIGI0_plib.c|DIGIO_plib.c]]: Digital I/O and change notification using the peripheral library.

'''Counter/timer'''
* [[Media:TMR_16bit.c|TMR_16bit.c]]: Set up a 16-bit timer to count the PBCLK.
* [[Media:TMR_16bit_external_clocks.c|TMR_16bit_external_clocks.c]]: Count two external clock sources, such as the A and B channel from a motor encoder.

'''Interrupts'''
* [[Media:INT_core_timer.c|INT_core_timer.c]]: Interrupt on core timer period match.
* [[Media:INT_ext_int.c|INT_ext_int.c]]: Interrupt on rising edge of external interrupt line INT0.
* Peripheral timer interrupt.

'''Output compare (PWM)'''
* [[Media:OC_PWM_nolib.c|OC_PWM_nolib.c]]: Set up PWM by setting SFRs.
* [[Media:OC_PWM_lib.c|OC_PWM_lib.c]]: Set up PWM using peripheral library functions.
* [[Media:OC_square_wave.c|OC_square_wave.c]]: Alternate between two different PWM duty cycles at 1 Hz. PWM is at 100 kHz and can be low-pass filtered to get a square wave analog output.

'''Analog to digital'''
* [[Media:ADC_Read2.c|ADC_Read2.c]]: Reads two analog inputs repetitively and prints the results to the user's terminal.
* [[Media:ADC_Read2_LCD.c|ADC_Read2_LCD.c]] Reads two analog inputs repetitively and prints the results to the LCD.
* Something else, scanning mode, asynchronous results check on the buffer, and/or interrupt generated when some results are ready.

'''Using the UART'''
* Simple RS232 communication: one UART to another on the same PIC
* [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* Talking to a PC with an FTDI cable

'''Using I2C'''
* I2C1 to I2C2 on one PIC
* PIC to PIC
* MAX518 8bit I2C DAC
* NAU7802 24bit I2C ADC
* PCF8570 2kbit I2C SRAM

'''Using SPI'''
* '''TESTED 2/7/2013''' [[Media:SPILoopback.c|SPILoopback.c]]: SPI4 to SPI1 on one PIC
* PIC to PIC
* MCP4922 12bit SPI DAC
* MCP3008 10bit SPI ADC
* Microchip 23k256 256kbit SPI SRAM

'''Comparator'''
* '''TESTED 2/7/2013''' [[Media:Comparator.c‎|Comparator.c‎]]: Toggle an LED based on the relative state of two pins
* '''TESTED 2/7/2013''' [[Media:ComparatorOutput.c‎|ComparatorOutput.c‎]]: Output analogue ref voltage based on the difference between source pins
* turn a light on or off based on potentiometer reading

'''Input Capture'''
* create a PWM signal (duty cycle controlled by a potentiometer) and read in to an input capture, display the pulse width or duty cycle

== Applications ==

'''DSP and FFT'''
* [[Media:DSP_sample_square_wave.zip|DSP_sample_square_wave.zip]]: Examples of FIR and FFT in both MATLAB and on the PIC32.
* [[Media:DSP_mips32_fft.zip|DSP_mips32_fft.zip]]: Example of using the Q31 mips library for FFT. Contains a C source file and a header file.

'''Reading a quadrature encoder with the dsPIC33FJ12MC201 breakout board'''
* [[Media:NU32_dsPIC_QEI_example.c | NU32_dsPIC_QEI_example.c]]: Read the encoder count at 250Hz, send to the computer at 5Hz

'''Controlling a stepper motor with the TB6612'''
* [[Media:NU32_stepper_example.c | NU32_stepper_example.c]]: Use the TB6612 to step the motor at 25 Hz steps (1 rev in 16s)

'''Controlling an RC servo motor'''
* [[Media:NU32_rcservo_pwm_example.c|NU32_rcservo_pwm_example.c]]: Use a PWM pin to set the position of the servo (note you only have 5 PWM pins)
* [[Media:NU32_rcservo_digio_example.c|NU32_rcservo_digio_example.c]]: Use any digital IO pin and a timer to set the position of the servo

== Extra PIC32 Code ==

'''USB'''
* HID to Processing on a PC
* CDC to PC

'''Watchdog Timer'''
* '''TESTED 2/7/2013''' [[Media:WatchdogTimer.c|WatchdogTimer.c]]: User button turns on LED the LED turns off again when PIC restarts due to watchdog timer
* Press a button every so often or watch the PIC reset itself (and perhaps a light stays off until you manually reset it or something)

'''Using the RTCC'''
* Keeping time: set time from a PC, display current time on same PC
* alarm clock demo?

'''Programming the onboard flash'''
* Flash self programming: displays saved data at power on, allows user to enter new data (button presses, whatever), displays the new data, and when you power cycle, PIC displays the most recent data on startup

'''Sleep, Idle, Freeze'''
* config bits?
* demonstrate little current usage in sleep mode; wake up at predefined intervals or on certain signals and do something (and see the spike in current usage?)

'''Using CAN'''
* Three PICs establishing a CAN bus: each PIC has a button and the state of the LEDs on each NU32 changes depending on which buttons are pressed (confirm communication between PICs)
* PC to PIC (Peak card?)
* some CAN chip? sensor?

'''DIP PIC32 with reconfigurable pins (1/2xx)''' (11/21)

* Reconfiguring the pins.

'''Data logging on a uSD card'''
* Using the Microchip FAT32 library, AN1045

File:ComparatorOutput.c

2013-02-07T21:53:58Z

AlexAnsari:

File:Comparator.c

2013-02-07T21:53:06Z

AlexAnsari: uploaded a new version of "File:Comparator.c"

File:Comparator.c

2013-02-07T21:43:42Z

AlexAnsari:

ME333 Unofficial Sample Code

2013-02-07T21:41:48Z

AlexAnsari: /* Extra PIC32 Code */

'''DO NOT USE SAMPLE CODE ON THIS PAGE! IT IS STILL IN TESTING MODE. USE [[ME333_Sample_Code|THIS PAGE]] INSTEAD.'''

Code for ME333 instructors to test before it goes live.

Code with '''TESTED''' has been tested and is ready to go live.

Code with '''EDITS''' has been updated but not fully test.

Code without any marking has not been looked at yet.

== PIC32 Code ==

'''Bootloader Project'''
* '''1/30/2013''' [[Media:NU32_bootloader.zip|NU32_bootloader.zip]]: (Updated 1/30 to make it jump to the noncacheable virtual address, not cacheable, just for conceptual clarity.) All files in one folder. Kevin's version building on Nick's. Jumps to application at new jump location that doesn't waste flash. Also sets config bits for Shadow Register Set.
* '''1/20/2013''' [[Media:NU32_old_bootloader.zip|Nick's bootloader app as of Jan 20, that doesn't compile]]

'''Simple PIC'''
* '''TESTED 1/16/2013''' [[Media:simplePIC.c|simplePIC.c]]: Flashes LEDs on the NU32 unless the USER button is pressed.
* '''TESTED 1/16/2013''' [[Media:simplePIC_standalone.c|simplePIC_standalone.c]]: Standalone version of simplePIC.c.

'''NU32 library, header file, procdefs, and terminal comm test'''
* '''1/17/2013''' [[Media:talkingPIC.c|talkingPIC.c]]: echoes strings sent from keyboard back to computer screen
* '''1/21/2013''' [[Media:NU32bootloaded.ld|NU32bootloaded.ld]]: Use this linker script when creating executables to be bootloaded on NU32 (not app.ld). Kevin's version which puts the program starting at 0x9D000000, allowing access to full amount of flash.
* '''1/20/2013''' [[Media:NU32.c|NU32.c]]: NU32 board library.
* '''1/28/2013''' [[Media:NU32.h|NU32.h]]: NU32 header file, updated to have config bits for Shadow Register Set and to include <plib.h>.
* [[Media:NU32_serial_comm.c|NU32_serial_comm.c]]: Serial communication test with the terminal.
* [[Media:NU32_serial_plot.c|NU32_serial_plot.c]]: Plot data with serial communication in NU32_Utility.

'''LCD code (to be moved into NU32.c)'''
* [[Media:LCD.c|LCD.c]]: LCD library.
* [[Media:LCD.h|LCD.h]]: LCD header file.
* [[Media:LCDtest.c|LCDtest.c]]: Test program for LCD library.

'''Serial Sample code for Invest.c'''
* [[Media:NU32_serial_for_invest.c|NU32_serial_for_invest.c]]: An example of serial communication, useful for converting invest.c to the PIC32.

'''Communication Examples'''
* Serial to a terminal
* Serial to MATLAB
* Serial to Processing
* Output to the LCD

'''Digital I/O'''
* [[Media:DIGIO_sfrs.c|DIGIO_sfrs.c]]: Digital I/O and change notification using SFR manipulation.
* [[Media:DIGI0_plib.c|DIGIO_plib.c]]: Digital I/O and change notification using the peripheral library.

'''Counter/timer'''
* [[Media:TMR_16bit.c|TMR_16bit.c]]: Set up a 16-bit timer to count the PBCLK.
* [[Media:TMR_16bit_external_clocks.c|TMR_16bit_external_clocks.c]]: Count two external clock sources, such as the A and B channel from a motor encoder.

'''Interrupts'''
* [[Media:INT_core_timer.c|INT_core_timer.c]]: Interrupt on core timer period match.
* [[Media:INT_ext_int.c|INT_ext_int.c]]: Interrupt on rising edge of external interrupt line INT0.
* Peripheral timer interrupt.

'''Output compare (PWM)'''
* [[Media:OC_PWM_nolib.c|OC_PWM_nolib.c]]: Set up PWM by setting SFRs.
* [[Media:OC_PWM_lib.c|OC_PWM_lib.c]]: Set up PWM using peripheral library functions.
* [[Media:OC_square_wave.c|OC_square_wave.c]]: Alternate between two different PWM duty cycles at 1 Hz. PWM is at 100 kHz and can be low-pass filtered to get a square wave analog output.

'''Analog to digital'''
* [[Media:ADC_Read2.c|ADC_Read2.c]]: Reads two analog inputs repetitively and prints the results to the user's terminal.
* [[Media:ADC_Read2_LCD.c|ADC_Read2_LCD.c]] Reads two analog inputs repetitively and prints the results to the LCD.
* Something else, scanning mode, asynchronous results check on the buffer, and/or interrupt generated when some results are ready.

'''Using the UART'''
* Simple RS232 communication: one UART to another on the same PIC
* [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* Talking to a PC with an FTDI cable

'''Using I2C'''
* I2C1 to I2C2 on one PIC
* PIC to PIC
* MAX518 8bit I2C DAC
* NAU7802 24bit I2C ADC
* PCF8570 2kbit I2C SRAM

'''Using SPI'''
* '''TESTED 2/7/2013''' [[Media:SPILoopback.c|SPILoopback.c]]: SPI4 to SPI1 on one PIC
* PIC to PIC
* MCP4922 12bit SPI DAC
* MCP3008 10bit SPI ADC
* Microchip 23k256 256kbit SPI SRAM

'''Comparator'''
* turn a light on or off based on potentiometer reading
* 16-value analog output?

'''Input Capture'''
* create a PWM signal (duty cycle controlled by a potentiometer) and read in to an input capture, display the pulse width or duty cycle

== Applications ==

'''DSP and FFT'''
* [[Media:DSP_sample_square_wave.zip|DSP_sample_square_wave.zip]]: Examples of FIR and FFT in both MATLAB and on the PIC32.
* [[Media:DSP_mips32_fft.zip|DSP_mips32_fft.zip]]: Example of using the Q31 mips library for FFT. Contains a C source file and a header file.

'''Reading a quadrature encoder with the dsPIC33FJ12MC201 breakout board'''
* [[Media:NU32_dsPIC_QEI_example.c | NU32_dsPIC_QEI_example.c]]: Read the encoder count at 250Hz, send to the computer at 5Hz

'''Controlling a stepper motor with the TB6612'''
* [[Media:NU32_stepper_example.c | NU32_stepper_example.c]]: Use the TB6612 to step the motor at 25 Hz steps (1 rev in 16s)

'''Controlling an RC servo motor'''
* [[Media:NU32_rcservo_pwm_example.c|NU32_rcservo_pwm_example.c]]: Use a PWM pin to set the position of the servo (note you only have 5 PWM pins)
* [[Media:NU32_rcservo_digio_example.c|NU32_rcservo_digio_example.c]]: Use any digital IO pin and a timer to set the position of the servo

== Extra PIC32 Code ==

'''USB'''
* HID to Processing on a PC
* CDC to PC

'''Watchdog Timer'''
* '''TESTED 2/7/2013''' [[Media:WatchdogTimer.c|WatchdogTimer.c]]: User button turns on LED the LED turns off again when PIC restarts due to watchdog timer
* Press a button every so often or watch the PIC reset itself (and perhaps a light stays off until you manually reset it or something)

'''Using the RTCC'''
* Keeping time: set time from a PC, display current time on same PC
* alarm clock demo?

'''Programming the onboard flash'''
* Flash self programming: displays saved data at power on, allows user to enter new data (button presses, whatever), displays the new data, and when you power cycle, PIC displays the most recent data on startup

'''Sleep, Idle, Freeze'''
* config bits?
* demonstrate little current usage in sleep mode; wake up at predefined intervals or on certain signals and do something (and see the spike in current usage?)

'''Using CAN'''
* Three PICs establishing a CAN bus: each PIC has a button and the state of the LEDs on each NU32 changes depending on which buttons are pressed (confirm communication between PICs)
* PC to PIC (Peak card?)
* some CAN chip? sensor?

'''DIP PIC32 with reconfigurable pins (1/2xx)''' (11/21)

* Reconfiguring the pins.

'''Data logging on a uSD card'''
* Using the Microchip FAT32 library, AN1045

File:WatchdogTimer.c

2013-02-07T21:36:15Z

AlexAnsari:

ME333 Unofficial Sample Code

2013-02-07T21:34:14Z

AlexAnsari: /* PIC32 Code */

'''DO NOT USE SAMPLE CODE ON THIS PAGE! IT IS STILL IN TESTING MODE. USE [[ME333_Sample_Code|THIS PAGE]] INSTEAD.'''

Code for ME333 instructors to test before it goes live.

Code with '''TESTED''' has been tested and is ready to go live.

Code with '''EDITS''' has been updated but not fully test.

Code without any marking has not been looked at yet.

== PIC32 Code ==

'''Bootloader Project'''
* '''1/30/2013''' [[Media:NU32_bootloader.zip|NU32_bootloader.zip]]: (Updated 1/30 to make it jump to the noncacheable virtual address, not cacheable, just for conceptual clarity.) All files in one folder. Kevin's version building on Nick's. Jumps to application at new jump location that doesn't waste flash. Also sets config bits for Shadow Register Set.
* '''1/20/2013''' [[Media:NU32_old_bootloader.zip|Nick's bootloader app as of Jan 20, that doesn't compile]]

'''Simple PIC'''
* '''TESTED 1/16/2013''' [[Media:simplePIC.c|simplePIC.c]]: Flashes LEDs on the NU32 unless the USER button is pressed.
* '''TESTED 1/16/2013''' [[Media:simplePIC_standalone.c|simplePIC_standalone.c]]: Standalone version of simplePIC.c.

'''NU32 library, header file, procdefs, and terminal comm test'''
* '''1/17/2013''' [[Media:talkingPIC.c|talkingPIC.c]]: echoes strings sent from keyboard back to computer screen
* '''1/21/2013''' [[Media:NU32bootloaded.ld|NU32bootloaded.ld]]: Use this linker script when creating executables to be bootloaded on NU32 (not app.ld). Kevin's version which puts the program starting at 0x9D000000, allowing access to full amount of flash.
* '''1/20/2013''' [[Media:NU32.c|NU32.c]]: NU32 board library.
* '''1/28/2013''' [[Media:NU32.h|NU32.h]]: NU32 header file, updated to have config bits for Shadow Register Set and to include <plib.h>.
* [[Media:NU32_serial_comm.c|NU32_serial_comm.c]]: Serial communication test with the terminal.
* [[Media:NU32_serial_plot.c|NU32_serial_plot.c]]: Plot data with serial communication in NU32_Utility.

'''LCD code (to be moved into NU32.c)'''
* [[Media:LCD.c|LCD.c]]: LCD library.
* [[Media:LCD.h|LCD.h]]: LCD header file.
* [[Media:LCDtest.c|LCDtest.c]]: Test program for LCD library.

'''Serial Sample code for Invest.c'''
* [[Media:NU32_serial_for_invest.c|NU32_serial_for_invest.c]]: An example of serial communication, useful for converting invest.c to the PIC32.

'''Communication Examples'''
* Serial to a terminal
* Serial to MATLAB
* Serial to Processing
* Output to the LCD

'''Digital I/O'''
* [[Media:DIGIO_sfrs.c|DIGIO_sfrs.c]]: Digital I/O and change notification using SFR manipulation.
* [[Media:DIGI0_plib.c|DIGIO_plib.c]]: Digital I/O and change notification using the peripheral library.

'''Counter/timer'''
* [[Media:TMR_16bit.c|TMR_16bit.c]]: Set up a 16-bit timer to count the PBCLK.
* [[Media:TMR_16bit_external_clocks.c|TMR_16bit_external_clocks.c]]: Count two external clock sources, such as the A and B channel from a motor encoder.

'''Interrupts'''
* [[Media:INT_core_timer.c|INT_core_timer.c]]: Interrupt on core timer period match.
* [[Media:INT_ext_int.c|INT_ext_int.c]]: Interrupt on rising edge of external interrupt line INT0.
* Peripheral timer interrupt.

'''Output compare (PWM)'''
* [[Media:OC_PWM_nolib.c|OC_PWM_nolib.c]]: Set up PWM by setting SFRs.
* [[Media:OC_PWM_lib.c|OC_PWM_lib.c]]: Set up PWM using peripheral library functions.
* [[Media:OC_square_wave.c|OC_square_wave.c]]: Alternate between two different PWM duty cycles at 1 Hz. PWM is at 100 kHz and can be low-pass filtered to get a square wave analog output.

'''Analog to digital'''
* [[Media:ADC_Read2.c|ADC_Read2.c]]: Reads two analog inputs repetitively and prints the results to the user's terminal.
* [[Media:ADC_Read2_LCD.c|ADC_Read2_LCD.c]] Reads two analog inputs repetitively and prints the results to the LCD.
* Something else, scanning mode, asynchronous results check on the buffer, and/or interrupt generated when some results are ready.

'''Using the UART'''
* Simple RS232 communication: one UART to another on the same PIC
* [[Media:Uart_pic2pic.c|Uart_pic2pic.c]]: Simple RS232 communication: PIC to PIC
* [[Media:Uart_hfc.c|Uart_hfc.c]]: RS232 with hardware flow control
* Talking to a PC with an FTDI cable

'''Using I2C'''
* I2C1 to I2C2 on one PIC
* PIC to PIC
* MAX518 8bit I2C DAC
* NAU7802 24bit I2C ADC
* PCF8570 2kbit I2C SRAM

'''Using SPI'''
* '''TESTED 2/7/2013''' [[Media:SPILoopback.c|SPILoopback.c]]: SPI4 to SPI1 on one PIC
* PIC to PIC
* MCP4922 12bit SPI DAC
* MCP3008 10bit SPI ADC
* Microchip 23k256 256kbit SPI SRAM

'''Comparator'''
* turn a light on or off based on potentiometer reading
* 16-value analog output?

'''Input Capture'''
* create a PWM signal (duty cycle controlled by a potentiometer) and read in to an input capture, display the pulse width or duty cycle

== Applications ==

'''DSP and FFT'''
* [[Media:DSP_sample_square_wave.zip|DSP_sample_square_wave.zip]]: Examples of FIR and FFT in both MATLAB and on the PIC32.
* [[Media:DSP_mips32_fft.zip|DSP_mips32_fft.zip]]: Example of using the Q31 mips library for FFT. Contains a C source file and a header file.

'''Reading a quadrature encoder with the dsPIC33FJ12MC201 breakout board'''
* [[Media:NU32_dsPIC_QEI_example.c | NU32_dsPIC_QEI_example.c]]: Read the encoder count at 250Hz, send to the computer at 5Hz

'''Controlling a stepper motor with the TB6612'''
* [[Media:NU32_stepper_example.c | NU32_stepper_example.c]]: Use the TB6612 to step the motor at 25 Hz steps (1 rev in 16s)

'''Controlling an RC servo motor'''
* [[Media:NU32_rcservo_pwm_example.c|NU32_rcservo_pwm_example.c]]: Use a PWM pin to set the position of the servo (note you only have 5 PWM pins)
* [[Media:NU32_rcservo_digio_example.c|NU32_rcservo_digio_example.c]]: Use any digital IO pin and a timer to set the position of the servo

== Extra PIC32 Code ==

'''USB'''
* HID to Processing on a PC
* CDC to PC

'''Watchdog Timer'''
* Press a button every so often or watch the PIC reset itself (and perhaps a light stays off until you manually reset it or something)

'''Using the RTCC'''
* Keeping time: set time from a PC, display current time on same PC
* alarm clock demo?

'''Programming the onboard flash'''
* Flash self programming: displays saved data at power on, allows user to enter new data (button presses, whatever), displays the new data, and when you power cycle, PIC displays the most recent data on startup

'''Sleep, Idle, Freeze'''
* config bits?
* demonstrate little current usage in sleep mode; wake up at predefined intervals or on certain signals and do something (and see the spike in current usage?)

'''Using CAN'''
* Three PICs establishing a CAN bus: each PIC has a button and the state of the LEDs on each NU32 changes depending on which buttons are pressed (confirm communication between PICs)
* PC to PIC (Peak card?)
* some CAN chip? sensor?

'''DIP PIC32 with reconfigurable pins (1/2xx)''' (11/21)

* Reconfiguring the pins.

'''Data logging on a uSD card'''
* Using the Microchip FAT32 library, AN1045

File:SPILoopback.c

2013-02-07T21:29:46Z

AlexAnsari:

ME 333 Introduction to Mechatronics (Archive Winter 2013)

2013-01-27T20:18:06Z

AlexAnsari:

'''Winter Quarter 2013'''

'''First day of class is Tuesday Jan 8'''
* Section 20: Prof. Kevin Lynch, T Th, 11:00-12:20, Tech LR5
* Section 21: Prof. Nick Marchuk, T Th, 12:30-1:50, Tech LR5
* TAs: Alex Ansari, AlexanderAnsari2011 at u.northwestern.edu; Jian Shi, JianShi2011 at u.northwestern.edu
* C Peer Instruction Sessions:
* '''Final demo''' (in lieu of final exam): Monday March 18 3-5 PM (12:30-1:50 section) and Wed March 20 9-11 AM (11-12:20 section) in LR5
* Office Hours:
** Mon-Fri 3-5 PM: Prof. Marchuk, Mechatronics Lab, Ford B100
** Mon 11:30-1:30 PM: Alex Ansari, Willens Wing Atrium
** Tues 2-3 PM: Prof. Lynch, B290
** Wed 12-2 PM: Jian Shi, NxR Lab, B230
** Thurs 3-4 PM: Prof. Lynch, B290

== Purpose of this Course ==

The purpose of this course is to '''provide tools that help you express your creativity'''. Maybe you want to build a robot, or a piece of kinetic art, or an automatic ball-throwing device to entertain your dog; maybe you've identified a market for a new smart product and you'd like to prototype the device. This course provides fundamentals of mechatronics to give you confidence to take on these projects. You are encouraged to take what you learn in this course and apply it in the project-based ME 433 Advanced Mechatronics course, Design Competition, or independent projects.

== Approximate Syllabus ==

This course is for students that want to build microprocessor-controlled electromechanical devices.

To do this, ME 333 focuses on three topics: (1) general C programming; (2) Microchip PIC microcontroller architecture and C programming specific to the PIC (e.g., using the PIC's peripherals, such as analog inputs, digital I/O, counters/timers, comm ports, etc.); and (3) interfacing the PIC to sensors and actuators, some theory of sensor and actuator operation, and interface circuitry and signal processing.

'''You will do a lot of programming in this course!''' If you are certain you hate programming, then this is not the course for you. But knowing how to program is very useful for any modern engineer. The language we will use is C, a fairly low-level language that works well for microcontrollers, without being nearly as painful and low-level as assembly language. If you don't know C, that's not a problem, most students don't before taking ME 333; but you should plan to learn it, and rather quickly. You will have all the materials you need to start learning C before class starts, and '''the first assignment on C is due on the first day of class'''! The reason: even though we start out with C, that's not the main goal of this course. The main goal is to teach you about microcontrollers and mechatronics. Plus some students already have C background.

You will bring your laptop to each class. As the quarter progresses, we will be handing out other equipment that you will need to bring to class, such as the [[NU32: Introduction to the PIC32|NU32 development board]] that breaks out the [http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en545660 PIC32MX795F512L] microcontroller.

'''It is essential you do the assigned reading in advance of class.''' Classes will begin with you turning in a short problem set related to the reading. (This includes the very first day of class!) Once a week we will have a short quiz. Most classes will be a combination of a brief review, Q&A, and working individually or in small groups on problems while the instructors help answer any questions.

Topics we will cover include:

* introduction to C programming
* introduction to the PIC32 hardware, and programming the PIC32 in C
* digital I/O
* counters/timers and interrupts
* analog input
* sensor smorgasbord
* digital signal processing: filters and FFTs
* analog output and pulse-width modulation
* brushed permanent magnet DC motors: theory and control
* stepper motors and RC servo motors
* communication by SPI, I2C, and RS-232

== Checklist to Complete Before the First Day of Class ==

Attendance at the first day of class (Tuesday Jan 8) is mandatory. By the first day of class, you should:

* Complete the reading and assignment 1, which is '''due the first day of class!''' In fact, the first two weeks of assignments are already posted, so you are welcome to complete them all over the break and coast through the first two weeks of class. The first assignments are designed to get you up to speed on the C programming language, which we will use throughout the course.
* Have a laptop with at least 2 USB ports. Any operating system is fine. One port will be used to program and communicate with your PIC microcontroller, and the other will be used for your portable oscilloscope.
* Be prepared to buy your class kit, consisting of the portable NUscope oscilloscope, the NU32 PIC32 development board, and lots of other goodies. Price $125 if you are starting from scratch; $75 if you already have the NUscope.


 

== Student Contract ==

By signing up for this course, you agree to complete the checklist above before the course starts. You understand that learning from classmates is encouraged, up to the stage of conceptualizing solutions. You understand that copying assignment solutions and program code plagiarism is not tolerated. You will report instances of code plagiarism you are aware of. Code plagiarism includes, but is not limited to:

* Allowing another student to copy your code.
* Copying another student's code, in whole or in part.
* Transforming copied sections of code to try to disguise their origin.
* Borrowing code from others not in the course, e.g., code found on the internet, without attribution. Borrowing code found on the internet is acceptable if the source is clearly indicated in your code comments, and if you understand how the code works.

On our part (faculty and TAs), we commit to do our best to provide you a curriculum and set of experimental materials to get you up to speed on sophisticated mechatronics integration as quickly and efficiently as possible, while giving you a foundation in concepts needed to go further in future projects and courses.

== Prerequisite ==

ME 233 Electronics Design or similar (EECS 221, 225) is required. You will be expected to analyze circuits with resistors, capacitors, inductors, diodes, transistors, and op-amps. You can find refresher material and a sample quiz at [[ME_333_Circuits_Review_Material|this page]].

== Reading ==

Required:

* [[Media:CrashCourseinC.pdf|A Crash Course in C]]: A brief introduction to the C programming language. Sample code from this appendix can be found [[ME333 Sample Code|here]].
([[Media:EssentialC.pdf|Essential C]] is also a very nice intro to C)
* handouts associated with individual classes
* wiki info on [[Microchip PICs]]
* [[Media:PIC32MX5XX6XX7XX_Family_Data_Sheet.pdf|PIC32 Data Sheet]] (256 pages, 5 MB pdf)
* [http://www.microchip.com/TechDoc.aspx?type=ReferenceManuals PIC32 Family Reference Manual, by chapter], and an [[Media:61132B_PIC32ReferenceManual.pdf‎|earlier version]] that conveniently has all chapters in one document. Lots of useful and detailed information on the PIC32 architecture and how the peripherals work, including detailed description of their SFRs. Only certain parts of certain chapters will be assigned. These chapters include quite a lot of example code. '''Be warned though, Microchip was not very careful when writing the sample code; some of it contains syntax errors, or values in registers that are incorrect.''' Even with this being the case, this is still a very useful document.
* PIC32MX Peripheral Library (included as a .chm file under "Program Files\Microchip\MPLAB C32\doc" with your C32 compiler installation)

Useful, but not required:

* [http://www.amazon.com/Programming-32-bit-Microcontrollers-Exploring-Technology/dp/0750687096/ref=sr_1_1?ie=UTF8&s=books&qid=1294091438&sr=8-1-spell Programming 32-bit Microcontrollers in C: Exploring the PIC32] by Lucio Di Jasio. This is an easy to read and informative exploration of the PIC32.
* MPLAB C32 Libraries Guide and MPLAB C32 User Guide, included under "doc" of your C32 compiler installation
* Other C resources, such as [http://publications.gbdirect.co.uk/c_book/ online] as well as this [[Media:CBook.pdf|pdf version]] of "The C Book," and the classic [http://www.amazon.com/Programming-Language-2nd-Brian-Kernighan/dp/0131103628/ref=sr_1_1?s=books&ie=UTF8&qid=1294091625&sr=1-1 C Programming Language] reference book by Kernighan and Ritchie

== Grading ==

Grades will be approximately 40% quizzes and 60% assignments (including the final project). We will have short quizzes once a week at the beginning of class covering material on the previous assignment. Bring a sheet of paper you can turn in with your quiz answers. (Your lowest quiz score and homework score will be dropped.) We will have a final project and demo in lieu of a final exam.

All quizzes and assignments have equal weight, regardless of how many points they are graded out of. If one homework is graded out of 20 points, and the next out of 40, the formula for calculating your total grade for these two assignments would be 0.5*(score1/20) + 0.5*(score2/40).

== Homework Submission ==

All homework will be submitted on Blackboard. All homeworks should be submitted by 11 AM on the day it is due (i.e., before the first section of the day). Late homeworks will not be accepted.

Here are a few guidelines/tips associated with homework submissions:
* We expect the required files for each assignment to be compressed together in a zip file (no rar files).
* When asked to submit C code for a given programming assignment, we are only concerned with receiving the relevant source files, i.e., all *.c and *.h files. We do not want entire IDE/MPLAB X projects or executables/object files.
* When writing your responses, please follow any instructions on how to write your response. For example, if we ask for a snippet of code, please do not submit your entire C program with header files and a main routine. We typically are only expecting a few lines of code that solves the problem.
* When submitting written responses, we prefer PDF files, but will accept word documents (.doc, .docx), .txt, and .rtf files.
* It helps both us and you if you format your code nicely. Clean looking code is easier for us to grade and easier for you to debug. Text editors with IDEs such as Netbeans and MPLAB X have tools for auto-formatting code. For example, highlighting a region and hitting Alt+Shift+f (Linux and Windows) will format that region according to your local formatting preferences.
* When you compile your code, pay attention to any compiler warnings. They are there for a reason! You should be able to eventually get your code to produce no warnings. Often if a piece of code is not working, the warnings will give a clue as to why.


== Schedule ==

All tutorial C code from "A Crash Course in C," as well as sample PIC32 code, can be found at this page: [[ME333 Sample Code|'''Sample Code for ME 333''']]

'''Winter Break'''
: '''Reading due for first class''': pages 1-10 of [[Media:CrashCourseinC.pdf|A Crash Course in C]]
: '''Assignment 1 due''': problems 1-4, 6-8, 10-11, 14-15 of A Crash Course in C. Bring your laptop to class and demonstrate your HelloWorld.c program.

'''Class 1''' (T 1/8)
: '''Assignment 1 due''': Hand in paper versions of your solutions at the beginning of class. No blackboard today. Also, bring your laptop to class to demonstrate HelloWorld.c.
: '''Class Topic''': Course overview and C programming
: '''Reading for next class''': pages 10-15 of A Crash Course in C
: '''Assignment 2 out''': problems 16-20, 23

'''Class 2''' (Th 1/10)
: '''Assignment 2 due'''
: '''Class Topic''': C programming continued
: '''Reading for next class''': pages 19-34 of A Crash Course in C (most of this is reference; the real goal is to fully understand the program invest.c)
: '''Assignment 3 out''': problems 24-26, 28-30, 32

'''Class 3''' (T 1/15)
: '''Assignment 3 due'''
: '''Class Topic''': C programming continued
: '''Reading for next class''': make sure you fully understand invest.c
: '''Assignment 4 out''': problem 33

'''Class 4''' (Th 1/17)
: '''Assignment 4 due'''
: '''Class Topic''': C programming conclusion. Thanks to Elliot Hevel, C newbie, for this [[Media:GradeSorter.c|C code]] he wrote in class today to solve problem 34 of a Crash Course in C. (The code seems to work fine, but we haven't tested exhaustively! No claims that it is the best or most efficient way to solve the problem, but definitely a nice job in the short time period. We removed an extraneous & seen in class today.)
: '''Reading for next class''': make sure you fully understand invest.c and are ready for a quiz on related C topics
: '''Assignment 5 out''': Purchase your ME 333 equipment [https://it.mccormick.northwestern.edu/matlab/student_license/login.php here]. If you have problems contact your instructor. Also, download the following (we will use them in Class 5):
Download and install:
* the free [http://www.microchip.com/pagehandler/en-us/family/mplabx/#downloads Microchip XC32 compiler] and [http://www.microchip.com/pagehandler/en-us/family/mplabx/ Microchip MPLAB X IDE] for your operating system
* the [http://www.ftdichip.com/Drivers/VCP.htm FTDI virtual COM port (VCP) driver] for your operating system
* the [http://processing.org/download/ Processing language] for your operating system
* a terminal emulator program like [http://freeware.the-meiers.org/ CoolTerm]

Also, download the [[Media:PIC32MX5XX6XX7XX_Family_Data_Sheet.pdf|PIC32 Data Sheet]] and the [[Media:61132B_PIC32ReferenceManual.pdf‎|PIC32 Reference Manual]].

'''Class 5''' (T 1/22)
: '''Assignment 5 due'''
: '''Quiz 1''': [[Media:ME333-2013-q1.pdf|Solutions]] On C programming (data types, pointers) and syntax similar to invest.c. '''As with all quizzes, no notes, computers, calculators, etc. are allowed.'''
: '''Class Topic''': our first programs for the PIC32, following chapter 1 and the [[NU32:_Quickstart|quickstart]]
: '''Reading for next class''': [[Media:ME333-Ch1-Ch2.pdf|Chapters 1 and 2]] of the class notes
: '''Assignment 6 out''': problems 1-7 of Chapter 2

'''Class 6''' (Th 1/24)
: '''Assignment 6 due'''
: '''Class Topic''': PIC32 and NU32 hardware
: '''Reading for next class''': finish Chapter 2 of the notes
: '''Assignment 7 out''': problems 8-16 of Chapter 2

'''Class 7''' (T 1/29)
: '''Assignment 7 due'''
: '''Class Topic''': PIC32 software
: '''Reading for next class''': [[Media:ME333-Ch3.pdf|Chapter 3]] of the notes through Chapter 3.5
: '''Assignment 8 out''': problems 1-6 of Chapter 3

'''Class 8''' (Th 1/31)
: '''Assignment 8 due'''
: '''Quiz 2''': PIC32 and NU32 hardware
: '''Class Topic''': PIC32 software
: '''Reading for next class''': finish Chapter 3 of the notes
: '''Assignment 9 out''': problems 7-12 of Chapter 2

'''Final Demo''': Monday 3/18, 3-5 PM (12:30-1:50 section) and Wednesday 3/20, 9-11 AM (11:00-12:20 section).

== FAQ ==

Q: Do I need to know the C language to take this course?

A: No. But if you already know C, there is still plenty else in this course for you. If you already know C, know how to use microcontrollers for real-time control, and have a good understanding how common sensors and actuators work and how to interface to them, this course may not be for you. Consider taking ME 433 Advanced Mechatronics in the spring quarter.

Q: Is there an independent project?

A: There is no large independent project. There will be a two-week project at the end of the course, but there will be no machining. For a significant project, do a quarter-long project in ME 433 Advanced Mechatronics, offered in the spring quarter. ME 333 is good preparation for ME 433.

Q: What kind of laptop do I need?

A: You need a laptop with at least 2 USB ports. Any operating system is fine.