 | | Re: Scout poweroff time out?
|
|
(...) The SetSleepTime() and SleepNow() thing was just sloppiness on my part when reorganizing the NQC API file. Those opcodes are clearly documented in the Scout SDK. I don't think we have to hunt around for undocumented features - just verify that (...) (26 years ago, 3-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) What other features will work? The BatteryLevel() one? I think we need to have a look at the rcx2 commands and see what's working for the Scout. Also, what does the Scout API include with the program? I know in the RCX it turns all motor ports (...) (26 years ago, 2-Oct-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) Possible, yes, but I'd prefer not to. The command line is already too complex. I might consider adding the information as part of the regular program download message (with the battery level). For devices other than Scout, there isn't a fixed (...) (26 years ago, 30-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) You know, I tried that. It didn't work. But then I'm using my new editor (that I'm working on) and had forgotten to set the brick type with EACH command to NQC. I only had it set to compile/Download. So the scout wouldn't be 'unlocked' until I (...) (26 years ago, 30-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) I just verified that both of these work. I'll fix the API for the next NQC release, but in the meantime, you can always add the following functions to your Scout programs: void SetSleepTime(const int t) { asm { 0xb1, t }; } void SleepNow() { (...) (26 years ago, 30-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?- Update
|
|
(...) After a *FEW* hours playing with this thing I've found out the following... It's built in shutdown is set for 15 minutes. Sending an IR code seems to reset this counter. So far I cannot find any way to keep it alive on it's own. If anyone (...) (26 years ago, 30-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout poweroff time out?
|
|
(...) Looking at the Scout SDK, I think it does support the same sleep time command as the RCX - although perhaps not from within a program. There are two things to try: nqc -sleep 0 or add the following function to your program and call it (with (...) (26 years ago, 30-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Scout poweroff time out?
|
|
I've just finished a very cool Camera mount that can be controlled via the web. (Linux, NQC & PHP) I've decided to use my scout because it's so limited. I've noticed one point and can't seem to see away way around this. I'm hoping someone can help. (...) (26 years ago, 29-Sep-00, to lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: Scout vs. RCX for Macintosh user
|
|
(...) I will add to Dave's great post above. I own 2 RCX 1.0's, a Scout & a Micro-Scout. The main reason for getting an RCX is that it's upgradeable. The Scout has it's firmware on a ROM and is NOT upgradeable. So it will one day just be a slave to (...) (26 years ago, 8-Sep-00, to lugnet.robotics.scout)
|
| |
| | Re: Scout vs. RCX for Macintosh user
|
|
Assuming it doesn't all wind up in a drawer collecting dust, the RCX is definitely worth the extra money. Plus you get a lot more than just the RCX when you buy RIS 1.5. For one thing you get the IR tower, which is pretty much an essential add-on (...) (26 years ago, 8-Sep-00, to lugnet.robotics.scout)
|
