 | | Re: NQC API for the new Swan firmware
|
|
(...) I would in this case prefer the second - I actually use a "kMyNamedConstant" convention in my code, and find it very nice to have the API constants very easily seperable from my constants. (...) Again, personally I would prefer that, as it (...) (21 years ago, 11-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC API for the new Swan firmware
|
|
I am working feverishly on updates to NQC which will include extensions to the built-in API in support of Dick Swan's new firmware. My intent is to be consistent with the existing NQC API. However, there are some issues I am debating and I would (...) (21 years ago, 11-Jan-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LNPd keeps sending TX_FAILURE
|
|
(...) Here is my ls -l: tyler@gyro life $ ls -l /dev/ttyS0 lr-xr-xr-x 1 root root 5 Jan 9 05:01 /dev/ttyS0 -> tts/0 tyler@gyro life $ ls -l /dev/tts/0 crw-rw---- 1 tyler tty 4, 64 Jan 9 11:17 /dev/tts/0 I've tried running as root and as tyler, (...) (21 years ago, 9-Jan-05, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNPd keeps sending TX_FAILURE
|
|
(...) hmmm, bad. I never did much wich lnp, but it worked on my machine. (...) I hope so :) Reading the problem description in your first posting gives me a knot in my brain. Next possible problem is a problem with the rights for your /dev/ttySx. If (...) (21 years ago, 8-Jan-05, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNPd keeps sending TX_FAILURE
|
|
(...) I tried the PARENB | PARODD fix. All it did was prevent the PC from receiving anything from the RCX, and it still didn't send anything. Is there anything I missed? (21 years ago, 7-Jan-05, to lugnet.robotics.rcx.legos)
|
