Re: Do shell script to dial a number (again) Missing enter input....
Re: Do shell script to dial a number (again) Missing enter input....
- Subject: Re: Do shell script to dial a number (again) Missing enter input....
- From: Jean-Baptiste LE STANG <email@hidden>
- Date: Wed, 29 Dec 2004 21:29:22 +0100
Maybe you can use Smile. If you type 'serial ports' in smile you'll
have something like : {{9, "/dev/cu.modem", "modem"}, {10, "en0", ""},
{10, "en1", ""}}
So I think you can talk to the modem, you'll find more detail here :
<http://www.satimage.fr/software/en/rs.html>
++ Jean-Baptiste
Le 29 déc. 04, à 20:51, Bernardo Hoehl a écrit :
Hi List,
I was just experimenting an app. called ZTerm.
I open one MacOS's Terminal Window side by side with ZTerm.
As I type the string echo "ATDT5551212" > /dev/cu.modem on terminal
window, I notice that the "ATDT5551212" apears on the Zterm window.
That means that my modem is listening to the echo comand. Right?
Then I switch to Zterm window, and hit "enter". I mean just enter, not
the whole string.
Then my modem dials the number.
I have tried a few ways of inputing the "enter" character via
terminal, but none of them worked, yet.
Most of the time Zterm just shifts to one line down, instead of
inputing the enter command to the modem. I believe that the modem is
not receiving the enter as enter, but as another input.
I believe that what I need is to find out a way of inputing the enter
inside this string:
"ATDT5551212"
Question:
What other ways can I input the enter command to the modem? Some crazy
shell script?
Thanks,
BErnardo
===============================
On 12 Dec, 2004, at 7:05 PM, Doug McNutt wrote:
While messing around with a USB chip I discovered that it was easy,
in a BBEdit worksheet, to
echo "Testing" > /dev/their_driver
Which passed characters to the device which I could observe on an
oscilloscope.
I tried:
echo "ATDT5551212" > /dev/cu.modem # which did nothing
echo "ATDT5551212" > /dev/tty.modem # which returned "device is busy"
I then turned off the FAX option, which was active for no good
reason, and;
echo "ATDT5551212" > /dev/tty.modem # no longer returns an error
But I didn't get any audio indicating that the modem responded. Now I
have no idea if this sawtooth G4 even has a working modem in it but
the idea may be worth some more thought or other insight from someone
familiar with serial devices under BSD.
It's amusing that in Terminal these echos can cause a hang that I
don't yet understand. It's seems to be expecting something like a
HERE document. Using
echo "ATDT5551212" > test.txt
cat test.txt > /dev/tty.modem # doesn't help.
-- --> There are 10 kinds of people: those who understand binary,
and those who don't <--
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list
(email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden