We have a lot of controllers working within TETRA radio networks.
The controllers on the PXA320 modules running WinCE5 make the connection via standard dial-up networking.
The connection procedure requires extra AT commands to tell the radio to start a PPP connection.
These commands are sent through a manual dial terminal. The terminal window pops up before dialing, according to
corresponding checkbox “Manual Dial (user supplies dial strings)” in the Port Setting tab.
But on the new T30 modules, that runs WinCE7, we stuck into a problem. After modem initialization the terminal window does not appear.
It seems that in the standard WinCE7 image Manual dial terminal is absent.
We tried to use extra commands field in the “Call Options” tab but unsuccessfully.
So how do we get the dial terminal back? May be there is a .cab file for it?
I am able to reproduce the problem here. It seems that Microsoft removed the terminal in later WinCe versions.
We are currently checking whether there is a way to re-activate this feature.
Meanwhile, can you give me details how your dial sequence must look like? Maybe there are workarounds to achieve the same without the terminal.
Actually, the sequence must contain a single mandatory command “ATO” to start up PPP connection.
When the modem receives this command it says “CONNECT 19200 etc.” and starts sending LCP packets and waits for a LCP response from PC.
Then, user must to close the terminal window and only after that a PPP driver on a PC-side starts negotiating with the modem.
Just supplying ATO in the extra commands field doesn’t give the same results.
May be there are some timeouts that have to be held or the dial terminal sends a “connected flag” up to PPP driver, I don’t know.
Please see Motorola notes about a PPP connection procedure in the attachment.
I might have found a solution using registry settings, but there is one thing you need to check for your modem:
After the dialing command ATO I cannot avoid that the Colibri transmits at least one digit 0-9. If your modem is capable of ignoring such a digit, then the following solution would work:
Use the following registry settings:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\Drivers\Unimodem]
"DevConfig"=hex:10,00,00,00,78,00,00,00,10,01,00,00,00,4b,00,00,00,00,08,00,00,\
00,00,00,00
[HKEY_LOCAL_MACHINE\Drivers\Unimodem\Settings]
"DialSuffix"=""
"Pulse"=""
"Reset"="ATZ<cr>"
"DialPrefix"="O<cr>"
"Tone"=""
"CallSetupFailTimeout"="AT<cr>"
"Blind_On"=""
"Blind_Off"=""
"Prefix"="AT"
"Terminator"="<cr>"
[HKEY_LOCAL_MACHINE\Drivers\Unimodem\Init]
; make sure to delete all registry entries in this key.
In the Phone Number dialog, delete country- and area code, and set the Phone Number to any digit, which will be transmitted after the ATO.
When starting the connection, configure Dial Properties → Dialing Patterns to “E” (all 3 fields)
The Colibri will output the following dialling sequence:
ATZ
AT
ATZ
AT
AT
ATO
0
Some comments on this:
ATZ resets the modem. This is also done with your previous manual dial sequence. Now we just do it more than once, which I assume should not harm.
AT is a general command to query the modem’s status, so it also shouldn’t harm. However we can change this to ATZ or anything else if required.
ATO starts the data connection, as per your modem’s datasheet.
The 0 in the end is the phone number which we cannot prevent. I hope your modem ignores this. We can prefix the number to turn it into a more complex command if it helps, such as ATE0.
You can test-drive this with your old Colibri configuration - just enter such a command in the terminal, after the ATO.
