|
|
|
 I need a This-Is-What-I-Meant checker. - N7UJJ [more] |
 |
|
|||||||
|
||||||||
 |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| I need a This-Is-What-I-Meant checker. - N7UJJ [more] |
|
|
|||||||
|
||||||||
|
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
Reciever Initialization problem
Most of our codes work, so do the joysticks and other things, and we'd like to test our code. However, whenever we try to initialize Initialize_Receiver() from user_routines.c, we got a code error. Everything is OK when we commented that initialization out.
Does anyone know what is wrong or has ran into this same problem? Please help. |
|
#2
26-01-2004, 23:54
|
|||
|
|||
|
Re: Reciever Initialization problem
What exactly is the error? They aren't just there to look confusing they provide useful information (usually).
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Whacky C Complier behavior | Larry Barello | Programming | 12 | 26-01-2004 22:15 |
| digital inputs not valid just after initialization? | WizardOfAz | Programming | 2 | 26-01-2004 13:21 |
| Victor problem | Andy Baker | Electrical | 15 | 24-06-2003 09:49 |
| The problem with scouting... | archiver | 2001 | 10 | 23-06-2002 23:49 |
| Major problem with chipphua motors | aka Scott White | Motors | 18 | 19-03-2002 19:44 |
Hybrid Mode
