George, I am not having much luck. For some reason, the ZTE MF636 is connecting on /dev/ttyUSB0 through USB3. wvdial is running on /dev/ttyUSB3. I created minicom profiles for ttyUSB2 and ttyUSB1, identical except for the port.
I did not change any of the other settings:
# Machine-generated file - use "minicom -s" to change parameters.
pu port /dev/ttyUSB2
pu minit ~^M~AT^M
The usb2 profile connects:
A - Init string ......... ~^M~AT^M
B - Reset string ........
C - Dialing prefix #1.... ATDT
D - Dialing suffix #1.... ^M
E - Dialing prefix #2.... ATDP
F - Dialing suffix #2.... ^M
G - Dialing prefix #3.... ATX1DT
H - Dialing suffix #3.... ;X4D^M
I - Connect string ...... CONNECT
J - No connect strings .. NO CARRIER BUSY
NO DIALTONE VOICE
K - Hang-up string ...... ~~+++~~ATH^M
L - Dial cancel string .. ^M
M - Dial time ........... 45 Q - Auto bps detect ..... No
N - Delay before redial . 2 R - Modem has DCD line .. Yes
O - Number of tries ..... 10 S - Status line shows ... DTE speed
P - DTR drop time (0=no). 1 T - Multi-line untag .... No
It is not hung (CTRL-A Z works), but it will not accept any input or display any response.
Welcome to minicom 2.3
Compiled on Oct 24 2008, 06:37:44.
Press CTRL-A Z for help on special keys
The usb1 profile sits at 'Initializing Modem'.
I tried echoing "AT" to /dev/ttyUSB2 and USB1, and using the 'cp /dev/ttyUSBx myUSBx' command to capture the output. The echo command completes on both ports, but I see no response from the modem. Echoing to /dev/ttyUSB0 hangs the echo command. I wonder if I have to set up the USB2 port with the same specs as wvdial is using? I may need to do some USB Snooping under Windows to see how the 'official' software talks to the ZTE modem.