Shop OBEX P1 Docs P2 Docs Learn Events
Recommendations for a serial driver. — Parallax Forums

Recommendations for a serial driver.

jtilghmanjtilghman Posts: 67
edited 2013-07-17 17:24 in Propeller 1
I am using a wireless link to my quickstart and I would like to get some recommendarions on which serial driver in obex to use.

I would like one that will work at 115200 and I need to pass only what I type from a terminal. (EX: I type a W and all that gets sent across the wireless is W no CR, no LF no NULL just the W)

I also need this driver to work with PuTTY and/or the Parallax Serial Terminal.

I welcome all suggestions.

Thanks,
jt

Comments

  • prof_brainoprof_braino Posts: 4,313
    edited 2013-07-17 08:41
    jtilghman wrote: »
    PuTTY and/or the Parallax Serial Terminal.

    I welcome all suggestions.


    PST doesnt do everything as expected. Consider teraterm as your terminal program


    if you can use forth, it is easy just switch the pins and use the default driver in propforth. PM if you are interested
  • Duane DegnDuane Degn Posts: 10,588
    edited 2013-07-17 08:43
    Parallax Serial Terminal.spin (in Prop Tool library) should do what you're after. I use it alot with wireless communication between PC and Propeller over a pair of Wixel transceivers.

    Using Parallax Serial Terminal.exe, the enter key transmits a carriage return but pressing a character on the keyboard sends the character and only the character over the serial connection.

    The wireless aspect doesn't really matter in my programs. I used the same code if I'm communicating over a USB cable or a Wixel.

    Edit: I just now see Prof's post. I'm not sure what problems PST has. I haven't used TeraTerm myself so I'm not aware of the benefits. I know Parallax wants Propeller objects to use PST (both spin and exe) with its Gold Standard objects.
  • prof_brainoprof_braino Posts: 4,313
    edited 2013-07-17 12:09
    Duane Degn wrote: »
    Parallax Serial Terminal.spin (in Prop Tool library) should do what you're after.

    I'm not sure what problems PST has.

    If PST and PST.spin work for your needs, then you should use those.

    The issues I refer to may only be present when using propforth, so take it with a grain of salt. If I recall correctly:
    - PST has a separate user input line, most awkward when we need a terminal interface for forth
    - PST doesn't allow control over CR vs CR+LF
    - PST does not behave as a generic VT100 terminal.
    - Since PST is not a generic terminal, it is not so easy to use as an ANSI terminal display, with feature such as cursor placement, changing screen colors, font, bold, highlight, reverse, etc. These may work on PST, but (in my case) its easier just to use teraterm and be done with it.
    - PST does display the state of DTR and other hardware lines, which is cool. But this is rarely needed (in my case) so I only use PST when this ability is specifically called for.
    - I think there were a couple other issues that I dont recall at the moment. The bottom line was it was easier to use teraterm than try to make PST fit the need.

    In summary, PST does things in a specific way to meet things spin does in it own unique way. If you are doing things beyond that, or different than than, then another tool may be appropriate.
  • Duane DegnDuane Degn Posts: 10,588
    edited 2013-07-17 12:39
    If PST and PST.spin work for your needs, then you should use those.

    The issues I refer to may only be present when using propforth, so take it with a grain of salt. If I recall correctly:
    - PST has a separate user input line, most awkward when we need a terminal interface for forth
    - PST doesn't allow control over CR vs CR+LF
    - PST does not behave as a generic VT100 terminal.
    - Since PST is not a generic terminal, it is not so easy to use as an ANSI terminal display, with feature such as cursor placement, changing screen colors, font, bold, highlight, reverse, etc. These may work on PST, but (in my case) its easier just to use teraterm and be done with it.
    - PST does display the state of DTR and other hardware lines, which is cool. But this is rarely needed (in my case) so I only use PST when this ability is specifically called for.
    - I think there were a couple other issues that I dont recall at the moment. The bottom line was it was easier to use teraterm than try to make PST fit the need.

    In summary, PST does things in a specific way to meet things spin does in it own unique way. If you are doing things beyond that, or different than than, then another tool may be appropriate.

    Thanks for taking time to list these issues.

    I guess I've just gotten used to PST. I probably don't know enough about other terminal software to know what I'm missing.

    I don't think think there's a way to change the font characteristic (bold, color, etc.) in PST, but one can place the cursor wherever desired. As you mentioned the cursor placement is only for output, not input.
  • Cluso99Cluso99 Posts: 18,069
    edited 2013-07-17 17:24
    Depending on the buffer sizes you might require, FullDuplexSerial should fill your needs. I posted a version FullDuplexSerial_rr004 where you can change the buffer sizes quite simply form the default of 16 each for Tx and Rx. There is also a 4port serial object that can handle up to 4 serial ports in 1 cog. Check it out - there is some info in the source file about speed restrictions when using multiple ports.
Sign In or Register to comment.