 | | Re: Attention please: Swan Problem demi-solved!
|
|
Here's the problem! I don't have fast0103.lgo, on swan's site there's only version 1.01. I think using that firmware (where can we find it?) and new NQC API all my problems are solved. About driving servo: to generate PWM for servo motors a (...) (19 years ago, 21-Jul-05, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
| |
| | Re: Attention please: Swan Problem demi-solved!
|
|
(...) Quite possibly you have an old version of the Swan firmware. My copy is called fast0103.lgo dated 2005-01-13. Dick sent me an updated version back then when I was working on the NQC API for his firmware. I don't know if it is available (...) (19 years ago, 21-Jul-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Attention please: Swan Problem demi-solved!
|
|
I tried to use files included in OLD test_swan.zip and RCX don't throw exception 40 no more! Then I tried a program with #include "swan.nqh" with latest NQC version and RCX throws exception no.5! To Dick Swan: NQC API is changed from old test_swan (...) (19 years ago, 20-Jul-05, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | Re: I've got what Iain Hendry's got, was Re: Swan Firmware
|
|
(...) Hi John I've fixed the problem. I tracked it down by commenting out parts of my program. Luckily I started on the function containing the problem So I found it very quickly. Solving the problem took longer though. As you can see below I've (...) (19 years ago, 16-Jul-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: I've got what Iain Hendry's got, was Re: Swan Firmware
|
|
(...) Can you please email me the NQC source so that I can generate the listing to see if possibly the compiler is generating invalid code? John Hansen (19 years ago, 16-Jul-05, to lugnet.robotics.rcx.nqc)
|
| |
| | I've got what Iain Hendry's got, was Re: Swan Firmware
|
|
(...) I've got the flashing five problem as well, and it's really annoying, I spent most of my Friday in vain trying to fix it. I thought/think it's a stack overflow problem, but after serious optimising of my program It's made zero difference. (...) (19 years ago, 16-Jul-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC FAQ updated
|
|
I have updated the NQC FAQ with a description of how to fix a USB Tower problem that many users have experienced when downloading a program via NQC. Many users have reported that they get a "Compile Failed no (or invalid) reply from RCX" error when (...) (19 years ago, 29-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) In C you would declare a as volatile. Jürgen (19 years ago, 11-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC release 3.1r2
|
|
I have released NQC version 3.1r2. The only change from 3.1r1 is a fix to the Spybot FindWorld API function. (URL) Hansen (19 years ago, 10-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | BricxCC release news
|
|
I continue to work on getting BricxCC ready for a new official release. My sincere apologies for not having one out at the beginning of the year as I had originally planned. Life keeps getting in the way. In any case, I have a new update to BricxCC (...) (19 years ago, 6-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) Neither of these work, although the second one does introduce a temporary for everything except for the 0 part. It will result in the display sometimes showing a value of zero. NQC tries really hard to use as few variables as it can so you (...) (19 years ago, 5-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) Thanks for the ideas! Actually these yielded some interesting results: a = 0 + ((x * 100) + y); occasionally yielded 0 (as expected), but never yielded anything other than 0 and the correct value (that I saw). a = ((x * 100) + y); and a = (x * (...) (19 years ago, 5-Jun-05, to lugnet.robotics.rcx.nqc)
|
