 | | serial interface building
|
|
A group of us are building the HB and we are at the serial interface building stage. When we perform the test on the serial interface to get +9 or +10 volts, we are all getting values of up to +8.5 only. Is there a problem or is this normal? Thanks (...) (27 years ago, 22-Jun-99, to lugnet.robotics.handyboard)
|
| |
 | | Re: IR questions
|
|
(...) Only transmitting keeps the tower alive, at least according to my tests. If absolutely necessary, an occasional 0xff sent by the PC will keep the tower alive; this will result in only a start bit being sent, which ought to occupy very little (...) (27 years ago, 22-Jun-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
 | | Re: Rolykits
|
|
I've been pretty happy with a storage container that I got from my local hardware store, manufactured by Arko-Mils, Inc: (URL) or more specifically ... (URL) I was using one of their "large portable organizers" (I paid about $17 US) to hold all of (...) (27 years ago, 22-Jun-99, to lugnet.robotics)
|
| |
 | | signals / legOS internals
|
|
Peek-a-boo! I've been banging my head against this a bit and thought I'd see if any of you can shove me in the right direction. I am trying to implement signals in legOS. The problem is that a signal can happen at any time. I know how to make that (...) (27 years ago, 23-Jun-99, to lugnet.robotics.rcx.legos)
|
| |
 | | Paris, Rome, & Rolykits : )
|
|
Chris, i recently ordered a Rolykit over the net. It was very expensive, but we will have to see how it works. It hasn't arrived just yet. I kind of wish now that i didn't order it because i suddenly decided to go on a trip to Paris & Rome in (...) (27 years ago, 23-Jun-99, to lugnet.robotics)
|
| |
 | | 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)
|