 | | Re: HOWTO Demo.c
|
|
Can you tell which line it's locking up on? Try commenting out lines until it doesn't lock up (or until you run out of lines) ----- Original Message ----- From: "Shehryar Shaheen" <shehryar.shaheen@ul.ie> Date: Tue, 9 Jul 2002 15:42:56 GMT To: (...) (23 years ago, 9-Jul-02, to lugnet.robotics.rcx.legos)
|
|
 | | Re: Navigation using landmarks (Was: Re: lasers and RCX)
|
|
I was hoping, since the thread was already onto how to modify and mount the mouse guts, that it would have been preceeded by a successful attempt to interface the little beast. Since I already know quite a lot about how tedious it is to get data (...) (23 years ago, 9-Jul-02, to lugnet.robotics)
|
|
 | | Re: HOWTO Demo.c
|
|
That is correct each Task started has a higher priority and they all have a higher prority than task_swapper like Prio Task 1 -- Task Swapper 2 -- Motor Driver Task 3 -- Light Sensor Task 4 -- Touch Sensor I changed the all the priorities to 1 but I (...) (23 years ago, 9-Jul-02, to lugnet.robotics.rcx.legos)
|
|
 | | RE: Navigation using landmarks (Was: Re: lasers and RCX)
|
|
(...) Nothing yet. I have a guy in England that's trying to use pbForth to do I2C comms. As I see it, there are two possiblilities here. One is a bit-bang interface on a sensor input port. Tricky to do with pbForth because it allows the normal 1 (...) (23 years ago, 9-Jul-02, to lugnet.robotics)
|
|
 | | Re: Navigation using landmarks (Was: Re: lasers and RCX)
|
|
I see all this nice stuff about trimming mouse bottoms and mounting the device off of the central steering axis and stuff to try and catch rotation, but I haven't spotted the posting about how people are actually getting the x and y values from the (...) (23 years ago, 9-Jul-02, to lugnet.robotics)
|
|
 | | RE: Navigation using landmarks (Was: Re: lasers and RCX)
|
|
A Killough platform may have 3 motors, but it operates in a X-Y coordinate plane, not X-Y-Z. The camera is looking for pattern shifts horizontally or vertically, not radially within it's field of vision. As long as the axis of the spin is not (...) (23 years ago, 9-Jul-02, to lugnet.robotics)
|
|
 | | Re: HOWTO Demo.c
|
|
If I understand this correctly (which I doubt) each task you start, has a higher priority, and they all have a higher priority than the 'task_swapper' task. Try setting all the priorities the same. Like to 1. See what that does. (...) (23 years ago, 9-Jul-02, to lugnet.robotics.rcx.legos)
|
|
 | | Re: HOWTO Demo.c
|
|
The code I have taken out of HOWTO.ps (URL) given at the end of the document under the name Demo.c I have fixed some compile time errors (like mismatching process ids in the kill call, the function for getting button state is dbutton() and not (...) (23 years ago, 9-Jul-02, to lugnet.robotics.rcx.legos)
|
|
 | | Re: HOWTO Demo.c
|
|
I'm no expert, but I can try to help you figure it out. Let's start with something simple. What version of LegOS are you using? How are you starting the 'task_swapper' task? What is in the 'motor_driver' task? At one time, when I was working with (...) (23 years ago, 9-Jul-02, to lugnet.robotics.rcx.legos)
|
|
 | | HOWTO Demo.c
|
|
Need Help, if someone has faced such a problem or knows the fix please do reply. In the legOS Howto their is a demo code demo.c which has some task switching examples I am having trouble with the following piece of code int task_swapper() { (...) (23 years ago, 9-Jul-02, to lugnet.robotics.rcx.legos)
|