 | | NXTAssembler 1.0 Alpha 2
|
|
Hi, First I want thanks John Hansen ,for the replies and for the NBC project. I released the alpha 2 of NXTAssembler 1.0, it's the first version that has something working! :-D (It's an alpha software and it contains a lot of bugs :-( ) Examples of (...) (17 years ago, 28-Jul-07, to lugnet.robotics.nxt)
|
| |
| | RE: RotateMotor is stuck/nxc
|
|
John, The new nbc b31 works! Thank you! Now I'm onto making the biped walking more fluidly... --E -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...ugnet.com] On Behalf Of John Hansen Sent: Friday, July 27, 2007 1:30 (...) (17 years ago, 27-Jul-07, to lugnet.robotics.nxt)
|
| |
| | Re: RotateMotor is stuck/nxc
|
|
(...) Elizabeth, Could you upgrade to b31 of NXC and see if you still have this problem? You will need to update your TextOut call to put the "false" as the last parameter or leave it out altogether. TextOut(0, LCD_LINE2, "DONE ROTATE"); Also, could (...) (17 years ago, 27-Jul-07, to lugnet.robotics.nxt)
|
| |
| | RE: RotateMotor is stuck/nxc
|
|
Just to clarify more although it probably is very clear to most... LEGS_TURNING_DEG = some int to indicate the turning degree MOVENOW & DONE contains different integer values --E -----Original Message----- From: news-gateway@lugnet.com (...) (17 years ago, 27-Jul-07, to lugnet.robotics.nxt)
|
| |
| | RotateMotor is stuck/nxc
|
|
Symptom: Stuck in RotateMotor function call. ===...=== Synopsis of how to create the problem : - 2 tasks - Task1 handles motor A & C - Task2 handles motor B - Task1’s motor movements have to synchronize with the Task2’s motor B movement - Mutex is (...) (17 years ago, 27-Jul-07, to lugnet.robotics.nxt)
|
| |
| | Re: stop task
|
|
(...) It hasn't, Elizabeth - I'm not upset at John, and he knows *far* more about programming than I do. I just wanted to point out that there are process where abruptly "killing" a thread was one of the best solutions I ever found, due to the speed (...) (17 years ago, 25-Jul-07, to lugnet.robotics.nxt)
|
| |
| | RE: stop task
|
|
Everyone, Being fair in the judgement in using a global watchdog flag to terminate a task. Honestly, when I have a multi-threaded process, I have always used a watchdog type of flag, mutex, semaphore, etc. to signal a thread to terminate. I hardly (...) (17 years ago, 25-Jul-07, to lugnet.robotics.nxt)
|
| |
| | Re: stop task
|
|
(...) Well, you may not consider that awkward, but having been able to use the "stop" & "start" task commands in NQC, I do actually consider it very awkward. For instance, if I want to immediately stop some task under the "stock" FW... well, I (...) (17 years ago, 24-Jul-07, to lugnet.robotics.nxt)
|
| |
| | Re: stop task
|
|
(...) It is not a rather awkward option, imho. That's like saying breaking out of an infinite loop using a flag is awkward and that it would be better to have some form of stop loop keyword that you could use from outside the loop instead. Is it (...) (17 years ago, 24-Jul-07, to lugnet.robotics.nxt)
|
| |
| | Re: stop task
|
|
(...) Using a global to flag out of a task is about the only (rather awkward) option I know of. This is one of the things that I really have issues with under the NXT-G FW. (17 years ago, 24-Jul-07, to lugnet.robotics.nxt)
|
