 | | LeJOS resource question
|
|
I recently purchased Brian Bagnall's book on LeJOS programming, and was both impressed by what JAVA can do as well as frustrated with trying to learn something new. (The only programming course I have taken was FORTRAN, back in the Jurrassic era). (...) (23 years ago, 12-Apr-02, to lugnet.robotics)
|
| |
| | Re: RCX Firmware speed versus legOS
|
|
(...) Of course you are right. <shame on me> (...) Hm? You don't use the gcc toolchain for the H8 but another compiler? Can you tell a bit more about your compiler? I revised my testings without optimizing out the calculation and the empty loop took (...) (23 years ago, 12-Apr-02, to lugnet.robotics)
|
| |
| | Release candidate legos-0.2.5.2 avail for testing
|
|
Details regarding release content, download instructions and how to provide feedback are at (URL) change detail specific to 0.2.5.2 see the file: ChangeLog Highlights: Added missing file TODO Repaired slow-mode IR comm. for Linux We look forward to (...) (23 years ago, 12-Apr-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX Firmware speed versus legOS
|
|
"Michael Obenland" <obenland@t-online.de> wrote in message news:GuEtHr.M39@lugnet.com... (...) but only (...) assume (...) I was surprized at the wide disparity between 'empty loop' and loop with 'reading the sensor'. I suspect there is significant (...) (23 years ago, 11-Apr-02, to lugnet.robotics)
|
| |
| | Re: Ultrasonic Sensor
|
|
Hello All, Many thanks to all who replied to my original post on this topic. The hardware is build (and works - sometimes(!!!)) and I am now writing the thesis for the project. It is due for submission next week, and if anyone would be interested in (...) (23 years ago, 12-Apr-02, to lugnet.robotics)
|
| |
| | RCX Firmware speed versus legOS
|
|
The discussion about the Firmware speed is intresting indeed. So I did a fast, by no means representative, reserch. The following program is a legOS program reading the light sensor, calculating some values and printing the elapsed time: ---...--- (...) (23 years ago, 11-Apr-02, to lugnet.robotics)
|
| |
| | Re: Turning the RCX off and on again (was: New pbForth 2.1.0 (and firmware speed))
|
|
For the Workshop3D Event I use the following construct, the button handling is from the book "Extreme Mindstorms": : main ( -- ) \ Main Task init \ do main initialize ( ... ) BEGIN ( ... ) BUTTON_SCAN BUTTON_RUN? IF ( ... ) \ Calibrating BEGIN ( ... (...) (23 years ago, 11-Apr-02, to lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | RE: Turning the RCX off and on again (was: New pbForth 2.1.0 (and firmware speed))
|
|
I need to look at some items for Joerg, but I'll also look at a small supervisor that integrates the View,Run,Prgm,and On/Off buttons. This hsould be pretty easy and would be a good bit of example code. Cheers, Ralph (23 years ago, 11-Apr-02, to lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: Turning the RCX off and on again (was: New pbForth 2.1.0 (and firmware speed))
|
|
(...) off (...) True. But I find not very practical to be forced to use the terminal to switch off the RCX or start the program again, expecially when you are attending a contest or take your robot to an exhibit. What I meant by "supervisor" is some (...) (23 years ago, 11-Apr-02, to lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Two RCX with one IR-Tower
|
|
Hello, I want to control two RCX with one ir-tower. The problem is that the RCX should send back status information. Sending information to the RCX is quite easy: Both RCX receive the message but only one will perform the command. I found (...) (23 years ago, 11-Apr-02, to lugnet.robotics.rcx)
|
