Unfortunately we don’t have a modem utility like the one in QNX4 for QNX6.
What you can do is write your own utility by using the “modem_*()”
convenience functions. You can take a look at these functions at the
following location. http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/lib_ref/lib-m.h
tml
Unfortunately we don’t have a modem utility like the one in QNX4 for QNX6.
What you can do is write your own utility by using the “modem_*()”
convenience functions. You can take a look at these functions at the
following location. http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/lib_ref/lib-m.h
tml
Regards,
Dave B.
Just curious. People have been asking for modem for about 2 years now.
Why isn’t QNX porting this useful utility to QNX6?
I myself can’t comment on why the modem utility hasn’t been ported to QNX6.
I would recommend that anyone wanting this utility should speak to their
sales representative. This way we can get a feel for how many people want
to use the utility under QNX6.
Unfortunately we don’t have a modem utility like the one in QNX4 for
QNX6.
What you can do is write your own utility by using the “modem_*()”
convenience functions. You can take a look at these functions at the
following location.
Just curious. People have been asking for modem for about 2 years now.
Why isn’t QNX porting this useful utility to QNX6?
Because some of the functionality isn’t available, and it’s low in the
priority queue. The chat util and the modem_* functions can be used to
customize your own needs for modem control in the mean time. I find it hard
to believe that the community hasn’t haven’t ported/rewritten a version of
modem since it’s so useful (modem source is available).
Porting modem is not the real problem (been there done (most) of it), it is
using it with tinit that the hangup (haha) occurs. But, it is easy to use
chat, but that forces you to use tcp/ip/ppp etc. Some people were happy with
qtalk and qcp, which by the way are still supported, but appear to be a bit
fragile in 6.1. The only way I could get qcp to work to/from a 6.1 box was
to access it from a 4.25 box, it would not work 6.1 to 6.1 for some reason.
Just curious. People have been asking for modem for about 2 years now.
Why isn’t QNX porting this useful utility to QNX6?
Because some of the functionality isn’t available, and it’s low in the
priority queue. The chat util and the modem_* functions can be used to
customize your own needs for modem control in the mean time. I find it
hard
to believe that the community hasn’t haven’t ported/rewritten a version of
modem since it’s so useful (modem source is available).
Porting modem is not the real problem (been there done (most) of it), it
is
using it with tinit that the hangup (haha) occurs.
What does tinit have to do with it? One of the ‘features’ in QNX4 is that
you could ask for and recieve notification via proxy from the Dev.* w/o
having a current open fd to the device. It’s not quite that straightforward
in QNX6, since notications are removed on close, and keeping the open count
non zero causes other applications to fail (since someone else has the
serial port open) because they’re playing nice with each other.
But, it is easy to use
chat, but that forces you to use tcp/ip/ppp etc.
chat has nothing to do with tcp/ip/ppp. It’s a EXPECT/REPLY mechanism you
can run over any open fd.
Porting modem is not the real problem (been there done (most) of it), it
is
using it with tinit that the hangup (haha) occurs.
What does tinit have to do with it? One of the ‘features’ in QNX4 is that
you could ask for and recieve notification via proxy from the Dev.* w/o
having a current open fd to the device. It’s not quite that straightforward
in QNX6, since notications are removed on close, and keeping the open count
non zero causes other applications to fail (since someone else has the
serial port open) because they’re playing nice with each other.
Couldn’t the design of modem be changed so that it works by itself
(instead of in concert with tinit)? I.E. modem is always loaded,
watches the open count like tinit does and only works when it’s the
only program monitoring a serial port?
Couldn’t the design of modem be changed so that it works by itself
(instead of in concert with tinit)? I.E. modem is always loaded,
watches the open count like tinit does and only works when it’s the
only program monitoring a serial port?
The problem is that modem would have to keep the open count non-zero just to
get notification of pending data (or you could poll, but that’s not going to
be nice). If you ran modem on a serial port, waiting for incomming data,
you couldn’t use qtalk to interact with your modem at the same time - qtalk
would complain that someone has the serial port open, and rightly so.
My thoughts are to scrap modem (as most QNX4 users see it) and just make a
basic template to answer the modem on RING, and/or dial a number other can
customize to whatever their needs-> but then I ask myself… you know, chat
can do exactly that.