 | | 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)
|
