Thanks, it is working now!
> Op 4 jun. 2019, om 21:11 heeft Matthias Trute het volgende
> geschreven:
>
> Am Dienstag, den 04.06.2019, 18:39 + schrieb Jan Kromhout:
>> Hello,
>>
>> Ho do I set the parameters for the speed if the I2C to 400
>> kHz? Thanks for any help.
>>
>> : init_i2c (
Am Dienstag, den 04.06.2019, 18:39 + schrieb Jan Kromhout:
> Hello,
>
> Ho do I set the parameters for the speed if the I2C to 400
> kHz? Thanks for any help.
>
> : init_i2c ( --- )
> \ init at 100 kHz
> i2c.prescaler/1 #72 i2c.init
> ;
>
Did you check http://amforth.sourceforge.net/TG/r
Hello,
Ho do I set the parameters for the speed if the I2C to 400 kHz? Thanks for any
help.
: init_i2c ( --- )
\ init at 100 kHz
i2c.prescaler/1 #72 i2c.init
;
Thanks for any help.
Cheers,
Jan
___
Amforth-devel mailing list for http://amforth.sf.
Hi,
A general question.
When I won’t to write I should put a “0” behind the address.
Should I do it by hand, or are the words clever enough to do this?
My address => $38 = %0111000
After shifting => %111 = $70
Cheers,
Jan
Op 10 nov. 2018, om 21:23 heeft Tristan Williams
mailto:h...@tjnw
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 comman
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:
> Trista
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 2018-11-1
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 begin
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! m
Hello Erich,
The i2c scanner is seeing $38, should i still shift to $70?
Cheers
Jan
Verstuurd vanaf mijn iPad
> Op 9 nov. 2018 om 22:30 heeft Jan Kromhout via Amforth-devel
> het volgende geschreven:
>
> Thanks Erich,
>
> Do I need this to start every time I use I2C
>
> i2c.init.default
Thanks Erich,
Do I need this to start every time I use I2C
i2c.init.default
Cheers,
Jan
> Op 9 nov. 2018, om 20:56 heeft Erich Wälde het volgende
> geschreven:
>
> Hello Jan,
>
> your i2c address: "$38", is this the 7bit address? You might
> need to shift it by one position to "$70".
>
Hello Jan,
your i2c address: "$38", is this the 7bit address? You might
need to shift it by one position to "$70".
Just an idea.
Cheers,
Erich
Jan Kromhout writes:
> Hi,
>
> This is my first step on the I2C road.
> I have a Gravitech shield for the Arduino, that work well.
> The code is very si
Hi,
This is my first step on the I2C road.
I have a Gravitech shield for the Arduino, that work well.
The code is very simple, and I have translate it to Forth.
The display is not working.
I include the Forth code. What is wrong?
Thangs for any help.
Cheers,
Jan
\ Gravitech display, I2C Generic
Am Dienstag, den 31.01.2017, 08:51 + schrieb Tristan Williams:
> Hello Matthias,
>
> Thank you. >rx-buf is wonderful. I have high hopes of making the
> keypad appear as a subset of the keyboard so they can use exactly the
> same code.
>
> The PCF8574A + keypad + interrupt also seems to work w
Hello Matthias,
Thank you. >rx-buf is wonderful. I have high hopes of making the
keypad appear as a subset of the keyboard so they can use exactly the
same code.
The PCF8574A + keypad + interrupt also seems to work well. I
explicitly protected each of the other i2c devices on the bus from
being i
Am Samstag, den 28.01.2017, 10:46 + schrieb Tristan Williams:
> I have successfully written a couple of forth words keypad? and
> keypad
> that use i2c (PCF8574A) and an interrupt to tell me if/what key has
> been pressed on my keypad. This is currently completely independent
> of
> the keyboar
I have successfully written a couple of forth words keypad? and keypad
that use i2c (PCF8574A) and an interrupt to tell me if/what key has
been pressed on my keypad. This is currently completely independent of
the keyboard buffer. What I would like to do is to take the value that
would placed on th
Am Mittwoch, den 25.01.2017, 13:02 + schrieb Tristan Williams:
> I replaced my i2c files with those from the trunk r2209 and all of
> i2c.c! i2c.c@ i2c.n! i2c.n@ i2c.m!n@ give me what I was expecting.
I've essentially re-implemented the i2c words after release 6.3.
Maybe I should finish 6.4
I replaced my i2c files with those from the trunk r2209 and all of
i2c.c! i2c.c@ i2c.n! i2c.n@ i2c.m!n@ give me what I was expecting.
What I was doing incorrectly below I don't know but perhaps starting
from a completely fresh UNO (as I did above) was part of the
solution. Apologies, I will do th
Hello,
I am in the process of connecting a keypad to an i2c port expander
(PCF8574A) to an UNO and have run into the following problem. More
than likely the problem is my lack of understanding. Writing to the
port expander appears to be no problem. Reading from it using i2c.>n
results in the UNO h
20 matches
Mail list logo
