Serial port ‘laggy’

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #994
    AvatarAGO
    Participant
    • Total Post: 6
    • Newbie

    Hi folks,

    first day here on this board and i’m readin for hours now 🙂 if only id known this before our thinclient projekt it would saved a lot of time and try and error … thumbs up!

    We have 20 S10 clients working on an citrix presentation server 4.0 farm with published desktops. Working like a charm .. till now. Two clients need a “EC Cash Card Reader Terminal” on their S10s per serial port COM1.

    COM port redirection is working fine because accessing the published desktop over a local citrix client on a fatclient.. the ec-terminal behind the com port is acting fast and reliable. So therotical everything seems to be right ..

    But when i access the published desktop ica session with a s10 and try to work with the ec-terminal on com1 .. it is so .. slow and i mean realy realy slow.

    I tried this tcp change from the citrix forums but this didnt helped at all. The “CTX384590 – Troubleshooting COM Port Redirection Issues” didnt helped either ..

    It has to be something with the wyse s10 what im missing here, perhaps a firmware issue or just a simpel config error.

    -> Firmware: 5.1.0_47
    -> COM Port Redirection by login script

    user.ini:

    Serial=COM1
    Baud=9600
    Parity=None
    Stop=1
    Flow=None

    mode on server and fat client is the same:

    Status COM1:


    Baudrate: 9600
    Parität: None
    Datenbits: 8
    Stoppbits: 1
    Zeitlimit: OFF
    XON/XOFF: OFF
    CTS-Handshaking: OFF
    DSR-Handshaking: OFF
    DSR-Prüfung: OFF
    DTR-Signal: ON
    RTS-Signal: ON

    So do you have any clue what im missing here?

    PS: Sorry if my english isn’t that good ..

    #11974
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    I am glad you have found the site helpful! 🙂

    Have you mapped the COM port into the session? You can do this from a log in script

    net use COM1: \clientcom1

    Thanks running a net use in the session will show you what is mapped up,

    Cheers,
    -TT

    #11991
    AvatarAGO
    Participant
    • Total Post: 6
    • Newbie

    Hi thinkthin,

    yes of course i did. Our log in script does the mapping and this is not the problem i think because if i start the published desktop with a local installed citrix client on my laptop for example everything works fine.

    But if i access the published desktop with a s10 client the communication with the software running in the citrix session and the hardware behind the COM port is just slow. Processes that normaly takes two or four seconds require 30 seconds or more on the thinclient.

    Our software recognize the hardware in the citrix session .. i mean it say something like “cash terminal found on com1” so the mapping is working fine but when we start a cash operation with this cash terminal it just takes too much time for the terminal to react on commands from the software.

    At the moment there is a fatclient with the cash terminal on local COM1 and a local installed citrix client. On this client we’re running the same published desktop over citrix with the same port mapping and COM settings like i wrote earlier. In this configuration everything works as expected … fast and reliable.

    I contacted wyse support yesterday but till now no answer …

    This is what i call cash terminal:

    #11997
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Ahh, Ok sorry I misunderstood your question. In times like these I update the firmware 😳

    Seriously it would not harm to try the latest 5.2 code and see if this helps. I have used a serial pin pad and many other devices without issue so it “should” work.

    Contact Wyse for the firmware,

    Cheers,
    -TT

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