 | | Re: Robolab, byte codes and assembler
|
|
Hello Don, Did you had a look to my analysis of this problem ((URL) But unfortunately I don't think that my modification is "competition-legal"... I agree that sampling can occur at the wrong time, but this should not occur more often at low (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) I've used some of the LabView features, though it seems like they work best when used on constants, rather than variables or containers. My impression, though, is that the non-Robolab-specific LabView features aren't what I'm looking for (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: failure in communicaton between RCX & IR Tower
|
|
(...) fine (...) (all (...) Ya, its a real pain in the arse... Rob (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Robolab can access LASM code (Lego Assembler) which may allow you to write instructions that fit your needs. The LASM documentation is part of the Mindstorms 2.0 SDK available from (URL) not an assembler programmer so I have no idea if this (...) (22 years ago, 27-Nov-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Robolab, byte codes and assembler
|
|
(...) Two problems: 1. From what I've read about the problem, the speed I ran it at was right in the "sweet spot". 2. BrickOS would not qualify for the competition. I wonder if (hope?) the recent unavailability of rotation sensors at Pitsco is (...) (22 years ago, 26-Nov-03, to lugnet.robotics.rcx.robolab, FTX)
|
