Tristan,
I have tried that. No results. Monday I get an Logic Analyser so I can watch
the I2C bus. Hopefully can I figure out what is wrong.
Cheers,
Jan
> Op 10 nov. 2018, om 21:23 heeft Tristan Williams het
> volgende geschreven:
>
> Jan,
>
>> This device is need only one byte per
Jan,
> This device is need only one byte per command, so I have used i2c.c!.
> Do you ave a clou?
but it might be expecting two single bytes, one immediately after the other.
Try
Number digit 2 7SEG i2c.n!
Best wishes,
Tristan
On 10Nov18 17:27, Jan Kromhout via Amforth-devel wrote:
>
Hello Jan,
> The i2c scanner is seeing $38, should i still shift to $70?
Don't be afraid of just trying this. There is nothing that
breaks, if you happen to use a different i2c address.
So I dont' think so, but let me check
> | $ ls -l /dev/ttyUSB0
> | crw-rw 1 root dialout 188, 0
Hello Jan,
> Where can I download the software of the articles of Clock Works.
> The link https://wiki.forth-ev.de/doku.php/projects:clockworks ...
Thanks for reminding me, that there is a broken link in the
game. This one is better:
Hello,
Find the source!!
Cheers,
Jan
> Op 10 nov. 2018, om 16:26 heeft Jan Kromhout via Amforth-devel
> het volgende geschreven:
>
> Hello,
>
> Where can I download the software of the articles of Clock Works.
> The link https://wiki.forth-ev.de/doku.php/projects:clockworks
>
Tristan,
This is my simple code.
The address of the SA1064 is $38
I have checked with the arduino for save playing the frequency of the bus
should be less than 100 kHz.
When I translate the simple code of the arduino to amForth I get this, but no
results.
Even no results with deleting the
Jan,
Have a look at the source your-amforth/common/lib/hardware/i2c.frt
and the comments at the top of the file.
i2c.c! i2c.c@ i2c.n! i2c.n@ i2c.m!n@ already have the i2c.begin and
i2c.end within the respective word. I don't know the Gravitech shield
but if you are sending multiple bytes i2c.n!
