 | | Re: NXC - embedded functions failed
|
|
(...) I think having NXC generate a compiler error is a great idea. :-) I will work that into the next beta release (b30). I just released beta 29 today. It has a number of important fixes and enhancements but I just noticed that it has a few new (...) (17 years ago, 22-May-07, to lugnet.robotics.nxt)
|
| |
| | RE: NXC - embedded functions failed
|
|
Hi John, Will throwing in a compilation error be a viable option? --Elizabeth -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...ugnet.com] On Behalf Of Elizabeth Mabrey Sent: Sunday, May 20, 2007 1:19 PM To: (...) (17 years ago, 21-May-07, to lugnet.robotics.nxt)
|
| |
| | Re: pbLua PCF8574 SOLVED !
|
|
(...) Let me say thanks to Dick as well. I think that the NXT firmware does what's called a repeat start in the I2C definition... Here's the part in the I2C spec that is required: (URL) And with pictures: (URL) Hope this helps... Ralph (17 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | Re: pbLua PCF8574 SOLVED !
|
|
(...) Hi Dick, your answer solves my knot :D It's a NXT specific behaviour and all alternatives NXT-OSes which uses original Lego-Source-Lowlevel routines have this feature ? Thanks for your answer Bye Christian (17 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
| |
| | RE: pbLua PCF8574 SOLVED ?
|
|
(...) This is the excepted behavior. When you want to read from I2C device, the NXT firmware first sends a write message to load the internal index "pointer" for the I2C device and then sends a read message that will read the requested number of (...) (17 years ago, 21-May-07, to lugnet.robotics.nxt, lugnet.robotics.nxt.nxthacking)
|
