 | | Re: RCX <-> PC communication
|
|
(...) Kaspar, There is a bug with serial towers with RCXPort in lejos 2.0. This causes the problem you are seeing. There is a fixed version in (URL) fixes RCXPort, but I haven't put the fix in the LNP versions yet. I only have a USB Tower, and (...) (24 years ago, 16-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: RCX <-> PC communication, more details
|
|
Hi Kaspar, Thanx for the information. In the Lejos-discussion mailing list (Sept 13), Lawrie Griffiths wrote: "A timeout of 100 milliseconds or more should ensure that it reads all the bytes in one message." Looks like it confirms what you (...) (24 years ago, 16-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: RCX <-> PC communication, more details
|
|
(...) Great, I just had too much time at hand, so I could already test the hypothesis above. Great, to be able to post a followup to my own message within half an hour... Ok, here it comes: The PC __IS__ swamping the RCX when using the LNP protocol. (...) (24 years ago, 16-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | RCX <-> PC communication, more details
|
|
Thanks for the three of you (Francois, Roger and Lawrence) who have answered to my questions. I was asked to state some more details, which I'll do here: I am working under linux (SuSE 7.3) and since the linux version of java does not yet support (...) (24 years ago, 16-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: RCX <-> PC communication
|
|
(...) Lawrie Griffiths asked me to forward the following to you: RCXPort should be about twice as fast as RCXF7Port. Do you have a serial or USB tower? I am concerned that you don't get complete reliabilty with RCXPort - I do with a USB Tower. (24 years ago, 14-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: RCX <-> PC communication
|
|
(...) I have not done any experimenting with Data Streams yet since I can get by with bytes. I have tried both the RCXPort and the RCXF7Port. The big advantage of the RCXPort using the LLC protocol is that if the RCX gets out of range or behind an (...) (24 years ago, 13-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: RCX <-> PC communication
|
|
Hi Kaspar, Did you compile the PC end program using javac and did you add pcrcxcomm.jar from the lejos lib directory to your CLASSPATH? Could you give some more details about your problem (what platform are you working on? complete code...)? Wap (...) (24 years ago, 12-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | RCX <-> PC communication
|
|
Ok, here's a little something to think about: I have been testing the three communication protocol stacks of LeJOS 2.0 (josx.rcxcomm package; LLC, LNP and F7 protocols). Simple application: Array (size 20) of ints on both PC and RCX. Got both a (...) (24 years ago, 10-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Help with Clock
|
|
(...) That's currently done in the leJOS loader (see rcx_impl/main.c), and only if no program is running. So you can't turn it off, but you don't need to turn it off either once your program is running ... Jürgen (24 years ago, 5-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Help with Clock
|
|
What about turning the timer off that turns the RCX power off. What would be the class and method or is it a ROM routine. Thanks, Scott (24 years ago, 4-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Help with Clock
|
|
(...) Interesting, I should browse through the classes every now and then ... One thing to note is that josx.platform.rcx is not the right place for it, as it is independent of the RCX platform (maybe josx.util ?). (...) I think it would be better (...) (24 years ago, 3-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Help with Clock
|
|
(...) Here is a Stopwatch class that does the sort of thing that Jeurgen discussed in his message. You can instantiate as many stopwatches as you want to keep track of the elapsed time between different events. import josx.platform.rcx.*; /** * (...) (24 years ago, 3-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Legos or Lejos
|
|
(...) If you already know some Java, I recommend Lejos. It has some very reliable classes for RCX to RCX communications using Java streams. It also has some useful debugging features. Good luck, Roger (24 years ago, 3-Sep-02, to lugnet.robotics.rcx.java, lugnet.robotics.rcx.legos)
|
| |
| | Re: Help with Clock
|
|
Hi Scott, (...) yes. It is like a big wall clock that shows milliseconds. (...) System.currentTimeMillis(); Note that this is a long integer. If you need more than one timer you can remember the time in variables and then compute the difference, (...) (24 years ago, 1-Sep-02, to lugnet.robotics.rcx.java)
|
| |
| | Help with Clock
|
|
I am using legjos and... having problems understanding the clock/timers. 1. Are their only one timer clock? 2. How do you acess the timers clock? What code would I use? Scott (24 years ago, 29-Aug-02, to lugnet.robotics.rcx.java)
|
| |
| | Re: Legos or Lejos
|
|
Hi Geeraard, Well, it mostly depends on what is your favorite language. If you're a hard-core C coder and don't mind working in a difficult coding environment, LegOS might be for you. Otherwize I would recommend leJOS. Note that in the past, LegOS (...) (24 years ago, 29-Aug-02, to lugnet.robotics.rcx.java, lugnet.robotics.rcx.legos)
|
| |
| | Legos or Lejos
|
|
Hello, I was wondering which OS to use for my RCX. ( Legos or Lejos) I've searched the internet and found out that Lejos is newer than Legos and had in the past not all the functions of Legos. Is there any change in this? I need the RCX to RCX (...) (24 years ago, 28-Aug-02, to lugnet.robotics.rcx.java, lugnet.robotics.rcx.legos)
|
| |
| | Re: Sensor port cross talk
|
|
(...) Yes. I avoid using raw mode whenever possible because of the background fluctuations I see in sensor values. These could quite easily swamp the VM making the robot appear unresponsive. Whereever possible I use percentage values if I need (...) (24 years ago, 1-Aug-02, to lugnet.robotics.rcx.java)
|
| |
| | RE: Sensor port cross talk
|
|
(...) If you've ever worked with multi-port A/D converters on a micro, and scanned all of the inputs you've been bitten by this one. It's caused by two things, parasitic capacitance on the chip itself and leakage between the lines going to the A/D (...) (24 years ago, 1-Aug-02, to lugnet.robotics.rcx.java, lugnet.robotics.rcx)
|
| |
| | Re: Sensor port cross talk
|
|
This is certainly a known defect in the input circuitry in the RCX. I know nothing about other kernels apart from the standard Lego one (via NQC) but the results of my examining the problem indicated that the ports are scanned in reverse order, 3 - (...) (24 years ago, 1-Aug-02, to lugnet.robotics.rcx.java)
|
