RoboSavvy Forum

I can get to the file now.

2006-06-02T22:02:27+01:00

I think the robosavvy site must have had a temporary problem.

When (if?) I get this working, I'll post the code and schematic.

Statistics: Posted by dshinsel — Fri Jun 02, 2006 10:02 pm

Re: Can't get to the file?

2006-06-01T03:14:33+01:00

dshinsel wrote:
Good timing, I am getting ready to try reading from an I2C I/O expander chip (hooking up a bumper sensors, etc.)

However, I can't see the .bas file. It looks like ALL the uploaded files have been deleted?

I seam to be able to get to the file. If I type the following in my address line:

http://robosavvy.com/Builders/KurtE/I2C_Test.bas

It shows the file in my browser. Maybe there is some type of file protection in place?

Just in case you still could not get to it, I did send you an email with the contents.

Good Luck with the expander chip.

Statistics: Posted by KurtE — Thu Jun 01, 2006 3:14 am

Can't get to the file?

2006-05-31T21:12:21+01:00

RE: "I put a copy of my test basic file up at:
http://robosavvy.com/builders/kurte/i2c_test.bas "

Good timing, I am getting ready to try reading from an I2C I/O expander chip (hooking up a bumper sensors, etc.)

However, I can't see the .bas file. It looks like ALL the uploaded files have been deleted?

Maybe you can just paste the I2C code here?
if not, could you email it to me: dshinsel verizon.net

Thanks!
I'll be posting my latest stuff soon...

Statistics: Posted by dshinsel — Wed May 31, 2006 9:12 pm

I2C and IO Ports...

2006-05-28T00:19:03+01:00

subpilot wrote:
Nice work, You going to share?

Sure . It is not pretty (or fast), but it appears to be at least somewhat working.

I put a copy of my test basic file up at:
http://robosavvy.com/Builders/KurtE/I2C_Test.bas

It has values assigned for which pins you are using for SDA and SCL.

Likewise it has two constants defined for the I2C address of the range finder. One for reads and one for writes. It is currently set to E4 and E5. This is not the defaults (E0), but happened to be what the sensor I pulled from a different robot was set to.

Later I will improve on this, but for now I wish to start integrating things. LIke mounting a servo to turn the head. Mount sensor on the head, add gyro and wait for new hands...

Good luck

Statistics: Posted by KurtE — Sun May 28, 2006 12:19 am

I2C and IO Ports...

2006-05-27T18:50:56+01:00

Nice work, You going to share?

Statistics: Posted by subpilot — Sat May 27, 2006 6:50 pm

I2C and IO Ports...

2006-05-27T16:47:00+01:00

subpilot wrote:
The I2C is used for the on board EEPROM so I believe the pull-ups exist. Bit Banging via Robobasic is going to be a serious pain.

You are right, The I2c is used by the boards EEPROM, which I believe is the chip marked with ATMEL504. This chip is not mentioned at all in the MR-C3024 spec.

I did some experimenting and I still not sure what RoboBasic input ports (if any) are assigned to the SCL/SDA pins on the board. So I finally decided to use two unused input ports to try to Bit Bang an I2C interface.

So Today I finally had some sucess and I know have RoboBasic code that can do a ping on my Devantech SRF10 (or SRF08) Range Finder

Statistics: Posted by KurtE — Sat May 27, 2006 4:47 pm

I2C and IO Ports...

2006-05-25T09:00:21+01:00

The I2C is used for the on board EEPROM so I believe the pull-ups exist. Bit Banging via Robobasic is going to be a serious pain.

Statistics: Posted by subpilot — Thu May 25, 2006 9:00 am

I2C and IO Ports...

2006-05-25T02:46:40+01:00

RubikCube wrote:
Did you try going to Robonova's website and downloading the MR-C3024 Specification ? The link is http://www.hitecrobotics.com/info/downloads.htm.

Yes thanks!

I am now pretty sure the SDA and SCL lines shown in their I2C example is wrong. I tried changing it over to 24 and 25 and I am seeing some differences with my logic probe. Tomorrow I will pick up my cheap PC based SCOPE and will watch the outputs to help me debug this.

One thing I have noticed through the logic probe is that the system software appears to also manipulate these logic lines. I wonder if they use the I2C for some other purpose?

I will probably take this offline... However I will post something if or when I get it working

Statistics: Posted by KurtE — Thu May 25, 2006 2:46 am

I2C and IO Ports...

2006-05-25T01:17:46+01:00

Did you try going to Robonova's website and downloading the MR-C3024 Specification ? The link is http://www.hitecrobotics.com/info/downloads.htm.

I have used SRF04 and it worked. It does not use I2C, it uses the sonar command and digital i/o ( any two not used servo ports).

Statistics: Posted by RubikCube — Thu May 25, 2006 1:17 am

I2C and IO Ports...

2006-05-24T05:17:35+01:00

I tried again today to connect a Deventech SRF10 Range Finder to my RN-1. This requires I2C, so I have been attempting to convert some C code that I had running on a robot that is based on an AVR16 microcontroller. However since I can not use the native support for I2C that is on this chip through RoboBasic, I ended up trying to do it bit by bit.

So far I am not having much luck . Has had any success using any I2C devices on their RN-1?

Does anyone know if the SDL/SCL lines that are labeled on the board already have pull-up resistors installed on them or not? Also does anyone know what their IO port numbers are? Also does anyone know if HiTec is using I2C for anything else on the board?

I know there is some sample code in the RN-1 user’s manual on page 93, however looking closely at it, I have my doubts if this code fragment would work. In this fragment it says that SCL=22 and SDA=23. With a couple of iterations of my code, I started to have some Servos jitter. That made me wonder if the IO Ports were wrong. The documentation mentioned that there 40 IO ports, so my assumption that 24 of them or the servos, 8 were the ATOD ports and the other 8 would probably be the 8 lines upper left including SCL and SDA, does this make sense? Something like:
IO PORTS
Servos 0-230-23
SCL24
SDA25
PWM026
Pwm127
Pwm228
LCD29
ERX30
ETX31
ATOD0-732-39

I wonder what their code fragment is trying to do. It looks like it is outputting a 4 bit address over SDA, probably the last bit is an R/W bit and then it reads in a byte from the slave from least significant bit to most significant bit. But this does not look like any standard I2C communication. Has anyone else made any better sense of this?

Sorry for just rambling on here .

Statistics: Posted by KurtE — Wed May 24, 2006 5:17 am