Subject:
|
Re: I2C device for the RCX
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Mon, 13 Jan 2003 18:16:07 GMT
|
Viewed:
|
997 times
|
| |
|
|
Bastiaan v.Kesteren wrote:
> every package is 8 bits long, plus an
> acknowledge bit, so 9 bits per package. that means 2385 bits in 375ms, which is
> 6360 bits/sec. This should mean there's a quite stable clockpulse at the sensor
> port at about 666Hz. (did I calculated thatone right?)
Nope, I didn't. Mixed up the packages/sec and bits/sec. It should be 6360Hz.
Sounds even more faster (-:
|
|
Message has 2 Replies:
 | | Re: I2C device for the RCX
|
| ARGH!!!...!!! i'm getting nuts of all these numbers! Now it appears that my stopwatch didn't give the time in steps from 1 ms, but in steps from 10 ms so then the program takes 3750ms, which means 70,6 packages per second. the RCX has send 1 adress (...) (22 years ago, 13-Jan-03, to lugnet.robotics)
| | | Re: I2C device for the RCX
|
| "Bastiaan v.kesteren" <b.van.kesteren53@zonnet.nl> wrote in message news:H8o02v.Gpz@lugnet.com... (...) 375ms, which is (...) at the sensor (...) 6360Hz. (...) I don't understand your references to clock pulses. The I2C protocol is edge triggered (...) (22 years ago, 13-Jan-03, to lugnet.robotics)
|
Message is in Reply To:
| | Re: I2C device for the RCX
|
| Before starting the hacking,I did some tests whit this 'for-lus-delay', and I found the results better than expected. I found that this: for(long i=0;i<100000;i++); takes about 120ms, so one for lus takes 0.0012ms. I made a test program which first (...) (22 years ago, 13-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
|
|
|
|
