Subject:
|
Re: I2C device for the RCX
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Wed, 15 Jan 2003 19:42:21 GMT
|
Viewed:
|
1058 times
|
| |
|
|
In lugnet.robotics, Bastiaan van Kesteren writes:
> >
> > Some days ago we had another idea of how to transfer about 100 bytes/s
> > without
> > a kernel patch (that should even work with NQC).
>
> whit NQC? thats intresting! This is even faster than what I got here
> whit my BrickOS driver! I would surely like to know more about this! the
> I2C device made a max transfer of 27 bits/sec(=about 3,4 bytes/sec(!))
> whit NQC.
We'll first check it out before boasting about it ;)
The whole thing won't work without some hardware modifications on the lepomux -
so I'll tell you about it in two or three weeks.
Gunther
|
|
Message has 1 Reply:
 | | Re: I2C device for the RCX
|
| (...) ... took slightly longer than 2 weeks, but now it works as expected. Using BrickOS you'll get up to 100 byte/s without any patch. I've put a protocol description on www.lepomux.org. Gunther (22 years ago, 1-Mar-03, to lugnet.robotics)
|
Message is in Reply To:
| | Re: I2C device for the RCX
|
| (...) Well, one reason for this is that I2C doesn't need a precise clocksignal (thanks to Dick Swan for telling me, I totally forgot about it). All the timer stuff shouldn't matter for the I2C device, so there should be even higher speeds possible, (...) (22 years ago, 15-Jan-03, to lugnet.robotics)
|
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
|
|
|
|
