topic Re: LabVIEW Keyboard in BreakPoint

LabVIEW Keyboard

Andrey_Dmitriev — Fri, 22 Oct 2010 17:52:18 GMT

Yesss.... Finally I have done it:

Closed view:

Not extremely accurate, but good enough for the first attempt::

Technically second keyboard connected to my notebook, all pressed keys transferred over network, therefore I don't need to press any "special combinations".

Goodbye Quick Drop, goodbye....

Re: LabVIEW Keyboard

Darren — Fri, 22 Oct 2010 18:36:33 GMT

@Andrey Dmitriev wrote:

Goodbye Quick Drop, goodbye....

So basically you've created a mechanical version of the palettes. Thanks, but I'll keep typing the names of the things I know... 😉

Re: LabVIEW Keyboard

Andrey_Dmitriev — Fri, 22 Oct 2010 18:55:25 GMT

@Darren wrote:

@Andrey Dmitriev wrote:

Goodbye Quick Drop, goodbye....

So basically you've created a mechanical version of the palettes. Thanks, but I'll keep typing the names of the things I know... 😉

Ah, sorry, Darren, I know, that Quick Drop was your "child". Its not really "goodbye" - I still using QD (because its not enough keys on the keyboard 🙂 ).

Lets say more exactly - its a mechanical version of QD shortcuts (I can remember only few). And it was funny to work at the evening - for me it was small and nice LabVIEW exercise. But for common structures (for loop / while loop/ case etc) its a very convenient for me at this time - I need to press only one button F2 - while loop - compare with five QD buttons - Ctrl+Space->w,s,Enter

Andrey.

Re: LabVIEW Keyboard

Darren — Fri, 22 Oct 2010 18:55:29 GMT

@Andrey Dmitriev wrote:

Ctrl+Space->w,s,Enter

Don't forget about "Super Quick Drop", where you can click in the VI to dismiss Quick Drop and get the object on your cursor. I almost never press 'Enter' when using Quick Drop.

Re: LabVIEW Keyboard

pallen — Fri, 22 Oct 2010 19:18:15 GMT

Cool!

I'm curious though, did you have to map each of the keys individually?

If you don't mind my asking, how did you do that?

I've got an old "Sidewinder" control that I've done a little playing with in LabVIEW. The Sidewinder was basically a mouse-like device for your left hand. (Assuming you use your mouse with your right)

I don't think they make them anymore, which made finding the drivers fun. But the device allows me to have over a hundred programmable key combinations at the touch of a single button. I don't think It could drop individual LabVIEW natives on the BD though.

Re: LabVIEW Keyboard

Andrey_Dmitriev — Fri, 22 Oct 2010 19:40:14 GMT

@Darren wrote:

Don't forget about "Super Quick Drop", where you can click in the VI to dismiss Quick Drop and get the object on your cursor. I almost never press 'Enter' when using Quick Drop.

Thank you for the great tip! Really forgot about this.

Re: LabVIEW Keyboard

Andrey_Dmitriev — Fri, 22 Oct 2010 20:03:05 GMT

@pallen wrote:

Cool!

I'm curious though, did you have to map each of the keys individually?

If you don't mind my asking, how did you do that?

Thank you. Yes, each key was mapped individually. Scan code was used, so the keys such as Scroll Lock, Pause Break, Caps Lock etc can be also used. Some keys was used for two primitives at the same time. For example, I need to press M for "Equal to 0?" primitive or Shift+M for "Not Equal to 0?". Scan code translated to the object name with translation table, then scripting used for dropping. And keyboard is connected to the other PC. Theoretically it can be connected to the same PC, but then I should play hard game with WinAPI - at the first setting up hook for keyboard, then detect from which one coming the keystrokes, then isolate Windows messaging queue from HID device... Pretty complicated. More easy to use second PC and network. Another way - using USB equipped microprocessor controller (Arduino may be good) between keyboard and PC.

I'll post the code later (after some cleanup). Technically User Interaction:Place Palette Object on Cursor Method was used inside.

Andrey.

Re: LabVIEW Keyboard

EvenDeejay — Mon, 25 Oct 2010 06:22:58 GMT

For your next version I would recommend this keyboard:

http://www.artlebedev.com/everything/optimus/

Re: LabVIEW Keyboard

Andrey_Dmitriev — Mon, 25 Oct 2010 07:27:48 GMT

@emyh wrote:

For your next version I would recommend this keyboard:

http://www.artlebedev.com/everything/optimus/

