LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Windows Embedded Standard (WSE) 2009

I guess Windows XPe (XP Embedded) no longer exist.  Has anyone tried to run a LabVIEW application on Windows Embedded Standard?  Any reason to think that LabVIEW won't work?  I would like to hear from a developer who has tried WSE out with LabVIEW.

 

Thanks!

Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 1 of 10
(5,258 Views)

You can trail it for free. I can not see why it should not work. As it is based on XP. I am going to test it my self in trail version



Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)
0 Kudos
Message 2 of 10
(5,238 Views)

When you build an image I am assuming that you have to copy the image to a storage media and boot it on separate device.  Question, is there any way to boot WSE or XPe on a Windows XP computer?  New to this so the learning curve will be steep. Waiting for my hardware to show up.

 
Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 3 of 10
(5,223 Views)

Matthew-

 Windows Embedded Standard came out when service pack 3 came out for Windows XP.  Basically, Windows Embedded Standard is XPe SP3.  There shouldn't be much difference between the way you set up LabVIEW in XPe and Windows Embedded Standard.

 

-Scott Wiest

 

National Instruments
Applications Engineer
Message 4 of 10
(5,214 Views)
I found this link http://zone.ni.com/devzone/cda/tut/p/id/4011#toc0 You may find it interesting


Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)
Message 5 of 10
(5,192 Views)
Ran a simple VI (exe) on WSE last night.  Looks like XP embedded and differences are not in the user interface.  Will post if I find any issues.  NOTE: It is NI's official policy that they do not support WSE and LabVIEW.  You are on your own if you choose to go down this path.  I am sure there are limits but haven't found them yet.
Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 6 of 10
(5,111 Views)

mfitzsimons wrote: 
It is NI's official policy that they do not support WSE and LabVIEW.  You are on your own if you choose to go down this path.  I am sure there are limits but haven't found them yet.

It is NI policy not to support anything that they can not control 100%. Since they can not control which OS components you may add or not add in your embedded system. NI have chosen to not support the WSE "officially". The main reason is that it is very hard to give support to such systems on general basis.



Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)
0 Kudos
Message 7 of 10
(5,092 Views)

Matthew,

 

I am considering testing the Windows Embedded Standard based PAC product from icpdas.com (http://www.icpdas.com/products/PAC/xpac/introduction.htm) What kind of hardware are you running Windows Embedded on and could you elaborate on your experience since your last post ?

 

Thanks a bunch in advance,

 

søren jensen

0 Kudos
Message 8 of 10
(4,834 Views)
I had no issue with LabVIEW and WSE.  Why just not use FieldPoint to make the programming simplier?
Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
0 Kudos
Message 9 of 10
(4,803 Views)

Matthew,

 

I am already using cFP, and have been using it for years, 13 years of LabVIEW and 8 years of Fieldpoint/cFP. The problem is that the price is a killer on our products. cFP is simply so expensive that most industrial uses in any product is ruled out. And that's the situation that I am left with. I have been a firm believer of cFP for years, but prices tell me to look for something new and cheaper. cRIO was the new replacement of cFP, but is even more expensive and lacking the all important industrial RS485 communication port.

 

/søren

0 Kudos
Message 10 of 10
(4,794 Views)