 | | Re: Debugging
|
|
(...) However, last night, I wrote a brute force (spin loop) msleep which works fine in the scheduler. I found that 800 iterations of an empty for loop with a 16 bit index comes pretty close to 1ms. Granted, I cheated a little, knowing that the (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) Oh, you're doing stuff inside the scheduler. Yeah, msleep doesn't work too well there :-) Yes, the pauses were only so I could see what was going on. Another thing you could do is print messages out the IR port; but I'm not sure how it would (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: SetClock defined
|
|
Mark Overmars already forwarded your SetClock definition to me, so it will be added to 1.3, although I'm considering naming it SetWatch() for consistiency with the nqc -watch option and the spirit.ocx call. Dave (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Debugging
|
|
(...) I don't think it does. Of course, the source would answer definitively, but I also know that until I remembered to put the refreshes in there, I didn't get useful output. (...) I did that too. In my case, the lower byte was the priority (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) That's the method I've used. Just be sure to put an lcd_refresh() after the cputw() call - I can't remember if cputw() does the lcd_refresh() or not. Another thing I've done is write out a number where the upper byte indicates a position in (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8300 Stack and SLEEP
|
|
Kekoa wrote: <<snipped original description of problem>> (...) <<snipped description of tests>> Once again, Kekoa goes the extra mile and proves what many of us are happy to be merely confident about. Someday, I'd like to be reincarnated as a grad (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | SetClock defined
|
|
I noticed that the byte code command to implement the SetClock(hrs,min) wasn't implemented in the nqc.h file. Here it is, rather simple really but I find it useful as a way for the RCX to communicate debugging info while running. Example, when a (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: FW: H8300 Stack and SLEEP
|
|
(...) To be more precise, it applies to sleep mode and software standby mode as long as you set port 5 bit 2 to high before activating either mode. It does not apply to hardware standby mode, since that does not save registers or end with an (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: H8300 Stack and SLEEP
|
|
(...) After talking with Ralph over the weekend, I suggested a test he might do to figure out if port 5 bit 2 really does what he suggested it might. I don't think he did this test, so I fired up my RCX and hacked it together. I verified that port 5 (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Debugging
|
|
Do you guys have an established mechanism for debugging? I'm thinking of writing certain numbers to the display using cputw(). The idea being that the number frozen forever on the display will be the (approximately) last place the code was ok before (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Program Wanted
|
|
Does anyone have a program for the Recycler robot? Please help! Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 15-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | FW: H8300 Stack and SLEEP
|
|
(...) Markus, (and anyone else listening) I think it applies to the RCX power_shutdown() function as described in Kekoa's reference. The key is that this function puts the external RAM into low-power mode. If you are not calling power_shutdown() or (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | H8300 Stack and SLEEP
|
|
Hi All, If this is old news, ignore it... I just figured out this weekend (thanks Kekoa) that the H8/300 stack pointer (r7) and the power-down function in the RCX have a close relationship. The stack pointer MUST be in the on-chip RAM area (0xFD80 (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | New pbFORTH release
|
|
This is an announcement of the latest version (102) of pbFORTH available at: (URL) This release of pbFORTH addresses some errors in the previous version including a fairly serious stack problem in TIMER_SET. Also POWER_OFF now works as advertised, (...) (26 years ago, 15-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | NQC known bug
|
|
Just wanted to inform everyone of a nastly little NQC bug in version 1.2: return statements in inline functions actually cause a top-level return from the enclosing subroutine / task. For example in the following code, sound 1 is never played: (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Battery voltage available within NQC?
|
|
(...) If you REALLY wanted to do this, you could use the bytecode to broadcast the battery information to the IR tower and have a service running on the PC which would recieve the battery message and then send an appropriate message back to the RCX. (...) (26 years ago, 12-Mar-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Battery voltage available within NQC?
|
|
(...) There's a bytecode (0x30) that instructs the RCX to send the battery voltage as a response over the IR. That's what NQC and Mindstorms use to read the battery voltage. I don't think this opcode has any effect within a program, or at best it (...) (26 years ago, 12-Mar-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Battery voltage available within NQC?
|
|
Last night I went out and bought six C cell nicads and wired them up as a power supply for my robot. What I'm wondering is this: is there some way to programmatically obtain the battery voltage, so I could make a decision based on a voltage (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Idle process
|
|
I guess my earlier posting got out after all. I got the message from the NNTP server telling me to register. That is why a slightly different version of my message appears later in the group. (...) I plan to keep the idle task, now that I understand (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) The idle task actually has the lowest priority in my scheme, but there was some efficiency gained in making the task list loop around. If the idle task is always there, it makes for simplified code in multitasking startup if you rely on that. (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
