Announcement

Collapse
No announcement yet.

Release 3 Beta 3 - version 1.3.0.0R10

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

  • Release 3 Beta 3 - version 1.3.0.0R10

    The current production firmware of xPico Wi-Fi is Release 2. With the upcoming Release 3, we're happy to provide a Beta for your testing.

    Please note: This code is Beta and not intended for production. A limited amount of testing has been done on it, but it has not gone through full regression testing. Use at your own risk.

    See also the attached supplementary Users Guide for the new features.
    Attached Files

  • #2
    So are you going to increase the length of the Monitor input message buffer from the 40 character limit. Did you make allowance for Monitor scan intervals smaller than 1 scan/s

    Comment


    • #3
      Originally posted by linktek View Post
      So are you going to increase the length of the Monitor input message buffer from the 40 character limit. Did you make allowance for Monitor scan intervals smaller than 1 scan/s
      Those parameters are not going to change in Release 3. We're still evaluating what the performance hit of that would be. Because the Monitor application uses buffers for the messages, it chews up memory and that needs to be balanced with the other needs of the platform.

      The Mux, on the other hand, streams data from the serial port to a web application, so you can send large amounts of data without taking up valuable RAM space.

      Comment


      • #4
        Originally posted by mariano View Post
        Those parameters are not going to change in Release 3. We're still evaluating what the performance hit of that would be. Because the Monitor application uses buffers for the messages, it chews up memory and that needs to be balanced with the other needs of the platform.

        The Mux, on the other hand, streams data from the serial port to a web application, so you can send large amounts of data without taking up valuable RAM space.
        Thanks for the feedback. The mux came a little too late so we had to make do with the Monitor. I did however have a quick look at the mux documentation looks kinda complicated. I was not expecting a command protocol. Does the mux realy need a command handshake protocol?

        Well as far as the Monitor is concerned, lets hope for the best.

        Comment


        • #5
          The Mux is more of an API on the serial port. The purpose is to be able to have multiple network streams share just one serial port. For example, you could be listening on one TCP port while also making an outbound connection to a different server, and each TCP connection gets different data.

          So the way to accomplish that is to give the attached MCU an API that it can use to control which TCP stream can pass/receive data from the serial port. The handshake is there for the MCU to know when (and how much) data can be streamed.

          I hope the Monitor works for you! Monitor is also a great application and easy to use (no MCU involvement) if it does what you need it to do.

          Comment


          • #6
            Are there plans to implement UDP communications? It works fine on the serial/Ethernet xPico module.

            Comment


            • #7
              UDP tunnel is a feature that's on our list (as you mention, we have other products that support it), but it's not there yet.

              To discuss the future availability of new features you should contact your local Lantronix sales person. If you don't know who that is, you can email [email protected] to find out who that is.

              Mariano

              Comment

              Working...
              X