steptail.com

Does expecting the unexpected make the unexpected the expected?

User Tools

Site Tools


guides:virtual_modem:section_4

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
guides:virtual_modem:section_4 [2021-04-11 20:01]
omolini [Name of the ethernet interface]
guides:virtual_modem:section_4 [2021-04-14 18:56]
omolini [Skip to previous sections]
Line 68: 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 ​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 78: 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 111: Line 110:
  
 ===== 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 136: Line 140:
   * [[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]] << You are here   * [[Guides:​Virtual Modem:​Section 4|Section 4 - Setting up Virtual Modem]] << You are here
 +  * [[Guides:​Virtual Modem:​Section 5|Section 5 - Using Virtual Modem]]
  
 ---- ----
  
 ==== Get In Touch With Us! ==== ==== Get In Touch With Us! ====
-Share your thoughts and report bugs on Discord. \\+Get support, share your thoughts and report bugs on Discord. \\
 [[https://​discord.gg/​4w6CpZ8|{{:​images:​social-discord.png?​nolink|}}]] ​ [[https://​discord.gg/​4w6CpZ8|{{:​images:​social-discord.png?​nolink|}}]] ​
  
 {{tag>​Guides Guides:​Networking}} {{tag>​Guides Guides:​Networking}}
  
guides/virtual_modem/section_4.txt · Last modified: 2023-11-24 23:16 by omolini