Subject:
|
Re: bad motor output because of lego firmware?!
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 28 Oct 2004 17:47:17 GMT
|
Viewed:
|
5415 times
|
| |
|
|
In lugnet.robotics.rcx.nqc, Gunther Lemm wrote:
> I've spent the last two days trying to write a function in NQC that transfers
> data to the Lepomux I/O-extender.
> There is a gap of at least 3ms between the fwd->off and the off->rev edge. This
> makes it impossible for the Lepomux to recognize it as one edge.
> The reason for this behaviour seems to be that the bytecode interpreter (or even
> the ROM routines) don't directly access the motor output register in the RCX
> (two bit per motor for off,fwd,rev,brk).
>
> Does anyone know a workaround or do I really have to patch the Lego firmware
> image?
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 opinion
Steve
|
|
Message has 1 Reply:
 | | Re: bad motor output because of lego firmware?!
|
| (...) 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 (...) (20 years ago, 3-Nov-04, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | bad motor output because of bad lego firmware?!
|
| Hi there, I've spent the last two days trying to write a function in NQC that transfers data to the Lepomux I/O-extender. The data transfer is normally done by connecting the Lepomux to one of the motor ports. Each transition from one motor state to (...) (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
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
