S30 not saving communication settings

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #5463
    Daryll
    Member
    • Total Post: 6
    • Newbie
    • β˜…

    Hi All… my first visit to these forums, maybe I’ll get help quicker here than from Wyse..
    πŸ˜‰

    We currently use a variety of 3125’s, 3150’s and S30’s to connect to an application via ethernet using the Thin Clients terminal emulation facilities.

    This application collects weight data and so an electronic weigh balance is connected to the Thin Client via the COM port.

    Our problem is that we’ve recently received a new batch of S30’s, (which has a different firmware to the last batch, so we cannot copy our standard image), and I can’t figure out how to get them to save the communication settings required by the electronic weigh balances.

    In the PowerTerm setup I have specified they use the AUX settings, and then gone into a session, the communication menu and “modify AUX”, and set the communications to 4800 baud, 7 bits, odd parity, 1 stop bit (our company standard settings), click OK, then go to “File” and “save session”, then exit.

    If I then go back into that session and back to the communication settings, they have reverted to the default 9600, 8, none etc…

    … so it looks like the Thin Client isn’t saving the session settings….

    Anyone had this before, or any ideas??

    thanks,

    Daryll.

    #16989
    ConfGen
    Keymaster
    • Total Post: 11417
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Have you tried to image the new S30 (at least one of them) with your old company image? Does that work?

    CG

    #16995
    Daryll
    Member
    • Total Post: 6
    • Newbie
    • β˜…

    Hi ConfGen… yes, our IT Dept have tried, but apparently because the new batch of S30s are a new firmware, they won’t accept images from the older S30s.

    πŸ˜•

    #17023
    ConfGen
    Keymaster
    • Total Post: 11417
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Strange, how old is the “old image”? What build number?

    CG

    #17060
    Daryll
    Member
    • Total Post: 6
    • Newbie
    • β˜…

    I’m not sure which build is on which client… I’ll have to wait until the IT guy who deals with the clients gets back off sick leave.

    I do know that our old S30’s are CE v5.0, but the new batch are CE v6.0, would this be the problem?

    Edit:

    I’ve managed to get my hands on old and new S30s…

    The old one is:
    Version 5.0 WYSE FR1 (Build 541)

    The Addon is Ericom Terminal Emulator v8.1.0 (build 25)

    The new one is:
    Version 6.0 WYSE WFR2 (build 656)

    The Addon is Ericom PowerTerm Terminal Emulator V9.1.0 (Build 33)

    Daryll.

    #17064
    ConfGen
    Keymaster
    • Total Post: 11417
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Yes, that looks like the root cause.
    You should file a call with Wyse as that seems to be bug in the latest Ericom or CE build.

    CG

    #17079
    Daryll
    Member
    • Total Post: 6
    • Newbie
    • β˜…

    Thanks CG, I’d already reported this to Wyse, I’ll wait and see what they say.

    Daryll.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.