To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.robolabOpen lugnet.robotics.rcx.robolab in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / ROBOLAB / 245
244  |  246
Subject: 
Re: Robolab, byte codes and assembler
Newsgroups: 
lugnet.robotics.rcx.robolab
Date: 
Thu, 27 Nov 2003 13:39:21 GMT
Reply-To: 
Dick Swan <DICKSWA@SBCGLOBALspamless.NET>
Viewed: 
9509 times
  
"Don Stauffer" <BrainChild@Skyler.com> wrote in message
news:Hoz4Gp.1zto@lugnet.com...
Having investigated rotations sensors thoroughly, I conclude
they have some serious design flaws. ... • <<SNIP>>
So, is there a way in Robolab to write a sub vi-like routine,
and specify theactual byte code instructions, just for that
time-critical part of the program, to be called by a regular
Robolab program?

The rotation sensor bad counts cannot be fixed at the byte-code
level. The problem is "native" to implementation in the underlying
firmware code.

Several of the RCX replacement OSes have improved the rotation
sensor performance. But of course they no longer run the byte codes.
It might be feasible to patch /hack their code back into Lego's
byte-code interpreter firmware. Which raises two questions:
[1] Would this still be competition legal?
[2] When is your competition date (i.e. how soon do you need it)?

The process that might be possible is the following:
[1] Use the rotation sensor handler source code from one of
    the replacement OSes. Less that 200 bytes of code.
[2] Assemble this code at some unused location within current
    Lego firmware. (E380 to EE5D looks like unused locations).
[3] Make the Analog-to-digital interrupt handler routine point to
    this "patch". (And also add a few other rotation handler hooks).
[4] Manually edit (via NOTEPAD or similar) the "firm0328.lgo" file
    to include this patch.
[5] Download the modified "firm0328.lgo" file.
[6] Everything remains Robolab compatible.



Message has 1 Reply:
  Re: Robolab, byte codes and assembler
 
Thanks for the response. (...) It seems to me it's a design flaw in the entire method of counting rotations, which relies on the theoretical ideal of "instantaneous" voltage changes, which can't be produced. You can't go from 2V to 5V without (...) (21 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)

Message is in Reply To:
  Robolab, byte codes and assembler
 
Having investigated rotations sensors thoroughly, I conclude they have some serious design flaws. Most notably, some samples taken during voltage transitions can be impossible to differentiate from samples at entirely different rotational positions. (...) (21 years ago, 26-Nov-03, to lugnet.robotics.rcx.robolab)

24 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
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR