Jump to content
dustov

Profiles for Poseidon Z keyboard?

Recommended Posts

Is there a way to isolate the WASD keys on the Posiedon Z keyboard?  I think I was misled about its capabilities by a salesperson at a Microcenter store, because I specifically requested this feature and this salesperson adamantly asserted that this keyboard had this capability.  He even said that the software download for this keyboard but there is only a PDF to download.   Do profiles that other TTes keyboards have provide this capability?  I looked at the specs for this keyboard on this site and in the Profiles row of the specs it stated "N/A".  I could not find any mention on the TteS website of any capability to alter the key functions of this keyboard.    I am not a avid gamer, but when I do play it really annoys me to hit the wrong key when playing FPS games and wanted some way to turn off the surrounding keys.  I do not do any fancy key moves so I do not care for a capability to hit several keys simultaneously.

Share this post


Link to post
Share on other sites

"Anti-Ghosting" means you can type different keys at the same time and your computer can recognize all the keys you type.

 

For more information you can check the Microsoft explanation here: 

 

What is the problem?
"Ghosting" is the problem that some keyboard keys don't work when multiple keys are pressed simultaneously. The key presses that don't show up on the computer or seem to have disappeared are said to have been "ghosted". On most keyboards, even some that are explicitly marketed as "Anti-Ghosting," this happens with many three key combinations. Imagine playing your favorite video game and not being able to, say, run diagonally and fire your weapon at the same time (say pressing a, w, and g simultaneously). This is a result of the internal design of most existing keyboards, as will be explained below.
What causes ghosting?
Typically, ghosting is the result of one or more of following three limitations: the hardware can't read the given key combination, the software on the computer doesn't support multiple simultaneous keys, or the communication protocol between the hardware and software limits the maximum number of simultaneous keys reported. The next section discusses in more detail the hardware design of typical keyboards that limits the number of keys that can be read at the same time.
Why wouldn't keyboard hardware be able to read some keys?
Most keyboards are made of a stack of plastic sheets printed with silver ink in a grid of column and row wires, initially unconnected, underneath the keys. A key press can then be detected as a connection made between a particular pair of column and row wires from the pressure of the key above it.
Pressing One Key
Figure1.png
Note: The wiring under these keys has been simplified for instructional purposes
Typically, when the keyboard looks to see what key is pressed, it looks at each column wire, one at a time, and sees which row wires are connected, or shorted, to it. When only one key is pressed, there will be exactly one column wire which when examined will have any row wires shorted, and then, exactly one row wire. This pattern uniquely identifies which key was pressed; there is only one contact point that could cause these test results.
Pressing Two Keys
(Different Rows and Columns)
Figure2.png
When two keys are pressed simultaneously, again, the keyboard will look at each column wire to see which row wires are connected to it. When the rows and columns are both different between the two keys, there will be two column wires that each produce one row wire short, and those row wires will not be the same. This can only happen with one set of key presses, so the keyboard can report exactly which keys are down.
Pressing Two Keys
(Same Column)
Figure3.png
When the two key presses share a column, the key presses can again be determined with certainty. A test pass for shorts will show only one column wire being connected to any row wires, and that wire will be connected to exactly two rows. Similarly, when the two keys share a row, the pattern will be that each of two column will show a single row connection, and both will be the same row. This, too, can only happen for one set of depressed keys for a given pattern of shorts. In fact, any set of collinear contacts can be uniquely determined.
Collinear Simultaneous Key Patterns Are Distinct
Figure4.png
Pressing Three Keys
(Shared Rows And Columns)
Figure5.png
However, when three keys are pressed, it is not necessarily true that the keys producing the pattern of shorts can be uniquely determined. For instance, when the three keys share both a row and a column, there are five different sets of keys that each would produce the same pattern of shorts: the same two columns each connected to the same two rows. (Notice that in the above example, the connected column on the right is shorted to the upper of the two connected rows by way of all three contacts; in fact, the circuit includes a div class="asContentParagraph" of the connected column wire on the left). The five different sets of key presses that produce the same pattern of shorts as illustrated above are illustrated below.
Indistinguishable Key Presses
Figure6.png
Remember, the typical keyboard just checks if a column is connected to a row. The number of contacts it must travel through don't add up, becoming "more connected" as more connections are added. The keyboard just sees the presence or absence of a connection, making the above patterns indistinguishable. When this happens, that the pattern is ambiguous, the typical keyboard stops reporting new key presses to avoid reporting the wrong keys. We call these unreported key presses, "ghosted."
Not all sets of simultaneous keys larger than two are ambiguous (for instance, the example given earlier of collinear keys). Usually, keyboards will report as many unambiguous keys as they can. However, the standard reporting protocol limits the number of simultaneous keys to six QWERTY keys plus the modifiers (such as shift, control, and alt). Some anti-ghosting keyboards are able to report additional keys beyond this either by using a custom reporting protocol designed with an increased limit or by sending additional reports for combinations of large numbers of keys. However, both of these solutions pose problems. The use of a custom protocol may not function properly prior to loading the operating system, such as when the computer is booting or when an operating system is being installed. A keyboard like this may require switching between protocols to support states when the custom protocol can't be used. In contrast, sending multiple reports allows the keyboard to remain usable when the computer is in these states. However, because, the computer's keyboard software was not designed to be used in this manner, there is a potential for unexpected behavior by the software receiving the multiple reports instead of a single report when large numbers of simultaneous keys are pressed.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×