To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.nqcOpen lugnet.robotics.rcx.nqc in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / NQC / 1702
1701  |  1703
Subject: 
Re: bad motor output because of lego firmware?!
Newsgroups: 
lugnet.robotics.rcx.nqc
Date: 
Wed, 3 Nov 2004 17:45:38 GMT
Viewed: 
5441 times
  
In lugnet.robotics.rcx.nqc, Steve Hassenplug wrote:

In any case, if you want your extender to be something you can market to most
users, it should work with the standard firmware, without modification.

Just my opinion
Steve

That's right. I simply didn't expect any problems with NQC + Lepomux because I
assumed that any RCX-OS has the ability to directly control the motor output. If
I had used NQC a little bit more, I surely would've noticed that strange output
behaviour of the Lego firmware.
Dick Swan's alternative RCX-firmware will hopefully do the job.

Gunther



Message is in Reply To:
  Re: bad motor output because of lego firmware?!
 
(...) I suspect part of this delay is inherant to the firmware, and won't be "patchable" In any case, if you want your extender to be something you can market to most users, it should work with the standard firmware, without modification. Just my (...) (20 years ago, 28-Oct-04, to lugnet.robotics.rcx.nqc)

4 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

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