 | | Ping mode for US Sensor in NXT-G —Guy Ziv
|
| | | I've written a detailed toturial on working in ping mode in NXT-G using I2C read/I2C write block and the US Sensor block. Read it here: (URL) shows how you can set the sensor to ping mode, read and display all 8 measurements and alternatly ping two (...) (18 years ago, 28-Feb-07, to lugnet.robotics.nxt)
|
| | | |
| | | | | Re: Ping mode for US Sensor in NXT-G —David Wallace
|
| | | | Hi Guy, You inspired me to do a ping using NBC, but I have run into trouble. I get a -35 (ERR_COMM_BUS_ERR) when I try to read more than one object reading. The code is long, so I'll just put the basics of what I am doing here to see if anyone (...) (18 years ago, 4-Mar-07, to lugnet.robotics.nxt)
|
| | | | |
| | | | | | Re: Ping mode for US Sensor in NXT-G —John Barnes
|
| | | | (...) You are using firmware version 1.04, right? 1.03 doesn't work well for multibyte reads. JB (18 years ago, 4-Mar-07, to lugnet.robotics.nxt)
|
| | | | |
| | | | | | Re: Ping mode for US Sensor in NXT-G —David Wallace
|
| | | | (...) multibyte (...) Yes I am John. But I am doing separate single-byte reads. I base this on the US sensor hardware doc where it indicates 0x02, 0x42 for the closest distance, 0x02, 0x43 for the next, 0x02, 0x44 for the next, etc. This also (...) (18 years ago, 4-Mar-07, to lugnet.robotics.nxt)
|
| | | | |
| | | | | | Re: Ping mode for US Sensor in NXT-G —David Wallace
|
| | | | Nevermind - my error. I was using some of NBC's internal variables/routines because I was going to suggest that John H. add a Ping command and I didn't realize that the variable I was using was later being blown away for another use later. Sorry for (...) (18 years ago, 4-Mar-07, to lugnet.robotics.nxt)
|
| | | | |
