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 / *12226 (+20)
  Re: signals / legOS internals
 
(...) The stack pointer must always always always point at the bottom of the stack data area, i.e. to the last valid data item on the stack. As a consequence, push val (or mov.w val,@-r7) never overwrites data. When an interrupt occurs, the first (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) Reading this again, I should mention that pushing things on the stack asynchronously is fine, as long as the stack pointer is always in the right place, which is why it must always always always point to the location I mentioned (and seemingly (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) When you define a bunch of local variables (more than fit in available registers), where are they? Unless you happen to know the answer, I may have to do some more experimenting. Admittedly, it has been awhile, but the last time I was heavy (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) I may have down and up reversed, since different machines grow the stack upward or downward, and I've worked with a few. I do have push and pop clear in my mind, though. So, yeah, down. So, by the "always" rule, nothing will ever be below the (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: using nqc for first time
 
The traces confirm a couple of things: 1) Normally the IR tower will "echo" all data that it sends (just a side effect of the LED blasting out the light and the phototransistor picking it up). In your case there are a significant amount of bit (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  I love my Akro-Mils Portable Organizers (was Re: Rolykits)
 
Those Akro-Mils Parts Storage are !!The Best!! IMHO for Technics bits. I bought mine at Frye's in California. I have three, one of each size. The lid storage is great for little bits such as pegs, bushings and other tiny parts. The rounded bottoms (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) I may have answered my own question here. Since the SP is adjusted before anything is actually done with the local variables, the rule about it always pointing to the last valid datum is not violated even if local variables are placed after (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: I love my Akro-Mils Portable Organizers (was Re: Rolykits)
 
David, It sounds like u r a discriminating user. I have not yet tried any of the storage kits plugged on this mailing list, & so have no real opinion. Michael Aaron (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
 
  Re: signals / legOS internals
 
(...) Yes, that is correct. As for passing parameters to a function, they are simply pushed onto the stack before the function call. Therefore, the H8 stack usually looks something like e.g. this: function param sp+10 function param sp+8 return (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  Re: signals / legOS internals
 
(...) Since it sounds like it might matter to you, I should point out that the interrupt situation on the RCX is a bit more complicated than the H8 manual makes it out to be. Interrupt vectors are in ROM, but the ROM does a dispatch to interrupt (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
 
  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)

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

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