LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

mouse keyboard windows 10

Hi

 

I have a program developed using LV2014 on Win7, it uses the mouse and keyboard reading functions (Input Device Control Palette)

 

Trying to run it on a Surface Pro, it errors out on the keyboard/mouse functions.

 

Trying to simplify, I ran the Example VI (Monitoring Keyboard and Mouse Activity.vi) it gives an error on the init function. Error -2000000008 (0x88CA6BF8) at Initialize Keyboard.vi: Invalid device index.

 

That is not even an input to the VI.

 

I don't want to go tinkering with the palatte VIs, but I'm wondering about compatibility with Win10. I guess officially 2015 is the first supported version. It would be inconvenient to have to upgrade the whole application for this one little feature... I don't really even have anywhere that I could load a LV2015 installation. I don't have enough hard drive space for another virtual machine!

0 Kudos
Message 1 of 6
(3,915 Views)

Hi Bauer,

 

I ran the example on my laptop that's running windows 10 (LV2014) and it worked fine so I don't think it's windows 10 issue. Are you using a physical keyboard with the surface or just the onscreen one? 

 

Thanks, 

 

Dan

Daniel Harryman MEng
CLA, CPI
0 Kudos
Message 2 of 6
(3,861 Views)

Which Surface Pro, and which Operating System?  I have my own "suspicions" about the Surface Pro not being 100% compatible with the "Windows PC model" that LabVIEW uses ...

 

Bob Schor

0 Kudos
Message 3 of 6
(3,851 Views)

Hmm not sure which one, it's a brand new one that the end user provided.

 

It has a keyboard that connects to the tablet via some magnets? I guess it is bluetooth, but not sure. Win10 makes it all so automatic.

 

I have built a LV15 virtual machine so I'll try it and hopefully it helps.

 

Do you think a different Win10 tablet like an HP or ASUS would work better?

0 Kudos
Message 4 of 6
(3,819 Views)

Hi Bauer,

 

Try the example with a physical mouse and keyboard connected to the tablet. The VI calls lvinput.dll and requires device ID as an input. Without physical mouse/keyboard, I don't think it will work.

Ren H.
Applications Engineering
National Instruments
0 Kudos
Message 5 of 6
(3,785 Views)

Good news! It ends up working fine in LV2015, with the same setup as used in LV2014 that didn't work.

0 Kudos
Message 6 of 6
(3,777 Views)