No Feedback via Programming Port

[manderson5192]

Hey guys,

I'm trying to use kevin's 3.0 code. I am using the proper version of MPLAB (8) and C18. The code compiles just fine. When I use ifi loader to download the code, though, I get zero feedback from my printf calls. They are in the right place btw. When I hit the reset button on the oi or rc I get a message like >ifi and an initialized... message. This was what one normally gets with no printf statements. I then tried a HEX file from 2007's season compiled with 2.4 and IFIs default code. This time I got plenty of feedback. My only question is how do I resolve this issue with kevin's code and the latest compiler (3.0)?

[JohnC]

Hmm, can you upload the file so the CD task force can take a look?

This is probably obvious but make sure the serial cable remains plugged in...

In the meantime, try copying and pasting the IFI warm-up printf call into Teleop() and commenting out all others.

Is it ONLY your printfs that don't work? That is, your robot still does the hokey pokey and everything, it just isn't showing serial feedback?

P.S. I'm in Tacoma! See you at PNW? Tacoma for sure though!

[Kevin Watson]

Hey guys,

I'm trying to use kevin's 3.0 code. I am using the proper version of MPLAB (8) and C18. The code compiles just fine. When I use ifi loader to download the code, though, I get zero feedback from my printf calls. They are in the right place btw. When I hit the reset button on the oi or rc I get a message like >ifi and an initialized... message. This was what one normally gets with no printf statements. I then tried a HEX file from 2007's season compiled with 2.4 and IFIs default code. This time I got plenty of feedback. My only question is how do I resolve this issue with kevin's code and the latest compiler (3.0)?If you're seeing the "IFI User Processor Initialized ..." message, everything should be functioning because it's generated by a printf() located at the bottom of the Initializtion() function. If you get stuck, send me your code and I'll have a look.

-Kevin

[manderson5192]

Thanks for the help guys. We resolved the problem by including \r and \n at the end of our printfs. I guess the compiler prefers that we not be lazy and only include \n.