Quote:
|
Originally Posted by Francis-134
I am almost sure that you can do what you want with easy C. However, I am having some trouble following what you want to do exactly and figuring out your problem. If you wish to drive your holomic robot, do not use both the RC driving blocks (i.e. two-motor or four-motor drive) and the motor module blocks. Simply use the motor blocks with the output being a variable. For example;
Retrieve a value from the joysticks from the
|
Thanks for the rapid reply!
Yes, this is exactly what I have in my program. I Put joystick values into variables for each axis, modify the variables, and then use the motor module blocks with the output being these modified variables fetched from GetRx Blocks. I use no RC driving blocks. The problem is, that the GetRx commands do not work when I have the motor block (non-Rc) with the variable outputs in the same loop. The Green activity light for Rx does not even come on on the controller. By using the print to screen block, I can see that the varables Fetched from GetRx are not changing at all as I move the joysticks. But, if I eliminate the motor module blocks, and re-download the program, all of a sudden the Rx activity light works, and the GetRx variables printed out to the screen change as they should. If i drop in just a single motor module block using one of these variable, then all Rx functionality goes away again.
It's like the motor module is a poison block when used in the same loop as GetRx that kills RC inputs. I suspect that this has to do with keeping the notions of autonomous and competition modes strictly enforced, so I hope that there is a way to circumvent this problem. I've tried using the code exaclty as above from the "It's a Vex Holonomic Drive!" thread, with the same problem.
I'm using Master Code 5, and the header on the EasyC i/o block is #include "UserAPI.h" while the holonomic code above has #include "main.h"
I wonder if that has anything to do with it?