Here I am again

Let's go straight to some code posting and then explain the problem, I'll go thru this loop twice with two different code versions and, of course, two different problems

(I spared a conversion code to keep things short, the CommandL/R will only give 1-6 as useful commands)



This way, I get the motors to move fine, but I also get about 1sec delay between interacting with the joypad and the actual motor action, it's weird it takes so much time to do the stuff so I thought about tasks and tried this other wersion...



Now the motor move perfectly, but I didn't use plural form as it does execute only the first command, moving the motor on port 0 and not the motor on port 1

I tried using 2 tasks for the 2 motors but it seems stupid as the number of tasks is limited, and even then, RobotC complained about using the function PFcomboPwmMode twice in parallel on two different tasks and the same time

There must be some solution and I feel like I'm close to it, yet so far away that I'm forced to ask here for help

Thank you all if you feel like trying to give me something to work on!

Looks to me like you don't really need a motors "task", but just a function. Try defining:

task Motore()

as

void Motore()

and calling it directly using

Motore();

cu,
Gary

Thank you Gary but using a function makes the motors answer with almost 1sec delay just like the first example having the commands inside the main task

Another thing to try is to add a wait1Msec(10) or similar in your loop, so that will free up the CPU to do other work.

cu,
Gary

To add a Pause in order to fix a Delay, that's wicked!
Now I'm at office but I'll try this one as soon as I reach home, can't wait to fix that in order to code other features

Thank you!

I still have to try the ms pause hint, need some spare time, hopefully I'll do it this evening

Any word from Xander about the issue, by the way?

What issue? I thought the problem was resolved by changing the tasks to a function?

- Xander

Nope, function still gives a 1 sec delay
I'm gonna try to wait 10 ms this evening

But why does the task move only one motor? why does it ignore the second command?

Just attach your current program (don't paste it). I'll take a look. I can't test anything as I am on vacation and don't have my NXTs with me.

- Xander

Man I'd bring my NXT on vacation... it sucks I can't take it at the office
Will send you the code later when I get home, after I test the last hints I received

Thank you, hope the best for you on your vacation

Alright, this is the version I'm trying right now, all problems remain even with the pauses



If I place the 2 PFcomboPwmMode inside the main while loop, I get 1sec delay between the joypad interaction and the actual motor reaction

If I use the Motore task technique I get a super fast motor response but it only execute the first PFcomboPwmMode, moving one track only

Using delay doesn't help, I tried from 10 to 200ms delay

What am I doing wrong?

You shouldn't use tasks like that. Just turn it into a normal function.

- Xander

Using a function still gives me the delay problem
I interact with the joypad and I can see display update and motor motion after like 1 second, it's unusable like that

Why do I get a delay when controlling two motors and I get none using a task? And why do the task run only 1 PFcomboPwmMode instead of 2?
I can't understand

I can't really look at this code until the end of next week as I am on vacation.

- Xander

Jampoz, it looks to me that you need to do both - not use a task (this isn't the right way to use it, just use a function or put the two lines of code back into the main loop), and you need the wait in the loop. Without both of these changes, I don't think you can make further progress. After these two changes, if there are still problems, please post your code and describe the behavior.

cu,
Gary