Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

For anyone Considering buying a Lanronix MSS-100 or other device from Lantronix

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • no2pencil
    replied
    Just to follow up on this thread with my resolution, it was a cabling issue. I currently have WAFFLE working on DOS taking telnet OR dialup. Currently working on getting multiple com ports configured.

    Thank you (SkydivinGir)SO MUCH for your picture example walkthroughs of configuration for the LANTRONIX MSS 100

    Leave a comment:


  • salamontagne
    replied
    Ive gotten back into connecting the Lantronix MSS-100 and have written a sorta-user friendly HOW-TO here:

    http://www.vcfed.org/forum/showthrea...-automatically

    Happy BBSing!

    Leave a comment:


  • SkydivinGirl
    replied
    It sounds like you've done about everything that you can. I'd be happy to test it for you if you like but it wouldn't be worth the cost by the time you sent it here and I sent it back. Probably best to pick up another one.

    Good luck,

    Heather

    Leave a comment:


  • no2pencil
    replied
    Originally posted by SkydivinGirl View Post
    Someone on Lemon64 made a guide for the MSS-100 configuration. There are also links in the post to configuration settings that I use. They will probably answer all your questions.

    http://www.lemon64.com/forum/viewtop...577bc89e3c5ae8

    Good luck! Feel free to send me a PM if you have any other questions.

    Heather
    For the last 2 months or so, I've been messing with this MSS100 on the weekends & getting no where. I've followed that walkthrough you suggested, actually had done so previously, prior to posting. I don't understand why I can't get any data across the serial connection. I am using multiple cables, as I previously stated, all of which give me no results. I have reviewed numerous documents on configuring the MSS100 device, I've reset it to factory defaults, gone through the configuration, & am using multiple computers & multiple cables that I can use other serial devices such as modems without any issue. At what point is it safe to assume this thing is defective, & I wind up dumping more money into another one?

    Currently I have a USB->Serial adapter on Linux, I've used minicom, syncterm, & cu to attempt to connect, each time power cycling the lantronics & re-configuring the USB->Serial adapter to avoid any configuration or lock-creep.

    Local> show port

    Port 1: Username: Port_1 Physical Port 1 (Idle)
    Char Size/Stop Bits: 8/1 Baud Rate: 9600
    Flow Ctrl: None Session Limit: 4
    Parity: None Modem Control: None
    Access: Remote Break Ctrl: Remote
    Local Switch: None
    Forward: None Backward: None
    Port name: Port_1 Terminal Type: None
    Autostart char(s): --/-- Datasend char(s): --/--
    Save chars (AS/DS): none/none Timer: (none)
    Dedicated Service: TCP: 192.168.1.131

    Characteristics: Autobaud DSR Logout Telnet Pad Dtrwait
    MdmEmulate

    Sessions: 0 Current Session: None
    Input/Output Flow Ctrl: N/N DSR/DTR/CTS/RTS/CD: N/N/N/Y/N

    Seconds Since Zeroed: 208 Framing Errors: 0
    Accesses Local/Rem: 0/0 Parity Errors: 0
    Flow Control Violations: 0 Overrun Errors: 0
    Bytes Input: 0 Bytes Output: 0
    Input Flow On/Off: 0/ 0 Output Flow On/Off: 0/ 0

    I am initializing on Linux with :
    stty -F /dev/ttyUSB0 9600 -cstopb -ixon -ixoff -crtscts -parenb echo
    Reviewing with stty -a -F /dev/ttyUSB0 gives the following :

    speed 9600 baud; rows 0 columns 0; line = 0;
    intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
    eol2 = <undef>; switch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
    werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 1;
    -parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal crtscts
    ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ioff
    -iuclc -ixany -imaxbel -iutf8
    -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel n10 cr0 tab0 bs0 vt0 ff0
    -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprnt
    -echoctl -echoke

    The reason that I'm using Linux is this gives me the most troubleshooting information, & the most control over the device. The DOS machine that I intend to use this on leaves me blind, only wondering why I get init failed back. I have yet to find a way to "initialize" the mss100 as a modem, & successfully issue AT commands to it. I'm kind of at my wits end with this... as the serial port is giving me nothing out, yet the tcp/ip side has been working fine from day one. It's incredibly frustrating as nothing I'm doing is giving me any indication of life (other than RING when telnet in, & sending ATA does nothing), despite following walkthroughs of others getting it to work. However, of the walkthroughs I'm following, these people are using 8bit Atari/C64 machines, & not 16bit DOS. Does this matter for RS232? I would think not, but what about the pinouts? Just so many inconsistencies, & all I know is that it's not communicating.

    Just to add to the cable confusion :

    http://www.lantronix.com/wp-content/...pdf/MSS_UG.pdf

    6: Troubleshooting
    --The MSS completes its power-up and boot procedures, but there's no noticeable serial activity.
    --Check the terminal setup and the physical connections, including the cable pinouts (see Pinouts). Try another serial device or cable, or cycle power on the MSS.

    Then under section 7 is the pinout diagrams. I'm trying to compare those pinouts vs what would be in a generic null modem cable referencing here : http://www.tldp.org/HOWTO/Serial-HOWTO-19.html
    Last edited by no2pencil; November 22, 2015, 02:14 PM.

    Leave a comment:


  • IBM Portable PC
    replied
    Originally posted by tingo View Post
    If the usb serial port is ttyUSB0 on your Linux machine, you need a line like this in DOSbox config
    Code:
    serial1=directserial realport:ttyUSB0
    HTH
    This is a little off-thread, however DOSBox cannot see the DCD transitions. The serial port works, as per your setup which I already had, however it appears the DCD register is not emulated by DOSBox.

    Leave a comment:


  • tingo
    replied
    If the usb serial port is ttyUSB0 on your Linux machine, you need a line like this in DOSbox config
    Code:
    serial1=directserial realport:ttyUSB0
    HTH

    Leave a comment:


  • IBM Portable PC
    replied
    Originally posted by IBM Portable PC View Post
    In Linux, has anyone enjoyed success with reading DCD status from a USB to RS232 tty port?

    Specifically, I'm running the Probe (by datafile) scanner (radio) automation DOS app in DOSBox and I'm trying to extend DCD status from a terminal server, having given up on USB to serial adaptors.
    Okay, after trying several USB to RS232 adaptors, I finally tried a second Prolithic PL2303 device and with:

    pi@raspberrypi ~ $ statserial /dev/ttyUSB0

    I can see a DCD transition change:

    Device: /dev/ttyUSB0

    Signal Pin Pin Direction Status Full
    Name (25) (9) (computer) Name
    ----- --- --- --------- ------ -----
    FG 1 - - - Frame Ground
    TxD 2 3 out - Transmit Data
    RxD 3 2 in - Receive Data
    RTS 4 7 out 0 Request To Send
    CTS 5 8 in 1 Clear To Send
    DSR 6 6 in 1 Data Set Ready
    GND 7 5 - - Signal Ground
    DCD 8 1 in 1 Data Carrier Detect
    DTR 20 4 out 1 Data Terminal Ready
    RI 22 9 in 0 Ring Indicator

    The other adaptors included a Lindy branded DB25 cable and a Keyspan box.

    Now to work out how to get this transition into DOSBox

    Leave a comment:


  • IBM Portable PC
    replied
    In Linux, has anyone enjoyed success with reading DCD status from a USB to RS232 tty port?

    Specifically, I'm running the Probe (by datafile) scanner (radio) automation DOS app in DOSBox and I'm trying to extend DCD status from a terminal server, having given up on USB to serial adaptors.
    Last edited by IBM Portable PC; October 30, 2015, 11:15 PM.

    Leave a comment:


  • no2pencil
    replied
    Thank you for your reply. That's one of the guides I've been using, the one with the red circles. I think at this point I'll issue a factory reset (again) to remove any assumptions, & just start over from the beginning.

    Leave a comment:


  • SkydivinGirl
    replied
    Someone on Lemon64 made a guide for the MSS-100 configuration. There are also links in the post to configuration settings that I use. They will probably answer all your questions.

    http://www.lemon64.com/forum/viewtop...577bc89e3c5ae8

    Good luck! Feel free to send me a PM if you have any other questions.

    Heather

    Leave a comment:


  • no2pencil
    replied
    Originally posted by salamontagne View Post
    Thankfully, i was able to get mine to not only "dial out" but also to allow me to "dial in" to my bbs when i had it setup.

    These devices are quite difficult, so be patient
    Can you review what all you did to get your Lantronix working?

    For some time now I've been fighting with a Lantronix MSS100 that I bought off eBay. To go over the list, I've done the following :
    Manually set the IP, disabled DHCP
    Verify ping to the device
    Login via DeviceIP port 7000
    set priv, change primary port to 23
    Can telnet to device port 2001, 3001, & 23 (also 7000 for admin)
    Can access device via port 80 with web browser
    Set Serial Port Settings 9600 8,1,none,dynamic,none
    Check Box enabled : DSR Logout, DTR Wait, Modem Emulation, all other settings empty.
    Local Switch, Forward Switch, Backward Switch : All none
    Break Control None
    AutoStart with Chars unchecked, no auto start characters are set.

    The device sits in "IDLE" & I can attempt to dial by telnet to the device, if refreshed the status shows "Job Service" until the attempt times out. If I have BBS software running, or ProComm in host mode, I can see (as per Lantronix documentation) the five "RING" attempts. However sending ATA to the request does nothing. From a client side, using ProComm if I attempt to Dial "ATDT 192.168.1.134:23" which is another local pc with running synchronet, I see nothing on either PC. I've initializing with a basic string such as AT&F&C1&D2, as well as many, many other combinations like AT&S0=0&V0&E1&X0 as per documentation I've looked at on line.

    As far as cables, I have 2 serial cables, a null modem cable, & a gender changer. The lantronix has a male DB25, connected to the gender changer, connected to the serial port DB 25 to DB 9 to the PC &/or introduced the DB9 to DB9 null modem cable. One of my serial cables seems to also be a null modem cable, as I get different results from each, which can be duplicated by adding the null modem cable (if that makes sense).

    Is there anything obvious that I'm missing here? Why can't I get the device to work as a client or a server? Do I need to look into something else? I've tried switching the com port settings in BIOS, as well as an I/O card with a com port. Seems nothing is working in either direction.

    Leave a comment:


  • salamontagne
    replied
    I'm unfamiliar with the uds-10. However, on the MSS-100, i had to change the settings via ethernet connection. The MSS-100
    had a nice internal web server that allowed me to alter it to everything I needed. If the device is getting an IP (check your router) type it in a browser window (just the IP, no ort)

    Are you trying to use it to telnet online bbs from a dos or other vintage machine? The MSS-100 might be a better fit. Thankfully, i was able to get mine to not only "dial out" but also to allow me to "dial in" to my bbs when i had it setup.

    These devices are quite difficult, so be patient

    Leave a comment:


  • Back2skooldaze
    replied
    Hi please can someone help me? I have a lantronix uds-10 and i have this connected to a winxp laptop via a lantronix 500-163 serial cable.I can open hyper terminal and power the lantronix on at the same time and hold down x to get to the setup mode.I can do telnet configuration to the setup mode on any pc on the network and i can web configuration too!
    When connected in hyper terminal i can type AT and i get OK as a reply and i can type ATDT and go in to monitor mode ***nodeset 2.0*** and in there i can type PI 192.168.0.1 which is my router and it pings back.I can ping all my devices on the network BUT i can't ping back the lantronix ip address? If i try i type ATDT 192.168.0.2 and i get Unreachable??? If i try to type a bbs ip address i type ATDT 173.80.198.175:23 and then i get No Carrier?
    I have set the lantronix up with all kinds of settings and i always get No Carrier? If i change the connect mode to anything other than D6 i don't get anything on the screen and i can't type anything in hyper terminal so i know i must have connect mode set to D6 which is Full Vebrose with Character Response! but i still get No Carrier?

    I have had 2 emails back from lantronix giving me some settings and instructions but nothing will let me dial out to a bbs site? I always get No Carrier?

    If someone can help me get past this issue of No Carrier i am good to go as i am able to communicate to the lantronix from hyper terminal but can't ping the ip address but if i go in to my router and ping from there i can get a ping back from the lantronix?
    So something between the lantronix and my winxp laptop is stopping me from dialing out as i have No Carrier? all other commands like the AT and ATDT all work ok?

    Leave a comment:


  • MikeS
    replied
    Yeah, between cabling issues and AT commands these things can be tricky, but I'd be very surprised if it couldn't answer an incoming Telnet "call"; that'd make it pretty useless as an end-to-end RS-232 over IP 'replacement'.

    I haven't used a Lantronix, but I have used software that effectively does the same on a PC and it took a while to sort out the cabling and configuration issues.

    Assuming that like most people you bought these used off eBay, I'd say that their tech support is actually unusually good for such an old product...

    Leave a comment:


  • salamontagne
    replied
    Update - I've got egg on my face and was completely wrong. These do, in no way require software. Ive been talking it over with tech support (whom is being very patient with me, and i'd recommend hands-down)

    Sadly, The mss-100 is not fully geared to serve a bbs. In case anyone is trying todo the same, I'll keep ya'll update on my adventures. The biggest thing is configureing the communications software to "release" control over the port. The command for this is "ATC LOGOUT" after which it will wait for a telnet session (use the command 'CHANGE TELNETDEST SERIAL' while you are logged into the telnet port 7000)

    Below is the email responses Ive gotten on the matter:

    Hi *,

    If you are getting a login prompt, it is probably because you telnetted to port 23. To telnet to the serial port over the network, you need to connect to the IP address and port 2001. In modem emulation mode, the MSS should then send a RING out the serial port. The attached serial device would then reply with an ATA and the MSS would complete the connection.

    To set up the MSS to send the RING, you need to enter the AT command ATS0=0 (which turns autoanswer off). You should also issue an ATV1 to assure that the result code is text.

    Note that we just receive the connection and have no control over the application making the telnet connection.

    Regards,

    Michael Lyon
    LANTRONIX
    Senior Technical Support Engineer
    167 Technology Drive, Irvine, CA 92618

    Hi *,

    The appropriate setting for the port is Dynamic. This allows both incoming and outgoing connections. But not at the same time.

    From a default configuration, the only thing you need to enable on the port is:

    change modem emulation enable
    change autostart character "A"

    You do not need to enable autostart, that is implied in the modem emulation setting.

    Now, once modem emulation is enabled, it uses the autostart character to put the serial port into command mode. This is the equivalent to getting the Local prompt on the serial port when you are not using modem emulation. In that state, the port is in "Local Mode". In that mode, it is awaiting a connection command and will not allow incoming IP connections.

    Once it is in Local Mode, it needs to go back to Idle before it will accept incoming connections from the network. There are a few ways to do this.

    One is for the serial device to toggle its DTR pin, which toggles our DSR pin. This is the normal way a modem is reset using hardware lines.

    Another is to set an idle timer and enable it on the serial port. This will automatically log out the session after a set amount of time. The commands for this are:

    change inactive timer 1
    change inactive logout enable

    The third is to issue an AT command of "ATC logout" from the serial side to reset the port.

    It is also important to look at the wiring information on page 5-10 of the User Guide. Since the MSS is a DTE device, its CD pin is outgoing. In order to mimic a DCE serial port as closely as possible, the incoming CD functionality is mapped to the DSR pin. This requires wiring changes from a typical null modem cable.

    Let me close with this. The MSS is the first product from us, and perhaps any manufacturer to implement modem emulation on a serial device server. It was added a short while after the product was originally released 13 years ago. Given that modems are DCE devices, there is a cabling factor to deal with. But wiring it as recommended will allow it to behave, from a wiring perspective, more like a DCE modem serial port.

    That being said, for future reference, we do have a couple of products that are much more suited for modem replacement. The UDS1100 and EDS1100 have DB-25 DCE serial ports, just like a modem. In addition, they both have much more developed modem emulation functions, as they were designed with it in mind from the start. In addition, both are considerably less expensive than the MSS100. The UDS1100 is the low cost alternative (MSRP around $150); while the EDS1100 is more powerfull and feature rich, more on par with and even superior in many ways to the MSS100, while still coming in a lower price.

    You may want to look into those devices for any future projects.

    In the mean time, let's see if we can get this setup running.

    One last thing. I still do not have a completely clear picture of the whole setup. Do you have the physical setup diagrammed or flow charted in some way, so I can get a better understanding of what is talking to what and what they are expecting to see and do?

    Regards,

    Michael Lyon
    LANTRONIX
    Senior Technical Support Engineer
    167 Technology Drive, Irvine, CA 92618
    Phone: 800-422-7044 or 949-453-7198

    Leave a comment:

Working...
X