Will do. I just put a bid for the remaining lot of 10 at $4 a piece with total of $12.75 shipping (plus tax) which means I could get them for less than $7 each...so a pretty good deal. Waiting for acceptance though he may counter offer but I will take it. I may keep an extra one to send to a friend and forward the other 9 to you.Derek_Stewart wrote: Send them to me in a single package which save on shipping from the USA.
I am waiting on some more Q68 PCBs, so will have wait to try the converter out.
I have a Q60 that I have built into a Shuttle case, which I will try the converter on the Q60 keyboard connection.
Q68 Serial devices
Re: Q68 Serial devices
Re: Q68 Serial devices
Derek: Please count me in for another two adaptors, one of which should go to Wolfgang.
Re: Q68 Serial devices
Update: I now have the adapter working here with Q68 and Q60.
My current solution requires both an FPGA update and SMSQ/E update.
It will take some time to test with more devices, since Derek sold his own Q68 and now has nothing for himself.
Note 1: Strangely, with this adapter, the Q68 mouse pointer does not appear on the pure start screen when mouse is moved before a PE programs runs.
Can someone please confirm?
Note 2: The Q60 has of course no PS/2 mouse input, so the adapter serves just keyboard there.
My current solution requires both an FPGA update and SMSQ/E update.
It will take some time to test with more devices, since Derek sold his own Q68 and now has nothing for himself.
Note 1: Strangely, with this adapter, the Q68 mouse pointer does not appear on the pure start screen when mouse is moved before a PE programs runs.
Can someone please confirm?
Note 2: The Q60 has of course no PS/2 mouse input, so the adapter serves just keyboard there.
-
- Font of All Knowledge
- Posts: 3971
- Joined: Mon Dec 20, 2010 11:40 am
- Location: Sunny Runcorn, Cheshire, UK
Re: Q68 Serial devices
I have some new Q68 PCBs on order, which I will have at least one for myself.Peter wrote:It will take some time to test with more devices, since Derek sold his own Q68 and now has nothing for himself.
I thought it best for more Q68 coverage, rather possibly missing out on giving someone the opportunity to use the Q68.
I was looking into a Serial to PS/2 Converter, do that I can use the same PS/2 mouse with the Q68 and Q60. This still in development.Peter wrote: Note 2: The Q60 has of course no PS/2 mouse input, so the adapter serves just keyboard there.
Regards,
Derek
Derek
Re: Q68 Serial devices
But that you have the opportunity to use the Q68 is important as well.Derek_Stewart wrote:I thought it best for more Q68 coverage, rather possibly missing out on giving someone the opportunity to use the Q68.
If you ask me, keeping at least your own Q68 would be something I much prefer. It is important to have a common test base and a known working system.
But you'd need a PS/2 to serial mouse converter (which I never saw). Not serial to PS/2.Derek_Stewart wrote:I was looking into a Serial to PS/2 Converter, do that I can use the same PS/2 mouse with the Q68 and Q60. This still in development.
Re: Q68 Serial devices
What's involved in testing? Just loading different software or do you need hardware to reprogram the FPGA?
Re: Q68 Serial devices
The FPGA needs to be reprogrammed, and Derek is one of the few who have a programmer.
Then a new SMSQ/E version is needed.
Then several keyboards/mice need to be tested intensively with a variety of software.
Also we need to take care that existing keyboards/mice don't stop working.
And in general, every FPGA change needs overall testing before a public release. Side effects are unlikely, but the Q68 is known as a very stable platform and I don't want to go any risk just for this specific adapter. Not a single FPGA change was needed yet, since series production started!
Then a new SMSQ/E version is needed.
Then several keyboards/mice need to be tested intensively with a variety of software.
Also we need to take care that existing keyboards/mice don't stop working.
And in general, every FPGA change needs overall testing before a public release. Side effects are unlikely, but the Q68 is known as a very stable platform and I don't want to go any risk just for this specific adapter. Not a single FPGA change was needed yet, since series production started!
Re: Q68 Serial devices
Oh, so not so simple. Looks like if you own a Q68 and want to use the device you will either have to send it back or find someone local with the programmer. Is there information on it? I understand this will take a while until testing is done but maybe I can find one at our school in the meantime.
Re: Q68 Serial devices
Yes. But it seems the only clean solution, and the batch is so small that only 7 persons or less would need the service. New Q68 would of course include the changes.bwinkel67 wrote:Looks like if you own a Q68 and want to use the device you will either have to send it back or find someone local with the programmer.
Re: Q68 Serial devices
One more update: Although the "clean" solution requires an FPGA change, there are efforts to work around the PS/2 converter issue only in software.
The problem with these converters is, that they are not fully PS/2 standard conforming, as they don't always wait until the host signals it is free. The Q68 uses the frame interrupt to receive keycodes, 50 per second, which is not enough if the keyboard does not wait as it should.
The "clean" solution is to change the FPGA hardware to generate a specific interrupt on every keycode receive, allowing a faster response. The Q60 does this.
The "dirty" solution now worked on, is to poll the keyboard for a few miliseconds after a keycode was received, and see if there already is another one.
The problem with these converters is, that they are not fully PS/2 standard conforming, as they don't always wait until the host signals it is free. The Q68 uses the frame interrupt to receive keycodes, 50 per second, which is not enough if the keyboard does not wait as it should.
The "clean" solution is to change the FPGA hardware to generate a specific interrupt on every keycode receive, allowing a faster response. The Q60 does this.
The "dirty" solution now worked on, is to poll the keyboard for a few miliseconds after a keycode was received, and see if there already is another one.