This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
guides:virtual_modem:section_4 [2020-12-22 04:19] omolini [Making Virtual Modem run at startup] |
guides:virtual_modem:section_4 [2021-04-11 20:16] omolini [Troubleshooting] |
||
---|---|---|---|
Line 42: | Line 42: | ||
* If you **do not** see ''/dev/ttyUSB0'' listed, you will need to update the script with the correct serial port. [[Guides:Virtual Modem:Section 4:Changing the serial port|Visit this page]] to update the script with the correct serial port. | * If you **do not** see ''/dev/ttyUSB0'' listed, you will need to update the script with the correct serial port. [[Guides:Virtual Modem:Section 4:Changing the serial port|Visit this page]] to update the script with the correct serial port. | ||
* If you **do** see ''/dev/ttyUSB0'' listed, continue on! | * If you **do** see ''/dev/ttyUSB0'' listed, continue on! | ||
+ | |||
+ | ==== Name of the ethernet interface ==== | ||
+ | For the sake of this tutorial we have used wired Ethernet. If you want to use Virtual Modem over a **wireless connection**, you will need to make sure it is properly set up, then update the script where it says ''etherp=eth0'' to say ''etherp=wlan0'' instead. To change the ethernet port in the vmodem.sh script, do the following: | ||
+ | - Run ''sudo nano /boot/vmodem/vmodem.sh'' | ||
+ | - Find the line ''etherp=eth0'' and change it to read ''etherp=wlan0''. | ||
+ | - Save file by pressing CTRL + o, then ENTER to save under the same name. | ||
+ | - Exit editor with CTRL + x. | ||
==== Network test on the Raspberry Pi ==== | ==== Network test on the Raspberry Pi ==== | ||
This would be a good time to test your network to eliminate any future headaches. | This would be a good time to test your network to eliminate any future headaches. | ||
- | Over SSH run the command: | + | * Over SSH run the command: ''ping ''''www.google.com'' |
- | <code bash> | + | * If you get ping replies, you are all set and the networking on your Raspberry Pi is working. |
- | ping www.google.com | + | |
- | </code> | + | |
* Press Ctrl + Z to stop ping. | * Press Ctrl + Z to stop ping. | ||
==== Initial VModem testing ==== | ==== Initial VModem testing ==== | ||
Line 63: | Line 68: | ||
</code> | </code> | ||
- | * If you see the READY text on the screen, the script is ready to accept connections. | + | * If you see the READY text on the Raspberry Pi, the script is ready to accept connections. |
- | * Now, go to your SERIAL terminal which should be hooked up to the Raspberry Pi's USB-to-serial adapter, and issue a few basic Hayes commands. Type "AT" and then press ENTER. You should receive an "OK" response. | + | * Now, open up a SERIAL terminal on the computer, and issue a few basic Hayes commands. First press ENTER a couple of times to sync up. Then type "AT" and then press ENTER. You should receive an "OK" response. |
- | * If you do not receive an OK response, you may need to sync up the connection by pressing ENTER a couple of times. Then try "AT" again followed by ENTER. | + | * If you receive a garbled or no response, the serial speed settings may be wrong. Make sure both computers are set to the same serial speed. |
- | * If you still do not receive a response, something may be wrong with the serial settings, or with the connection to the Raspberry Pi. | + | * If you do not receive any response, something may be wrong with the serial settings, or with the connection to the Raspberry Pi. Does the computer have a fast 16550 UART and a good USB-to-Serial adapter? (check section 2 of this tutorial). |
* Check to see that the vmodem.sh script is running and is receiving your keystrokes. If it working, it should echo your input from the serial terminal to the script's output. | * Check to see that the vmodem.sh script is running and is receiving your keystrokes. If it working, it should echo your input from the serial terminal to the script's output. | ||
+ | * If you're still not able to get it working, see the Troubleshooting section below. | ||
* On a serial terminal, this is the output you should be getting: | * On a serial terminal, this is the output you should be getting: | ||
{{ :guides:pics:vmodem_hyperterm.png?600 |}} | {{ :guides:pics:vmodem_hyperterm.png?600 |}} | ||
Line 73: | Line 79: | ||
{{ :guides:pics:vmodem_putty2.png |}} | {{ :guides:pics:vmodem_putty2.png |}} | ||
- | ===== Note about Wi-fi ===== | ||
- | If you wish to share a wireless connection on serial instead of a wired connection, you will need to edit the line "etherp=eth0" in vmodem.sh to "etherp=wlan0". | ||
===== Getting online ===== | ===== Getting online ===== | ||
Now you can proceed to check out the system specific guides on how to interface different vintage computers and devices with VModem. Once you are done, return back to this guide! | Now you can proceed to check out the system specific guides on how to interface different vintage computers and devices with VModem. Once you are done, return back to this guide! | ||
Line 80: | Line 84: | ||
* [[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 a Macintosh Classic to the Internet]] COMING SOON | * [[Guides:Connecting a Macintosh Classic to the Internet]] COMING SOON | ||
- | * [[Guides:Connecting a Digital VT100 compatible terminal to the Internet]] COMING SOON | + | * [[Guides:Connecting a Serial Terminal to the Internet]] COMING SOON |
+ | |||
+ | */ | ||
Make sure vmodem.sh is running on the Raspberry Pi first before attempting connection! | Make sure vmodem.sh is running on the Raspberry Pi first before attempting connection! | ||
Line 88: | Line 97: | ||
After you have **verified** that the VModem works properly on the console, and you have tested that you are able to connect to your network, you can make VModem run automatically as a background process after the Raspberry Pi is powered on. It will run as a background process so you won't see it's output, so it's highly recommended to thoroughly test the script first. | After you have **verified** that the VModem works properly on the console, and you have tested that you are able to connect to your network, you can make VModem run automatically as a background process after the Raspberry Pi is powered on. It will run as a background process so you won't see it's output, so it's highly recommended to thoroughly test the script first. | ||
- | * Edit the /etc/rc.local file. Make sure your /etc/rc.local has the following near the bottom, but **ABOVE the line that says "exit 0"**: | + | * Edit the **/etc/rc.local file**. Go to end of the file, and find the last line. It should be ''exit 0''. Now add the following lines **ABOVE** it. |
<code bash> | <code bash> | ||
# Start serial port and simulate a modem | # Start serial port and simulate a modem | ||
Line 99: | Line 108: | ||
* 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. | ||
- | ==== Further steps ==== | ||
- | You can now proceed to connect your retro machine to the Internet using Virtual modem. | ||
- | |||
- | * [[Guides:Connecting Windows 3.1 to the Internet]] | ||
- | * [[Guides:Connecting Windows 9x to the Internet]] | ||
- | * [[Guides:Connecting a Macintosh Classic to the Internet]] | COMING SOON | ||
- | * [[Guides:Connecting a Dumb/Smart Terminal to the Internet]] | COMING SOON | ||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
+ | |||
+ | **Cannot communicate on serial terminal with the vmodem script**\\ | ||
+ | After running the Virtual Modem script on the Raspberry Pi, and connecting it to your computer via the USB-to-Serial adapter and a null modem cable, you should be able to fire up a simple serial terminal on the computer and issue a few Hayes commands to ensure connectivity. Hayes commands are a common way to communicate with Modems, and by typing AT and pressing enter in the terminal, you should see an "OK" response. The vmodem script also recognizes other commands, such as HELP which should provide a short list of recognized commands). If you receive a garbled response after typing AT or HELP, your serial speed settings may not be the same on both ends. Make sure you have adjusted the communication speed to match. If you receive no response whatsoever, you might have a problem with the USB-to-Serial adapter or you may be using an older UART on your computer (see section 2 for more on this). If you're still unable to communicate with the VModem script, feel free to join our Discord channel (see bottom of page for link) for further support. Simple tutorials can only go so far... :) | ||
+ | |||
+ | |||
**After dialing in, system is disconnected immediately**\\ | **After dialing in, system is disconnected immediately**\\ | ||
Line 117: | Line 124: | ||
**Other issues:** | **Other issues:** | ||
* Some computers are not capable of operating at fast serial speeds. If you're unable to connect at 57600 or faster, try slower speeds, such as 9600 baud at first. Adjust both the vmodem.sh script and the computer to connect at only 9600 baud. If that works, work your way up to see where the limit for your specific computer is. | * Some computers are not capable of operating at fast serial speeds. If you're unable to connect at 57600 or faster, try slower speeds, such as 9600 baud at first. Adjust both the vmodem.sh script and the computer to connect at only 9600 baud. If that works, work your way up to see where the limit for your specific computer is. | ||
- | * If you run into any other issues, take a note of them and look for commonalities in any steps you've taken before this step. Open up the script vmodem.sh for editing to make sure the baud and serial port are properly set. If you're unable to figure it out, feel free to contact me (see bottom of page). | + | * If you run into any other issues, take a note of them and look for commonalities in any steps you've taken before this step. Open up the script vmodem.sh for editing to make sure the baud and serial port are properly set. If you're unable to figure it out, feel free to contact us at Discord. We have a channel specific for Virtual Modem support (see bottom of page). |
+ | |||
+ | ==== Related Topics ==== | ||
+ | * [[http://www.protoweb.org/|ProtoWeb - The 90's Internet Service Provider]] | Connect your retro computer to surf the 90's Web! | ||
+ | * [[Guides:List of Compatible Websites]] | List of classic websites that work with pre-2000 legacy web browsers. | ||
+ | * [[Guides:Virtual Modem:Script|Virtual Modem Source code and Coding Examples]] | These should help you get started with building new modules for Virtual Modem. | ||
+ | |||
+ | |||
+ | ---- | ||
==== Skip to previous sections ==== | ==== Skip to previous sections ==== | ||
Line 126: | Line 141: | ||
* [[Guides:Virtual Modem:Section 4|Section 4 - Setting up Virtual Modem]] << You are here | * [[Guides:Virtual Modem:Section 4|Section 4 - Setting up Virtual Modem]] << You are here | ||
- | ==== Related Topics ==== | ||
- | * [[http://www.protoweb.org/|ProtoWeb]] | Surf the 90's Internet ! | ||
- | * [[Guides:List of Compatible Websites]] | List of classic websites that work with pre-2000 legacy web browsers. | ||
- | * [[Guides:Virtual Modem:Script|Virtual Modem Source code and Coding Examples]] | These should help you get started with building new modules for Virtual Modem. | ||
---- | ---- | ||
- | Questions? Comments? [[:Contact Information|Contact Me!]] | + | ==== Get In Touch With Us! ==== |
+ | Share your thoughts and report bugs on Discord. \\ | ||
+ | [[https://discord.gg/4w6CpZ8|{{:images:social-discord.png?nolink|}}]] | ||
+ | |||
+ | {{tag>Guides Guides:Networking}} | ||