Support Engineering Group : OASIS Release Notes This page last changed on Nov 30, 2010 by kgomes. From Kent Headley
    #
    # Cawthron TASCAM OASIS3
    # Release Notes
    # 28 Oct 2010
    #

    ############################
    # ESD Handling Precautions
    ############################
    All of the OASIS3 hardware requires proper ESD handling at all times.
    The Persistor cards are particularly sensitive to static discharge.

    ##########################################################
    # Known Issue: Issuing "reset pico" from radio console
    ##########################################################

    If connected to an OASIS console through a radio link,
    issuing the "reset pico" command to restart OASIS will
    break the radio link. It will not be possible to restore
    contact until the hardware watchdog timer (WDT) expires.
    It takes about 30 minutes for the timer to expire, which
    restarts OASIS and runs the radio driver again.

    The next release of code (still in testing), implements a warning message to prompt the
    operator before disconnecting radio.

    ##########################################################
    # Known Issue: Missing line feeds in OASIS.CFG cause
    # OASIS app to fail on reboot, requiring hardware recovery
    ##########################################################

    An OASIS configuration file (OASIS.CFG) containing lines not terminated with a
    line feed character (0xA) will cause OASIS to fail on the next reboot.
    If this occurs, OASIS loads with a minimal set of drivers (UserIF, radio, OASIS).
    To recover, it is necessary to correct and re-install the file.

    This condition may occur in one of several ways:

    - text editors may be configured to terminate lines with CR (0x0D) only

    - terminal programs (e.g. HyperTerm) may remove line feeds if they they
      are configured to disable sending line feeds with line ends

    Lines may be terminated with CRLF or LF, but not CR only.

    To prevent this, the following practices are strongly recommended:

    - Review the configuration file in a hex editor before attempting to upload it.
      Ensure that it has CRLF (0xD 0xA) line terminators.
      Multiple CRLF pairs or LF characters are permitted, but each line must
      terminate in a line feed (0xA).

      In Notepad editor, files will appear to be on one long line and/or some lines will
      run together if the line feeds are missing. This is not a definitive test, however.
      XVI32 works well, and is available for free at

      http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm

    -  *ALWAYS* upload to a temporary file name (e.g. foo.cfg) and check it the file before using it
       Transferring the file using HyperTerm can cause this problem regardless of the editor. Terminal
       programs must be configured to enable sending line ends with line feeds.

    - Use the PicoDOS type command to display the file on the OASIS console. If the lines all run together,
      the file must be fixed and/or resent. If the file looks OK on the console (i.e., is does not appear to be one
      continuous line), it is OK to rename it to oasis.cfg
      and reboot.

    - The recommended method for transferring files is to use Motocross "Send Binary File" and the PicoDOS or OASIS "capture" command:
       - issue the capture command from OASIS prompt (preferred) or PicoDOS prompt.
       - use "Transfer>SendBinaryFile" from the Motocross menu and select the file to send (remember to use a temporary file name)
       - issue Motocross "Send Break" command to end the transfer (CTRL-C may also work)
      It is preferred to DISABLE line feeds when using Motocross; transfers work correctly and disabling prevents double prompts.
      Not all versions of Motocross include the required "Transfer>SendBinaryFile" menu item. Version 2.32 has it.
      Motocross does not support Y-Modem transfer.

    - It is possible to upload OASIS.CFG at the OASIS prompt or at the PicoDOS prompt. The following notes apply:

      Uploading using Hyperterm works OK from OASIS> prompt if the "Send Line ends with Line
      Feeds" is ENABLED. You may later want to disable it to prevent double OASIS prompts.

      Uploading using Hyperterm works OK from PicoDOS C:\> prompt if the "Send Line ends with
      Line Feeds" is DISABLED. It will work OK if ENABLED, but will cause double OASIS prompts.

      It is possible to upload using Hyperterm from the PicoDOS prompt with a 'yr' command.
      See note above on using reset pico via radio console.

    ######################  Summary ###########################
     - use dumb editors
     - check line ends (using a hex editor) before sending
     - use Motocross + capture from OASIS prompt
     - DISABLE "send line ends with line feeds" if using Motocross
     - ENABLE "send line feeds with line ends" if using HyperTerm
     - transfer to a temp file name
     - check line ends (type test) after sending
    ###########################################################

Document generated by Confluence on Feb 03, 2026 16:22