A few questions, if I may.
1. Are you using the hardware I2C pins on the PSIM?
2. The PSIM I2C port has the pullup resistors going to ground instead of +5v, did you fix
this?
3. If you did not fix the resistors, then the I2C port is not open collector (drain) but is
using the "hard" pullups on the GPIO section of the pin driver. That means only 1 device
can be on the I2C bus?
--- In ComputerVoltageSources@yahoogroups.com, "djbrow54" <davebr@...> wrote:
>
> --- In ComputerVoltageSources@yahoogroups.com, "John Loffink"
> <jloffink@> wrote:
> >
> > Do we have to pay for your DPO4000 too? That will be one expensive
> > piece of code. :-)
>
> You know, this scope is quite affordable. But no, I've just borrowed
> it for now.
>
> I did manage to interface the AtomPro24 I2C to a SAA1064 I2C to 7
> segment LED driver. I am sending 6 data bytes in a single message (7
> bytes total since it includes the device address byte) in 1.32 mS.
> The receiver is correctly ack'ing the packets and I am not getting any
> AtomPro24 errors.
>
> With interrupts enabled at 1 mS timer, I can see the packets jitter as
> the cycles are stretched by the interrupt service routine. It all
> seems to work quite well (as long as you used a scope to figure out
> the peculiarities of the i2cout command).
>
> The burst data transfer is 4545 bytes/second. Now that I have a known
> data stream, I will see if I can get an AVR to correctly receive it.
> I'm not going to do anything until my LCD arrives and I can verify
> functionality of my code. I don't want to tear the development system
> down yet. The LCD is scheduled to arrive Monday.
>
> Dave
>