|
 | | RE: Custom Firmware, IR Problems, and Dead RCXs (long)
|
| (...) The use of alternative firmware such as pbForth, legOS and leJOS usually requires frequent upload/download cycles, and may use long communications periods. (...) I agree on this point, but that will affect the low power range more as well. (...) (23 years ago, 29-May-01, to lugnet.robotics)
| |
|  
mindstorms, firmware
(score: 0.619)
|
|
| | RE: Custom Firmware, IR Problems, and Dead RCXs (long)
|
| (...) You are right, but the RCX and the tower are right at the hairy edge. The additional 50R impedance will leave the near mode essentially unchanged and I'll sacrifice on the high range. Start with the tower. If you use a 9V battery, the IR (...) (23 years ago, 28-May-01, to lugnet.robotics)
| |
|
mindstorms, firmware
(score: 0.619)
|
|
| | RE: Custom Firmware, IR Problems, and Dead RCXs (long)
|
| (...) Well, yes and no. The biggest risk is when you use the tower or the RCX in high-power (far) mode for extended transmissions. I was thinking about why we have not received more posts about dead RCXs. My old pbForths (and I think legOS too) set (...) (23 years ago, 27-May-01, to lugnet.robotics)
| |
|
mindstorms, firmware
(score: 0.619)
|
|
| | Re: ScriptEd - Question
|
| (...) Hi Steve, I see the message apearing in the status bar, but it's an error! Error is : Error (0xe0050801) from VPBrick compiler The error apears in following line: const delay1 = 1000 // minimum stop time in station (10 seconds) The word (...) (19 years ago, 4-Aug-05, to lugnet.robotics.rcx)
| |
|
firmware
(score: 0.618)
|
|
| | Re: lego firmware in hex to high level language
|
| (...) I'd like to do that too, but I'd settle for assembler. It can be done if you download the Hitachi H8 processor datasheet and interpret the opcodes. You'll need to understand the memory map to know what's going on. As written, I think the (...) (19 years ago, 26-Jul-05, to lugnet.robotics)
| |
|
firmware
(score: 0.618)
|
|
| |
|
firmware
(score: 0.618)
|
|
| | Re: Swan firmware crash!
|
| (...) This is the old-style Swan API which is deprecated. The Swan API built into NQC uses MotorPower128(n) and SetMotorPower128(n, m). With the latest version of NQC you no longer need to include the old swan.nqh header file. The old swan.nqh file (...) (19 years ago, 21-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.618)
|
|
| | Asking about Firmware (need help)
|
| Dear All I`m a newbies in programming LEGO Mindstorms RIS. I have explored CD that embedded in my RIS KIT. Now i want to try make a user interface for LEGO Mindstorms RIS in my own language. I used microsoft visual c++ to build my software From the (...) (23 years ago, 26-May-01, to lugnet.robotics)
| |
|
mindstorms, firmware
(score: 0.618)
|
|
| | RE: Swan firmware crash!
|
| I have put "fast0103.lgo" on web page. It appears that web page on my ISP (drjsoftware.com) doesn't match the local copy on my PC's hard drive. It will take me a few days to update. I'm also planning to release a firmware update in the same (...) (19 years ago, 22-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.618)
|
|
| | Swan firmware crash!
|
| Hi. I've installed new NQC and BRICXcc to test new functions in fast firmware by Dick Swan. I wanted to see if the new 1/1000th second resolution could let me drive a servo. When I try to use the SetMotorPower128 command, compiler is ok, downloading (...) (19 years ago, 19-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.618)
|
|
| |
|
firmware
(score: 0.618)
|
|
| | RE: Swan firmware crash!
|
| Exception error 40 is intended to indicate that you've tried to write to an invalid source parameter value. "Source parameter" is the first byte of an internal interpreter variable (0 is variable, 2 is constant, etc). If you send me the NQC source I (...) (19 years ago, 20-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.617)
|
|
| | Re: Swan firmware crash!
|
| (...) I already post a simple code that causes the error: (URL) task main{ SetMotorPower128(MTR_A,100); SetOutput(MTR_A,OUT_REV); Wait(300); Off(MTR_A); } The command SetMotorPower128 is the cause. (if I remove it, all works). Today I get also the (...) (19 years ago, 20-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.617)
|
|
| | Re: Swan firmware crash!
|
| (...) Here is Bricxcc help about those commands: SetMotorPower128(const int motor, const int &v) Function - Swan Set the power of a motor to the specified value (using a scale from 0 to 127). SetMotorPower128(MTR_A, 100); ___...___ (...) (19 years ago, 20-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.617)
|
|
| | Re: Swan firmware crash!
|
| (...) * Maybe I wasn't too clear, but really there isn't much to say: it is the SetMotorPower128 command that causes the error. * Another question is: why costants MTR_A or MTR_B don't work at all? Here's the code(all the code): task main{ (...) (19 years ago, 20-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.617)
|
|
| | Re: Swan firmware crash!
|
| (...) That's where your completely wrong. I can see the error, calls to motor power should be set out like this motorPower128(1) = MyVariableName; in this example the constant "1" means set the power to output B to the value specified by (...) (19 years ago, 20-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.617)
|
|
| | Re: Swan firmware crash!
|
| (...) You haven't given us(readers) much to go on. I had a similair problem but finding the solution was a bit of a fluke. If you could provide some info like program size, and a description of what the program does or some code we may have more (...) (19 years ago, 19-Jul-05, to lugnet.robotics.rcx.nqc)
| |
|
firmware
(score: 0.617)
|
|
| |
|
firmware
(score: 0.617)
|
|
| |
|
firmware
(score: 0.616)
|
|
| |
|
firmware
(score: 0.616)
|
