Using port other than ttyAMA0 for console about raspiarduino HOT 6 OPEN

I'm still studying this code myself. @me-no-dev is the master of the code. I looked at the TTY class and was surprised to see that the constructor of it expects a "numeric" ... so creating an instance of it with "17" will open /dev/tty17 ... great ... but if we have a TTY called /dev/ttySC0, we can't seem to use TTY!! That seems a trifle odd.

from raspiarduino.

The tty lib is actually to control the console tty that you see when you plug in a monitor/tv. With it you can write to it like you are using a keyboard

from raspiarduino.

I see, and thanks, both for creating a cool project, and for replying.

So as tty lib exposes almost the same interface as serial, i suppose i
could just create another serial port using tty as a base, eg
with termios???

Would be good if we could generalise it to use say ttyUSB0 etc as well, so
that Arduino apps could use whatever serial ports Linux knows about...

Ill have a play

BTW I see other forks have taken your project forward, are you planning on
merging those?

On Wednesday, September 7, 2016, Me No Dev [email protected] wrote:

The tty lib is actually to control the console tty that you see when you
plug in a monitor/tv. With it you can write to it like you are using a
keyboard

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#51 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGQxBPam2gKlm1aZGU0IMQUghQUs1wCLks5qnpaXgaJpZM4J1_JW
.

from raspiarduino.

Thanks Neil, thats sort of what im puzzling over, it looks like it should
be possible to use termios instead of accessing the hardware directly , but
i dont know enough about it yet to be sure...

And thanks for your books, esp the ESP8266

On Tuesday, September 6, 2016, Neil Kolban [email protected] wrote:

I'm still studying this code myself. @me-no-dev
https://github.com/me-no-dev is the master of the code. I looked at the
TTY class and was surprised to see that the constructor of it expects a
"numeric" ... so creating an instance of it with "17" will open /dev/tty17
... great ... but if we have a TTY called /dev/ttySC0, we can't seem to use
TTY!! That seems a trifle odd.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#51 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGQxBH_QDHfc197Wv6a7_oV8T-dYiawdks5qnbpNgaJpZM4J1_JW
.

from raspiarduino.

As i am currently employed by Espressif I have little time to work on the pi :) i don't even have pi 3 yet. I accept PRs but none have been sent.

from raspiarduino.

I would advise you not use the tty lib but rather unload the kernel driver and find arduino lib for your i2c uart and use that to communicate. It will be all fast and good :)

from raspiarduino.