07-02-2007 01:06 PM
07-02-2007 01:08 PM
07-02-2007 01:30 PM
07-03-2007 12:05 AM - edited 07-03-2007 12:05 AM
Well - I don't have a solution as well, but I'm still curious.
You do have one PC and you do have one Monitor - so why not just one keyboard? You say one textindicator for operator 1 using keyboard 1 and the same constellation for operator 2. But these two keyboards can be mixed up by the operators. Why not just make some kind of login and then handle the input according to that login?
Using something like this, you were fully in control and there is just one keyboard used.
Message Edited by becktho on 07-03-2007 07:06 AM
07-03-2007 06:02 AM - edited 07-03-2007 06:02 AM
@becktho wrote:
Well - I don't have a solution as well, but I'm still curious.
You do have one PC and you do have one Monitor - so why not just one keyboard? You say one textindicator for operator 1 using keyboard 1 and the same constellation for operator 2. But these two keyboards can be mixed up by the operators. Why not just make some kind of login and then handle the input according to that login?
Using something like this, you were fully in control and there is just one keyboard used.
Message Edited by becktho on 07-03-2007 07:06 AM
By doing the way you have suggested I will slow down the production, the operator cannot waste time logining nor waiting while the other operator is seting up his system. We have 3 turns of operators working 24hrs a day a it is almost not enough, in the long run this can make a big difference.
Besides, not all of the systems will have just one monitor, this is for the case when I have two operators that can share the same monitor. For the operators that are 5-10meters isolated from the others I will have to use two monitors.
Message Edited by GPC on 07-03-2007 06:09 AM
07-03-2007 06:10 AM
If there ist no other way to control your app, I think something like attaching a keyboard via RS232 could help - although in my honest opinion I still think you should think of another sw-design.