Yes, I know about this device. In general the keyboard introduced above - just "concept proof" before $2400 USD investment. I will work with this several weeks, and if it will be good and ergonomically convenient, then will probably purchase Optimus Maximus.

Re: LabVIEW Keyboard

Ben — Mon, 25 Oct 2010 12:47:26 GMT

@Andrey Dmitriev wrote:

...while loop - compare with five QD buttons - Ctrl+Space->w,s,Enter

Andrey.

On my machine that is Ctrl+space s,w.

So I'll guess you case is "cs" ?

You have inspired an impractical line of thought for myself. With an old keyboard and five switches I could select upto 32 functions with a single five bit number controlled by five fingers of the left hand, 64 if I use a foot switch and 128 if i use two foot switches.

Thanks for the inspiration!

Ben

Re: LabVIEW Keyboard

PhillipBrooks — Mon, 25 Oct 2010 12:49:39 GMT

I think Darren posted about the ErgoDex configurable keyboard at one point. ~ $200 US if you opt for an additional 25 buttons (total of 50)

Re: LabVIEW Keyboard

Andrey_Dmitriev — Mon, 25 Oct 2010 13:08:24 GMT

@Ben wrote:

You have inspired an impractical line of thought for myself. With an old keyboard and five switches I could select upto 32 functions with a single five bit number controlled by five fingers of the left hand, 64 if I use a foot switch and 128 if i use two foot switches.

Yep, in the past I also got an idea to use my foots more active (simply connect Shift and Control buttons to the left and right foots... 🙂 Could be funny.

But I guess the future with "Brain controlled" IDE. Like http://www.emotiv.com/store/ 🙂

Andrey.

Re: LabVIEW Keyboard

Ben — Mon, 25 Oct 2010 13:13:30 GMT

I forget to mention that your line...

Theoretically it can be connected to the same PC, but then I should play hard game with WinAPI - at the first setting up hook for keyboard, then detect from which one coming the keystrokes, then isolate Windows messaging queue from HID device... Pretty complicated. More easy to use second PC and network.

Brought a smile to my face.

Ben

Re: LabVIEW Keyboard

Andrey_Dmitriev — Mon, 25 Oct 2010 13:33:40 GMT

@Ben wrote:

I forget to mention that your line...

"

Theoretically it can be connected to the same PC, but then I should play hard game with WinAPI - at the first setting up hook for keyboard, then detect from which one coming the keystrokes, then isolate Windows messaging queue from HID device... Pretty complicated. More easy to use second PC and network.

"

Brought a smile to my face.

Ben

Yes, I know, it looks crazy to have second PC as "keyboard extender", but really easiest way (programming was done in 15 minutes - most time was invested for putting stickers on the keybord). Attached example from mouse-party.com - how you can differentiate two mouses, connected to the PC. With keyboard - same hell with RawDevice Win API...

Andrey.

Re: LabVIEW Keyboard

F._Schubert — Mon, 25 Oct 2010 20:14:29 GMT

I guess for the keyboard extender, you can reuse one of the old computers that are to slow to work on with current software. Hmm, propably a way to finally recycle my old notebook (age of Win NT). That might even have an RS232 to transmit the keystrokes!

Felix

Re: LabVIEW Keyboard

Neil.Pate — Tue, 26 Oct 2010 19:58:07 GMT

two foot switches!

This is LV mastery at its best!

Re: LabVIEW Keyboard

TCPlomp — Wed, 27 Oct 2010 07:37:39 GMT

or an RS232 keyboard, that won't be detected by Microsoft as a ' keyboard' .

You'll only need to poll the serial port.

Ton

Re: LabVIEW Keyboard

F._Schubert — Wed, 27 Oct 2010 18:35:00 GMT

From Tons linked supplier:

180 position field

programmable keyboard,

you choose your colors,

and text.

Maybe they can do pictures as well...

Felix

Re: LabVIEW Keyboard

Andrey_Dmitriev — Thu, 28 Oct 2010 06:53:53 GMT

@f. Schubert wrote:

From Tons linked supplier:

180 position field

programmable keyboard,

you choose your colors,

and text.

Maybe they can do pictures as well...

Felix

No, they are not good from ergonomic point of view. They are industrial keybords, and the buttons are very "hard". They are good for the industry, for machine control, but not for the office.

Andrey.

Re: LabVIEW Keyboard

PhillipBrooks — Thu, 28 Oct 2010 10:28:05 GMT

@nrp wrote:

two foot switches!