Announcement

Collapse

Forum Rules and 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.


Rule 1: 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.


Rule 2: 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.



Rule 3: 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.


Rule 4: "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.

Rule 5: 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

    #16
    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.

    Comment


      #17
      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

      Comment


        #18
        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!
        -------------------------------------------------------------------------------------------------------------
        Currently Looking for Samsung Sens Pro Laptop's (500, 520,800,820) and accessories, specifically a docking station.

        Comment


          #19
          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

          Comment

          Working...
          X