12-23-2014
Yes, you got it. There is an interface signal (called DCD, Data Carrier Detect, which is pin 8 on the 25-pin RS232) that tells the host at each end if the modulated carrier (telephone line signal) is lost.
Although your (RS232) interface is a virtual one within the USB driver, the functionality should be the same. My point is that there may be some programming instruction (AT command(s)) to tell each of the modems what they should do if they see carrier lost. I would expect them to notify the USB driver through the USB interface so that the USB driver (if it's the correct one) can tell the host O/S that the line has gone down.
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
hi all,
I have been trying to setup network on solaris10 from a long time but am unable to do so..
I tried it with the ethernet card i have(dfe -520tx) but since i was not able to find drivers for that particular device, i thought of using the usb mode to run network..
However am not able... (0 Replies)
Discussion started by: wrapster
0 Replies
2. AIX
Hello AIX Group Members,
I have two systems: (1) IBM pSeries 640, 7026-B80. (2) A 5-month old HP laptop with Windows Vista. It has no serial port and only has USB ports on it.
My question are: How can I use the laptop as the p640's terminal? How can I make the connection? What type of cable... (4 Replies)
Discussion started by: aixlover
4 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have PC with Linux OS RHEL3 and USB port is disabled from BIOS. BIOS access is protected using password. But, I have root access. Now, how can I enable USB port using root access? Is there any trick that I can do using root access that can enable USB port once my PC has booted up? (3 Replies)
Discussion started by: gydave
3 Replies
4. UNIX for Advanced & Expert Users
I want to watch the USB ports.
If any device is connected to the USB port I want to take the name of the device and
I want to log the device name. how to watch all the USB ports.
How to find the device is connected in which usb port. (1 Reply)
Discussion started by: ungalnanban
1 Replies
5. Ubuntu
Hi
I have to buy my selfe external case for hdd but I don't know whether my ubuntu linux, needs some driver to be able to work with this device or it has inside of itselfe this driver ?
rhx for help. (1 Reply)
Discussion started by: presul
1 Replies
6. Shell Programming and Scripting
Hi @all,
i am currently having a Problem:
I want to restart 2 USB Bluetooth Dongles from the shell at the same time. It is very important that they are restarted nearly simultaneously, so that their clocks are starting to run at the same time.
At the moment i am using a command called... (3 Replies)
Discussion started by: cabrix
3 Replies
7. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
8. Solaris
In ubuntu etopic i create this udev rules for prolink 3g usb modem:
SUBSYSTEM=="block",
SUBSYSTEM=="scsi",
ATTRS{idVendor}=="1e0e",
ATTRS{idProduct}=="f000",
ACTION=="add",
RUN+="/sbin/modprobe usbserial Vendor=0X1e0e Product=0Xf000"
After plugging the usb modem, ubuntu assigns the ports... (4 Replies)
Discussion started by: shamsat
4 Replies
9. Shell Programming and Scripting
Hi everybody! :)
I am a complete newbie. :D Is it possible to write a script (shell or python) to listen to usb port event and to notify me every time an usb storage key is plugged or ejected? I want it to echo the device to mount (eg. /dev/sdb).
I wrote an udev rule wich runs a script after... (1 Reply)
Discussion started by: manuhexadec
1 Replies
10. Linux
I have someone wanting to connect to the serial management port of a switch from a PC running CentOS6. The management port on the switch is apparently baud 9600, 8 data bits, 1 stop bit & no parity They have plugged in a cable to connect and the output from lsusb is:-Bus 001 Device 001: ID... (7 Replies)
Discussion started by: rbatte1
7 Replies
UHSO(4) BSD Kernel Interfaces Manual UHSO(4)
NAME
uhso -- Option N.V. Wireless WAN modem driver
SYNOPSIS
uhso* at uhub? port ?
HARDWARE
The uhso driver supports at least the following adapters:
GlobeSurfer HSUPA
GlobeSurfer iCON 7.2
GlobeTrotter Express 40x
GlobeTrotter Express HSUPA
GlobeTrotter HSUPA
GlobeTrotter Max HSDPA
GlobeTrotter Module 382
GlobeTrotter iCON 225
GlobeTrotter iCON 321
GlobeTrotter iCON 322
GlobeTrotter iCON 401
GlobeTrotter iCON 505
GlobeTrotter iCON EDGE
DESCRIPTION
The Option N.V. modems appear at first as a umass(4) device containing the Windows and MacOS drivers and, upon receipt of a SCSI "REZERO
UNIT" command, will detach from the USB bus and reattach as a Wireless WAN modem. Unless disabled by clearing the sysctl(8) variable
hw.uhso.autoswitch, the driver will handle that automatically.
The modems provide a number of IO channels spread over several USB interfaces which are mapped by function to a standard port number in each
driver instance. The defined channels are:
Channel Name Port
Control 0
Diagnostic 1
Diagnostic 2 2
Application 3
Application 2 4
GPS 5
GPS Control 6
PC Smartcard 7
Modem 8
MSD 9
Voice 10
Network 11
Apart from the Network port, which is attached as a network interface, the ports are attached as tty(4) devices using the port number as the
minor device number. In order to connect using pppd(8), the Modem tty should be used (eg /dev/ttyHS0.08).
The Network port provides a direct IPv4 interface, but before this can be used the modem needs to be placed in connected mode and network
settings subsequently retrieved using the proprietary "_OWANCALL" and "_OWANDATA" AT commands on the Control port.
Note that the Modem and Network ports should not be enabled at the same time for USB performance reasons.
FILES
/dev/ttyHS?.??
/dev/dtyHS?.??
/dev/ctyHS?.??
SEE ALSO
intro(4), netintro(4), tty(4), uhub(4), usb(4), ifconfig(8)
HISTORY
This driver originated as the hso module for FreeBSD written by Frederik Lindberg. It was rewritten for NetBSD, and to provide more complete
device support with information extracted from the hso driver for Linux provided by Option N.V.
The rewrite and this manual page by Iain Hibbert.
BSD
August 26, 2011 BSD