 | | Re: lcd display on RCX 1.0
|
|
(...) If you load RCX2 firmware in a RCX1 brick (they are fully compatible*), you'll have acces to this function (and all other RCX2 specific possibilities) Philo *Except for some minor differences in IR hardware. (18 years ago, 25-Jun-07, to lugnet.robotics.rcx.nqc)
|
| |
| | lcd display on RCX 1.0
|
|
NQC: with RCX2, it has a function to display a user defined value. Is there a way to do it with RCX 1.0? How about just to display the current mail value with RCX1.0? Suggestion? Thanks in advance. --Elizabeth (18 years ago, 24-Jun-07, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Shutdown/Off while program running crashes BrickOS
|
|
(...) Yes, that should be the latest version. (...) That is correct. You shouldn't need to do anything else. At one point, I made some changes to the firmware so the program could also access the run button. But, normally all that is handled in the (...) (18 years ago, 17-Jun-07, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Shutdown/Off while program running crashes BrickOS
|
|
(...) I'm using what appears to be called BrickOS 0.9.0. It was installed using John Hansen's simplified installation from his BricxCC sourceforge site. I was under the impression that on later versions of BrickOS, like what I am using, the firmware (...) (18 years ago, 17-Jun-07, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Shutdown/Off while program running crashes BrickOS
|
|
(...) Gus, It sounds like the code is testing for pressing the run button, but not pressing the power button. I would think testing for shutdown would be good enough, but who knows... :) What version of BrickOS are you using? I'd be glad to take a (...) (18 years ago, 17-Jun-07, to lugnet.robotics.rcx.legos)
|
| |
| | Shutdown/Off while program running crashes BrickOS
|
|
I have a big and somewhat complicated BrickOS program that I believe is reasonably well behaved. All my loops monitor shutdown_requested and I have tested stopping the program with the Run button while the program is in various states and it always (...) (18 years ago, 16-Jun-07, to lugnet.robotics.rcx.legos)
|
| |
| | RoboLab
|
|
Have a great Summer Tom Lohre’s Quarterly Art Show at Med+ Opening July 14th, 2007 from 6:30 to 9 PM, light refreshments served. In the lobby of Med+ Urgent Care, 9549 Montgomery Rd. Suite 100, Cincinnati, OH 45242, 513-489-3737, just north of (...) (18 years ago, 12-Jun-07, to lugnet.robotics.rcx.robolab)
|
| |
| | NQC release 3.1r6 - support for 64-bit platforms
|
|
I have posted a new release of NQC which includes the fixes from r5 which were never officially released (aside from being included along with recent versions of BricxCC). It also includes a small source code change which makes it possible to (...) (18 years ago, 11-Jun-07, to lugnet.robotics.rcx.nqc, lugnet.robotics)
|
| |
| | Alternate firmware upload from MacOSX
|
|
Hi all, We're trying to wrap up our alternative runtime for the RCX (first), and soon the NXT. I am struggling, however, to upload our firmware from the Mac using a USB tower. I can upload using a serial or USB tower from both Windows and Linux... (...) (18 years ago, 10-Jun-07, to lugnet.robotics.rcx)
|
| |
| | Re: Getting patches integrated into the brickos?
|
|
(...) As far as I know, all the sourceforge web pages are held in the CVS repository, as are the sources. Only people with developer permission on the project have commit access to CVS - you have to contact the project admins to request that (...) (18 years ago, 25-Apr-07, to lugnet.robotics.rcx.legos)
|
| |
| | Getting patches integrated into the brickos?
|
|
I've been trying to build a cross compiler and brick-os on my machine for a day now and well, what can I say except that all the how-to's and instructions for building brick-os seem to be either wrong, bad or out of date. (e.g. they talk about very (...) (18 years ago, 23-Apr-07, to lugnet.robotics.rcx.legos)
|
| |
| | Re: IR Problems
|
|
(...) tom@tomlohre.com is my private address (18 years ago, 14-Apr-07, to lugnet.robotics.rcx)
|
| |
| | Re: IR Problems
|
|
(...) tom@tomlohre.com Dear Claude, Thanks for your message. I have delayed in replying to the excellent advice concerning communication with more than one RCX. Last night in a dream I realized that I could just bypass communication placing two push (...) (18 years ago, 13-Apr-07, to lugnet.robotics.rcx)
|
| |
| | Re: IR Problems
|
|
(...) Thank you for the excellent information concerning communication with more than one RCX. Last night in a dream I realized that I could just bypass communication placing two push button sensors where needed driving the additional RCX. The (...) (18 years ago, 13-Apr-07, to lugnet.robotics.rcx)
|
| |
| | Re: IR Problems
|
|
Hi Tom, I tried to send you a private mail, but the email address I have doesn't work anymore. Could you give me the new one? -Claude (18 years ago, 3-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
Elizabeth is quite right. It's easy to get collisions on the IR "bus" if two devices are sending (or replying) simultaneously. What I've done in the past with two RCXs is define one RCX as primary that is periodically (every 100 to 250 milliseconds (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
RCX IR does not require direct line of sight. All sorts of reflections will work. Especially if you're in a "smallish" (bedroom, home office) room. The RCX firmware always has the IR turned off. "Wait for mail" and "send mail" is just a higher (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
IR communication is no where near the reliability like a tcp/ip. You can easily lose a message ... so program must be either extremely simple one way communication. The sender should be programmed to handle message loss. What I had the kids done was (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | Re: IR Problems
|
|
(...) Thanks for your reply. I had to return the 1.0 RCX and motor back to school today. Those things are like gold. The 1.0 faces the 2.0 and is not in direct line of sight of the tower. The 1.0 is just to the side of the tower. I think my problem (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
| |
| | RE: IR Problems
|
|
Are you sure your problem isn't interference? How did you "lock out" the RCS 1.0 from receiving (and responding) to the direct commands? You have two RCXs turned on and sending direct commands from the PC. They will both try to respond to the (...) (18 years ago, 2-Apr-07, to lugnet.robotics.rcx)
|
