|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#4
|
||||
|
||||
|
Sounds cool.
Quote:
I have a few questions though: What did you use to program this? I'm trying to understand the communications a bit more. I don't have very much experience in serial or COM communications at all. From what I understand, the PC puts together a data packet of all 4 joysticks. This is 8 bytes in length. I'm assuming it's 2 bytes per joystick, 1 byte per axis. When Its got a new packet ready, it sends out a signal to the RC. When the RC is ready to receive, it sends a signal back. The RC receives the packet, then sends out its 10 byte, 2 integer packet back. But I'm having trouble with the inner workings of this routine. I browsed through the pc_interface.c file included in the packet, and found the Wait4TXEmpty function call. I noticed that when I tried to compile the project, I couldn't, because the alias.h was referred to as IFI_aliases.h and the IFI_default.h (i think) was missing something. I'm guessing you updated the default code with that function. Anyway, I'm guessing that it means wait until the PC has pulled this value. So, when I load up my program (the one I wrote for the joysticks ) and it starts transmitting data, the RC gets stuck in an infinite loop. Now, my PC recognizes if the RC goes offline, so I know it's seeing it right. I just don't think I'm handling everything correctly. Could you give a C code example (even though I'm using Qbasic ...for now...) of how the data's put together and sent/received. Anyway, I have got the joystick input working aok. I've got one flight stick hooked up, and I can pull all the axis, wheel, and buttons from it. The program I have currently calibrates the joystick at startup, then filers the values every cycle, so they range from 0-254, and the axis are lined up correctly. So far so good. I just need an idea of what to do after that. After 1 PC cycle, the next packet is ready. So, I'm supposed to send a small byte to the RC, right? Or do I pull a value?That's where most of my confusion sets in. Oh, and another quick question: What's the setup of the COM connection? 9600baud, no parity, 7 databits, 1 stopbit ? That also may be where I'm off. Anyway, thank's for the help. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| How much planning goes into your robot? | Jnadke | General Forum | 41 | 29-01-2006 21:29 |
| White Paper Discuss: Using an Operator Interface with the 2004 EDU RC | CD47-Bot | Extra Discussion | 6 | 20-01-2004 21:11 |
| Some code in C that we may need if we are in trouble | Andrew Rudolph | Chit-Chat | 16 | 07-10-2003 21:34 |
| serious problem found - robot controller resets when jarred! | KenWittlief | Electrical | 23 | 19-03-2003 13:30 |
| Controlling a FIRST robot with a Lego RCX Controller? | archiver | 2001 | 5 | 24-06-2002 04:19 |