Subject:
|
Re: I2C device for the RCX
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sun, 12 Jan 2003 11:23:42 GMT
|
Viewed:
|
826 times
|
| |
|
|
Hum. i think my first post was not very clear( and whit some stupid mistakes)
I think you now how I2C works: there are to lines, SCL and SDA. so whit this
device, I got to sensor ports, one for SCL and one for SDA. making high and low
signals on the bus is done by switching the sensorport from active to passive
mode. I did not use any motor ports, so sorry for my first(unclear) post. Do
you also know something about these sensor ports?
Gunther Lemm wrote:
> This actually seems to be some sort of 'combined' problem which results from
> the brickOS-kernel doing task scheduling plus some ROM-internal functions
> eating up some CPU-time.
> I did some research on it and came up with a rather evil solution. Take a look
> at http://lepomux.org/patch.html
well, same problem here, It looks very promising, but it is for motor outputs
do you think this also works for the sensor ports?
thanks for all the trouble,
bas
|
|
Message has 1 Reply:
 | | Re: I2C device for the RCX
|
| (...) I think it will - as long as you put the sensor handler on timer B (the motor handler probably can stay there too). Take a close look at _ds_handler inside the file dsensor.c. That's where all the active/passive switching and sensor readout is (...) (22 years ago, 12-Jan-03, to lugnet.robotics)
|
Message is in Reply To:
| | Re: I2C device for the RCX
|
| (...) high (...) frames (...) very (...) anyone (...) I (...) BrickOS (...) In the current release of BrickOS, the motors only get updated by the timer ISR every 2ms, so that probably explains why trying to twiddle the bits any faster than that (...) (22 years ago, 11-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
|
|
|
|
