Created Sat, 06 Apr 2013 03:18:02 +0000 by ryban1
Sat, 06 Apr 2013 03:18:02 +0000
I have a chipKit Max32 and have recently bought a RF transmitter and receiver from Sparkfun (https://www.sparkfun.com/products/10534). I want the transmitter to send a message to the receiver. I went through the KPL tutorial on their website (https://www.sparkfun.com/datasheets/RF/KLP_Walkthrough.pdf). I ran the code for given in the tutorial on mpide and the receiver code never uploads. My next plan is to try the virtualwire code, but I am not sure how to add it on mpide. Any help would be appreciated.
Sat, 06 Apr 2013 16:05:19 +0000
Which chipKIT board are you using?
Which serial port on the chipKIT board are you using?
Which pins are you using for that serial port?
What baud rate are you trying to talk with?
What is the part number of the device you are using?
The correct serial port and pins to use will depend on the board you are using and may not match exactly the Arduino example.
[edit] it looks like the RF-KLPA will work best with the chipKIT boards based on the supply voltages of the board.
Jacob
Mon, 08 Apr 2013 21:41:45 +0000
Which chipKIT board are you using?
I am using chipKit Max32 and Arduino Uno
Which serial port on the chipKIT board are you using?
For chipKit com4 Arduino com5
Which pins are you using for that serial port?
For chipKit Max32 I am using digital pin 0(Rx) & 1(Tx)
For Arduino I am using digital pin 0(Rx) & 1(Tx)
What baud rate are you trying to talk with?
In the KPL tutorial they use a 2400 baud rate in their example code
What is the part number of the device you are using?
chipKit Max32 - http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,892,894&Prod=CHIPKIT-MAX32
Arduino uno - http://arduino.cc/en/Main/arduinoBoardUno
Tue, 09 Apr 2013 02:39:11 +0000
Pin 0 and 1 of the Max32 go to the FTDI that goes to the PC. The FTDI holds the Rx link high and may prevent the reception of data from your device.
I think its the same on an Arduino so I'm confused if it works on an Arduino and not a Max32.
The Max32 has additional serial ports that you can address by using Serial1.print, ect.
Could this be your issue?
Jacob