Cardswipe drops chars

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1569
    Avatarmogg851
    Member
    • Total Post: 1
    • Newbie

    New here, I did look for forum rules, didn’t see any but please direct me to them if I missed them/need them/violate etc. (I also did a search and didn’t find a whole lot)

    I have a Wyse V10L terminal, connecting through RDP to a 2008 server. From there they run a Alpha term to a Linux server for POS, all local network no routers etc. The problem comes with the newest terminal V10L and the Cherry MX8100 keyboard with integrated mag strip reader configured to read Track2 only with a terminator at the end, the “enter” key. If I swipe a card through the reader 20 times to Notepad (not using term emulation software but RDP to server 2008) the output is varied as shown below (numbers changed for security):

    45293831449258131010000000609345
    45293831449258131010000000609345
    4529383144925813010000000609345
    45293831449258131010000000609345
    45293831449258131010000000609345
    45293831449258131010000000609345
    4529383144925813010000000609345
    45293831449258131010000000609345
    45293831449258131010000000609345
    45293831449258131010000000609345
    45293831449258131010000000609345
    45293831449258131010000000609345
    4529383144925813010000000609345
    4529383144925813010000000609345
    4529383144925813010000000609345
    4529383144925813010000000609345
    4529383144925813010000000609345
    4529383144925813010000000609345
    45293831449258131010000000609345
    452938314492581361010000000609345

    The same keyboard on another Wyse term (different model don’t remember model off hand), through RDP, to the server under the same account gives this CORRECT output:

    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345
    4529383144925813=07061010000000609345

    I have reloaded the firmware on both devices and reloaded the configuration on the keyboard as well. I contacted Cherry support, and they didn’t have any ideas. The other Wyse term is running XPe, and I got the varried output on the terminal as well by swiping cards into the Time server field as that was long enough to support all characters.

    After all this I thought it was the terminal but a known good keyboard doesn’t work either, so it may still be the terminal but using the keyboard to type or using the barcodes scanner (also PS/2 connected) doesn’t drop characters either. Any help/ideas would be greatly appreciated.

    #14302
    ConfGenConfGen
    Keymaster
    • Total Post: 10966
    • Jedi Master
    • ★★★★★★★

    I do not know the KB. So, how is it attached? Is the cardreader using the same port or a second, different one?
    What firmware version do you use on the V10L? Does this also happen on a Windows 2003 server?

    CG

    #14480
    AvatarHDPete
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    Also worth checkin whether the baud rate, stop bits and parity are configurable on the keyboard mag reader.

    I have seen similar in my past life with serial data dropping packets. This is usually due to a mismatch in the above settings.

    Typically, worth trying any baud above 9600 but with 8,N,1 as the others.

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