Subject:
|
Re: Ultimate ROBOLAB
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sun, 12 Dec 2004 15:02:45 GMT
|
Viewed:
|
1198 times
|
| |
|
|
In lugnet.robotics, Claude Baumann wrote:
> In lugnet.robotics, Jerry Kalpin wrote:
> > While I program all my projects using Robolab, I suspect that 'Ultimate Robolab'
> > is so far above my capabilities that I should not attempt to use it.
>
> Ultimate is close enough to standard ROBOLAB to allow easy programming too.
> Ultimate certainly is not reseved for high specialists.
> >
> > Here's what I understand: Ultimate Robolab is a program, which works with
> > Robolab 2,5.4 but compiles its end product (my LEGO program) directly to
> > Assembler language and H8 opcodes ...so that... I no longer need the LEGO RCX
> > firmware to be installed first to do that work of compiling. Therefore, you
> > call the programs it creates 'firmwares'.
>
> Right. The gain is : memory, speed and control; the loss is : longer download
> speed.
I think Ultimate Robolab sounds very cool. Unfortunately, I think some Robolab
users may be confused by the name and think that their Robolab programs will be
completely reuseable in Ultimate Robolab. As far as I can figure this is simply
not the case.
The entire API of Robolab is geared toward the standard RCX/Scout firmware which
is not present when you are using Ultimate Robolab. Ultimate Robolab looks like
it is probably akin to brickOS or Quite C which are very similar to NQC in many
ways but which have a somewhat different API for accessing the RCX inputs and
outputs. That means you can't take an NQC program and compile it for brickOS or
Quite C. With the right preprocessor macros, custom header files, and a really
simple NQC program you might be able get it to work. My guess is that
non-trivial Robolab programs will face similar challenges if you tried to use
them in Ultimate Robolab.
Perhaps my lack of experience with Robolab is giving me the wrong impression.
Am I right Robolab vs Ultimate Robolab? Will Robolab users be able to reuse
their existing LEGO programs (as Jerry asks above) in Ultimate Robolab?
The Ultimate Robolab info page says this:
"compatible with standard firmware opcodes 0x10 (ping), 0x63 (uploadRAM),
0xA4(uploadDatalog)... "
I'm wondering what the "..." means. It sounds almost as if the base firmware
code used in Ultimate Robolab supports more standard firmware opcodes than the
three listed. Support for some of the standard firmware opcodes is something
I've long hoped would be added to brickOS.
John Hansen
|
|
Message has 1 Reply:
 | | Re: Ultimate ROBOLAB
|
| (...) Yes and no! In fact, the name Ultimate ROBOLAB was chosen together with the father of ROBOLAB Prof Chris Rogers. This might be a bit confusing as to compatibility. But compatibility there is: 1. Most of the "modifiers" like "Red (...) (20 years ago, 12-Dec-04, to lugnet.robotics)
|
Message is in Reply To:
| | Re: Ultimate ROBOLAB
|
| (...) Ultimate is close enough to standard ROBOLAB to allow easy programming too. Ultimate certainly is not reseved for high specialists. (...) Right. The gain is : memory, speed and control; the loss is : longer download speed. (...) So did I. But (...) (20 years ago, 12-Dec-04, to lugnet.robotics)
|
8 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
