guides:virtual_modem:section_5
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
guides:virtual_modem:section_5 [2021-04-14 19:18] omolini [Supported Modem Commands] |
guides:virtual_modem:section_5 [2023-03-07 03:58] (current) omolini [Troubleshooting] |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| * [[Guides:Connecting Windows 3.1 to the Internet]] | * [[Guides:Connecting Windows 3.1 to the Internet]] | ||
| * [[Guides:Connecting Windows 9x to the Internet]] | * [[Guides:Connecting Windows 9x to the Internet]] | ||
| + | * [[Guides:Connecting Windows 2000 to the Internet]] | ||
| + | |||
| + | |||
| /* | /* | ||
| Line 29: | Line 32: | ||
| * Restart Raspberry and test the changes. After rebooting, VModem should automatically start up with system processes and start expecting connections on serial. | * Restart Raspberry and test the changes. After rebooting, VModem should automatically start up with system processes and start expecting connections on serial. | ||
| - | ===== Supported Modem Commands ===== | + | ---- |
| + | |||
| + | ===== Supported Commands ===== | ||
| + | |||
| + | * **HELP** or **?** Show quick reference | ||
| + | * **LOGIN** Start a new shell session on serial | ||
| + | * **SETUP** Change system settings, such as Wi-Fi settings, etc. | ||
| + | * **EXIT** Quit Virtual Modem | ||
| - | Hayes commands supported: | + | Functional Hayes commands: |
| + | * **AT** Tests Modem. Returns OK if successful | ||
| * **ATDn** Dial number, where n is a phone number | * **ATDn** Dial number, where n is a phone number | ||
| * **ATDTn** Dial number using touch tone | * **ATDTn** Dial number using touch tone | ||
| * **ATDPn** Dial number using pulse dialing | * **ATDPn** Dial number using pulse dialing | ||
| + | * Note! This command actually runs a shell script by the name of the phone number stored in the same path as vmodem. If you dial ATD1, Vmodem will run 1.sh in the same directory and pass control to it. Any response you receive will be coming from 1.sh. When the script ends, you will be returned back to VModem. | ||
| * **ATE** - Command echo to host | * **ATE** - Command echo to host | ||
| * **ATE0** Commands are not echoed | * **ATE0** Commands are not echoed | ||
| Line 42: | Line 54: | ||
| * **ATQ0** Modem returns result codes | * **ATQ0** Modem returns result codes | ||
| * **ATQ1** Quiet mode. Modem gives no result codes. | * **ATQ1** Quiet mode. Modem gives no result codes. | ||
| - | * ATV Result codes in numerical or verbose form | + | * **ATV** Result codes in numerical or verbose form |
| - | * ATV0 Returns the code in numerical form | + | * **ATV0** Returns the code in numerical form |
| - | * ATV1 Full-word result codes | + | * **ATV1** Full-word result codes |
| - | * ATX Extended result codes | + | * **ATX** Extended result codes |
| - | * ATX0 Disable extended result codes (Hayes Smartmodem 300 compatible result codes) | + | * **ATX0** Disable extended result codes (Hayes Smartmodem 300 compatible result codes) |
| - | * ATX1 Add connection speed to basic result codes (e.g. CONNECT 1200) | + | * **ATX1** Add connection speed to basic result codes (e.g. CONNECT 1200) |
| - | * ATX2 Add dial tone detection (preventing blind dial, and sometimes preventing ATO) | + | * **ATX2** Add dial tone detection (preventing blind dial, and sometimes preventing ATO) |
| - | * ATX3 Add busy signal detection | + | * **ATX3** Add busy signal detection |
| - | * ATX4 Add both busy signal and dial tone detection | + | * **ATX4** Add both busy signal and dial tone detection |
| - | * ATZ Reset modem | + | * **ATZ** Reset modem |
| - | * ATZn Restore stored profile n | + | * **ATZn ** Restore stored profile n |
| - | ==== Extended Modem Commands ==== | + | ==== Supported Extended Modem Commands ==== |
| - | * AT&Cn Carrier-detect | + | * **AT&Cn** Carrier-detect |
| - | * AT&C0 Force DCD signal active | + | * **AT&C0** Force DCD signal active |
| - | * AT&C1 DCD signal indicates true state of remote carrier signal | + | * **AT&C1** DCD signal indicates true state of remote carrier signal |
| + | * **AT&F** Restore factory settings | ||
| + | * **AT&Fn** Use profile n | ||
| ==== Faked Commands (does not perform any action, always returns OK) ==== | ==== Faked Commands (does not perform any action, always returns OK) ==== | ||
| - | * ATA - Answer | + | * **ATA** Answer |
| - | * ATH Hang up or pick-up. | + | * **ATH** Hang up or pick-up. |
| - | * H0 Go on-hook (Hang up) | + | * **ATH0** Go on-hook (Hang up) |
| - | * H1 Go off-hook | + | * **ATH1** Go off-hook |
| - | * ATM Speaker control | + | * **ATM** Speaker control |
| - | * M0 Speaker always off | + | * **ATM0** Speaker always off |
| - | * M1 Speaker on until carrier detected | + | * **ATM1** Speaker on until carrier detected |
| - | * M2 Speaker always on | + | * **ATM2** Speaker always on |
| - | * M3 Speaker on only while answering | + | * **ATM3** Speaker on only while answering |
| + | * **ATS** S Register settings | ||
| + | * For example, **ATS0=0** | ||
| + | * **AT&Dn** Data Terminal Ready settings | ||
| + | * **AT&D0** Modem ignores DTR | ||
| + | * **AT&D1** Go to command mode on ON-to-OFF DTR transition. | ||
| + | * **AT&D2** Hang up on DTR-drop and go to command mode | ||
| + | * **AT&D3** Reset (ATZ) on DTR-drop. Modem hangs up. | ||
| + | * **AT&K** DTE - MODEM Flow control | ||
| + | * **AT&K0** Local flow control off | ||
| + | * **AT&K1** Not used | ||
| + | * **AT&K2** Not used | ||
| + | * **AT&K3** RTS/CTS | ||
| + | * **AT&K4** XON/XOFF | ||
| + | * **AT&K5** Transparent XON/XOFF | ||
| + | * **AT&K6** RTS/CTS and XON/XOFF | ||
| + | * **AT&Sn** DSR Override | ||
| + | * **AT&S0** DSR will remain on at all times. | ||
| + | * **AT&S1** DSR will become active after answer tone has been detected and inactive after the carrier has been lost | ||
| + | ---- | ||
| ===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
| Line 83: | Line 116: | ||
| **After dialing in, system reports connected, but no network is available**\\ | **After dialing in, system reports connected, but no network is available**\\ | ||
| Make sure you have updated the network device in **vmodem.sh** to reflect the correct network interface. By default it is eth0. If you are using Raspberry on WIFI, you may need to change this to wlan0. | Make sure you have updated the network device in **vmodem.sh** to reflect the correct network interface. By default it is eth0. If you are using Raspberry on WIFI, you may need to change this to wlan0. | ||
| + | |||
| + | **Is there any way to get it work faster than 56k?**\\ | ||
| + | Your serial port hardware will govern the maximum speed you can do with Virtual Modem. Please note, that Virtual Modem is a dial-up simulator. The best dial-up modems only went up to 56 kbaud, that was on a good day. You can crank it up to do a little bit faster, but you're running into limitations on what your serial port hardware can do, and faster speeds are beyond the scope of support, as going beyond your hardware limits can cause other connectivity issues that are unrelated to the virtual modem. If you would like a faster speed, you might need to look into other solutions, as this is beyond the scope of this project. | ||
| + | |||
| + | **I am still having issues using your script on something else than a Raspberry Pi and Raspbian/Raspberry Pi OS**\\ | ||
| + | Unfortunately there is very little in terms of support with hardware and software combinations that I can offer. If it works for you, great. But if it doesn't, you will need to try the recommended hardware and software combination as highlighted in [[guides:virtual_modem:section_2|Section 2 - Shopping list]] and follow the instructions carefully in further sections. Unfortunately I cannot offer support with untested setups, because I will not have access to the same software or hardware as you do. And if I don't have the same hardware and software, I cannot replicate the issue in the same way as in your particular environment. If I can't replicate the issue, I'm unable to troubleshoot it and offer support. This is why we have recommended hardware and software, because it is tested known working. If you are able to replicate the issue with our recommended hardware and software, and are still having the same issue, feel free to contact us on Discord and I will be more than happy to assist. | ||
| **Other issues:** | **Other issues:** | ||
| Line 102: | Line 141: | ||
| * [[Guides:Virtual Modem:Section 3|Section 3 - Setting up Raspbian]] | * [[Guides:Virtual Modem:Section 3|Section 3 - Setting up Raspbian]] | ||
| * [[Guides:Virtual Modem:Section 4|Section 4 - Setting up Virtual Modem]] | * [[Guides:Virtual Modem:Section 4|Section 4 - Setting up Virtual Modem]] | ||
| - | * [[Guides:Virtual Modem:Section 5|Section 5 - Using Virtual Modem]] << You are here | + | * **[[Guides:Virtual Modem:Section 5|Section 5 - Using Virtual Modem]] << You are here** |
| + | |||
| + | * [[Guides:Connecting Windows 3.1 to the Internet]] | ||
| + | * [[Guides:Connecting Windows 9x to the Internet]] | ||
| + | * [[Guides:Connecting Windows 2000 to the Internet]] | ||
| ---- | ---- | ||
guides/virtual_modem/section_5.1618427911.txt.gz · Last modified: 2021-04-14 19:18 by omolini
Page Tools
