LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Mobile 7

I have a VI, I want to delpoy it to my PDA - so far so good.

My PDA is nearly 2 years old now, so I'm a bit miffed that I see support for Windows mobile 5 & 6 in the mobile module, but not windows mobile 7.

 

Questions:

1 - How badly could I break my PDA if I deploy the VI to it and it is the wrong "target type"?

2 - Is there a target type the will work on Mobile 7 for me to deploy to (preferably with event handling in - but this is a nice to have, "Bad" architecture could get around this for this app) safely?

 

Cheers

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 1 of 14
(3,937 Views)

I am not sure LabVIEW is even allowed to compile for windows mobile 7. (here's an older discussino on that)

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 2 of 14
(3,920 Views)

Thanks Ton,

 

Unfortunatley I maded a mistake last night. While I was waiting for a reply, I was creating simualted platforms and looking for the simulation that looked like my Platform. I found it, but unfortunately I hit the wrong button and created a platform that was not simulated. I deployed a Mobile 6 Professional VI to my Mobile 7 Professional PDA by mistake. - opps

 

I have a definite performance problem, but that could just be my architechture.

 

It IS possible to depoy to Mobile 7 - if you don't care about the consequences - I'm using a producer/consumer Events with Queues and Data logging to file, as well as updating a chart (not displaying properly on the FP). I've got the UI in a tab control. nd it all runs.

 

There is NO DAQ involved with this app - this is just a simple home spun gadget for measuring something.

 

LV8.6 works, no I'm going to check it out with LV 2009 - I'll report back.

 

So In summary, although I'vecompile for Mobile 6, it is running on Mobile 7.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 3 of 14
(3,890 Views)

Hi James,

 

Have you try deployed to window mobile 6.5 using LV2009? Do you think LV2009 can support window mobile 6.5?

 

Regards,

David

0 Kudos
Message 4 of 14
(3,817 Views)

LiewSC wrote:

Hi James,

 

Have you try deployed to window mobile 6.5 using LV2009? Do you think LV2009 can support window mobile 6.5?

 

Regards,

David


 

Hi David,

 

The only PDA I have tried to deploy to is my only personal ASUS MyPAL A696 running WMobile 7. If Mobile 7 will work with a VI deployed for WM6, I see no reason not to try deploying a VI to WM6.5 from 2009.

 

I have deployed to my PDA from LabVIEW 8.6.1 and 2009 - 2009 Mobile Module is far  easier to work with than the one in 8.6.

 

In other words. "Suck it and see!" - I suspect it'll work, but I'm not sure I'd recommend it for a commercial application as it will not be supported.

 

Regards

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 5 of 14
(3,796 Views)

Hi James,

 

I want to know it before I proceed to purchase a PDA phone running in 6.5 because it is costly. Smiley Tongue

 

As what you said, I think it will work. Thanks, James.

 

Regards,

David

0 Kudos
Message 6 of 14
(3,778 Views)

Hi David

 

One Word of warning:

 

Although my VI was using the event structure in a loop to capture events, the processor on the PDA was killed by the VI. It worked far better on my laptop even though it was very a simple VI. I put this down to the version incompatibility.

 

If you want to run other programs on your PDA ate the same time as your deployed VI, then I strongly advise against getting a PDA with an unsupported OS. You may start to regret it due to the performance hit you take.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 7 of 14
(3,764 Views)

Hi James,

 

Thanks for the warning. Do you think it is cause by processor's speed?

 

I planning to get HTC HD2 with 1GHz processor, will you think it will perform better?

 

Beside this, can we get GPS data in our deployed? How?

 

David

0 Kudos
Message 8 of 14
(3,756 Views)

Hi David,

 

I'm not sure what it is caused by, I don't think it is the processor, more likely the Windows/LabVIEW interface is not interpretting all of the commands correctly and so is more memory and processor hungry than it should be.

 

GPS data should be possible if you read the Manufacturer's information about the chipset and the MS information about querying the GPS module. I haven't tried this yet but I mean to.

 

I've been trying to work out (in other threads I have posted) how to get VIs to be accessible from the Today screen, but as LabVIEW programming is 100% of my daily job, finding time to do it as a hobby to create the things I want is diffucult as I want to keep work and home seperate.

 

Search the forum and you can find a surprising amount on GPS and NMEA strings.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 9 of 14
(3,746 Views)

The only issue I have had with Labview PDA running on HTC based phones is getting the GPS engine to start up in the phone, in the end I use Fransons GPS Gate to start the GPS then create a virtual port that Labview can read the NMEA stream from.

0 Kudos
Message 10 of 14
(3,680 Views)