To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / *12236 (+20)
  speed control help
 
I have a problem that involves speed control. My robot is curently configured for differential steering and have shaft encoders installed on each one for feedback. the shaft encoders generate 64 pulses /rev The motors are PWM using the rug warrior (...) (27 years ago, 23-Jun-99, to lugnet.robotics.handyboard)
 
  Paris, Rome, & Rolykits : )
 
In article <37705837.D413A8C6@uswest.net>, Michael Aaron Finch <goblintrain@uswest.net> writes (...) They're a bit far south to see the eclipse, and it would be apity to be so close and miss it. Go to Metz (France), and see both the hot air ball0on (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  RE: signals / legOS internals
 
(...) Not to put too fine a point on it, and I hope Kekoa agrees, but the "fluff" is the reason why replacement firmware works in the first place. Without the ROM vectors being dispatched through RAM pointers that are initialized by the ROM and then (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Lego Reflectivity in the IR Band
 
-In case you were curious about which colors of Lego reflect infrared the best, I did a little experiment. Visit my Lego page at: (URL) -JW Jonathan Woodward woodward@guesswork.com (URL) don't know which is more depraved: The audacity and greed (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) Actually, gcc moves the stack pointer before using any variables, so it is always safe to use stack below the current stack pointer. If you are using a different C compiler or doing assembly tricks, then you are on your own. (...) Traditional (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: speed control help
 
lroska wrote: <snip> (...) <snip> (...) <snip> (...) <snip> The easy solution is to avoid using a formula that assumes anything about the motor speed curve (except of course that reducing the motor value reduces the speed). Try using a feedback (...) (27 years ago, 23-Jun-99, to lugnet.robotics.handyboard)
 
  Re: speed control help
 
It sounds like you are running open loop. If you use the wheel encoders as feedback devices to close the loop, then you can use the motor control function in your program as a variable to adjust motor control current via PWM to match the command (...) (27 years ago, 23-Jun-99, to lugnet.robotics.handyboard)
 
  New Challenge
 
Hello all.... I've been watching this group for a long time and while the discussions about RCX programming and LegOS is fine and good, what about some good old fashioned building challenges? Something that's challenging, yet actually can be (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) Why signals?!? Unix-style asynchronous signals is the last feature I would ever want to implement or use. Brain-dead and very dangerous "feature". As you write; "The problem is that a signal can happen at any time". You shouldn't pass this (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) An asynchronous signal models a hardware interrupt. There are times when that is the appropriate interface. There are times when other interfaces are less error prone and are easier to write correctly. Frequently using only synchronous (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: Robotic arm on Mindstorms box
 
I found a gripper system in a catalog called "Robot Store". Or go to www.RobotStore.com (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: New Challenge
 
Stock Mindstorms kit only? Or do we get additions? -Luis (...) ###...### Profanity is the one language that all programmers understand. -Anonymous ###...### -- Did you check the web site first?: (URL) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) But hardware interrupts schedule a different context (the interrupt process or ISR) from the one already executing. A Unix-style signal asynchronously signal interrupts the executing process and jumps to a different location in the code that (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) An ISR can certainly modify data that is used by the executing code. For example, if it doesn't save registers that are used the interrupted code will certainly be affected. In fact, the ISR is of little use if it doesn't modify data that can (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  RE: New Challenge
 
If no further details are provided, than this is a trivial challenge. No robot needed either. Take a dumbbell with disk weights, put it on a smooth, hard surface so that it can roll easily. Connect a winch to a Lego motor. Mount it on a base plate, (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) In OSE interrupt processes (first class processes, that is why we don't call them ISR's) use OS mechanisms (usually messages) to communicate with normal processes. The OS handles all update of shared data structures (such as message queues). A (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) This is the same thing as most modern RTOS use, called various things. The terminology I use for this is FLIH/SLIH (first level interrupt handler and second level interrupt handler). Coupled with lock priority inheritance, it makes for a very (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  RE: New Challenge
 
(...) Good idea Todd, but there is a hitch. What surface is the dumbell on? Can the bot pick up the dumbell? Can the dumbell be in a cart? etc.... Cheers, Ralph Hempel - P.Eng ---...--- Outside of a dog, a book is a man's best friend. Indside of a (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) This second methed doesn't really solve anything since you still have to communicate with the compute thread from the receive thread. (...) But what can you actually do in the signal handler? Modify the state of the state of the executing (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) Because they are useful at times, and Markus directed me to implement them. I think the upcoming network code is going to use them, too (at least, that's what I heard). Just 'cause they're there doesn't mean you have to use them. (...) How do (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)

Next Page:  5 more | 10 more | 20 more
Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR