|
| | Re: bad motor output because of lego firmware?!
|
| (...) That's right. I simply didn't expect any problems with NQC + Lepomux because I assumed that any RCX-OS has the ability to directly control the motor output. If I had used NQC a little bit more, I surely would've noticed that strange output (...) (20 years ago, 3-Nov-04, to lugnet.robotics.rcx.nqc)
| | | | Re: SetUserDisplay?
|
| (...) correct. Kevin (20 years ago, 30-Oct-04, to lugnet.robotics.rcx.nqc)
| | | | Re: SetUserDisplay?
|
| (...) Thanks Dave. I didn't notice the RCX2 option in Bricxcc, works great now! Just to clarify, the only difference between RCX 1 & 2 (from the compile target POV) is the firmware it's running? ROSCO (20 years ago, 30-Oct-04, to lugnet.robotics.rcx.nqc)
| | | | Re: SetUserDisplay?
|
| (...) My guess is that NQC hasn't been told to target the 2.0 api, so it is defaulting to 1.0 which does not have SetUserDisplay(). See (URL) for a more detailed explanation. Dave (20 years ago, 30-Oct-04, to lugnet.robotics.rcx.nqc)
| | | | SetUserDisplay?
|
| I can't seem to get SetUserDisplay to compile. When I compile my program, it gets "Error: undefined function 'SetUserDisplay'". I thought it might be the version of NQC (3.0a1) so I downloaded 2.5r3, but same error. Seems strange because (...) (20 years ago, 30-Oct-04, to lugnet.robotics.rcx.nqc)
| |