View Single Post
  #2   Spotlight this post!  
Unread 23-08-2008, 03:56
Pat Fairbank's Avatar
Pat Fairbank Pat Fairbank is offline
Circuit Breaker
FRC #0254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2001
Location: San Jose, CA
Posts: 2,132
Pat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond reputePat Fairbank has a reputation beyond repute
Send a message via MSN to Pat Fairbank
Re: Serial communication between RC's

For receiving on the serial port to work you need to have ENABLE_SERIAL_PORT_ONE_RX defined and to call Init_Serial_Port_One() in the initialization, but I'm assuming from the content of your post that you've got that covered.

Are you confident in the integrity of your null modem cable? If you're receiving input on the computer terminal, that's fine, but that's presumably with a different plain serial cable. Try hooking up the slave to the computer and sending the '@' from the terminal.

Also, if I were trying to debug this problem I would put some temp code to flash the lights directly in the serial port rx interrupt handler in user_routines_fast.c, just to verify that the serial port is receiving independently of what's being sent.

Lastly, when you say "null modem cable", you do mean a male-male serial cable that has the TX and RX pins swapped along the length and not just a normal serial cable with a gender-bender, right? Just checking.
__________________
Patrick Fairbank
Team 254 | Mentor (2012-)
Team 1503 | Mentor (2007-2011)
Team 296 | Alumnus (2001-2004) | Mentor (2005-2006)

patfairbank.com