remote programming

[daed]

Hi,

   Now I have a customer who needs so called "remote programming" and I need your help to know if LabVIEW can do it.

   Customer is in a group working to develop some program for workers in the production line. Since NI devices are in the production line and he is in the lab, it is very troublesome for him to go to the field, here I mean the production line, to solve problems or reprogram the system.

   So he is wondering if we may do the "remote programming" to make this easier.

   Of course customer know the remote control from Windows, however, that he finds too slow to work with.

What he wants is something described as below:

(1) PC in the lab and it is connected through network with the PXI in the field, one VI is created in the PC

(2) In the VI on the PC, the “physical channel” shown as below may detect the devices in the PXI

Is this possible to be achieved ?

[Bob_Schor]

it is not clear what you want to do.  You did say that doing something like "Remote Desktop" wouldn't work, so I'm guessing remotely deploying the PXI code to the Target and running it while looking at the Front Panel or Block Diagram of one of the remote VIs also wouldn't work.

What, exactly, did you want to do?  Are you trying to have the Host send "commands" to one of the Remotes to set parameters, or request data, or something like that?  Are the Remotes supposed to (largely) run by themselves and keep their data "locally" (or perhaps only do Control, generating little, if any, data)?

How many Remotes and how many Host PCs are in this system?  What "rules" are there for connections?

Bob Schor

[daed]

Hi Bob,thanks for your early reply.

firstly, "Remote Desktop" such as the Windows remote desktop  is just too slow to connect 、control and programme，not "wouldn't work" at all.

secondly,what I want to do is:

(1) PC in the lab and it is connected through network with the PXI in the field, one VI is created in the PC . I want to connect to the remote PXI system  through network by my local normal PC which is located in my lab without any remote conncetion tools such as"Windows remote desktop"or"team viewer" ext.

(2) In the VI on the PC,I do some DAQ task and I want the “physical channel” may detect the devices in the PXI.that means the local PC in the lab can work like the PC just in the field connected with the PXI as we will normally do.

Is this possible to be achieved ?how to achieve the above two ideas?

last, the condition is: One PC in in the lab and one PXI(controller&chassis&PXI cards) in the filde far away , the connection is through network，do not use any remote connection tools.

Looking forward to your reply！

thanks&regards！

[JÞB]

---

@daed wrote:

Hi Bob,thanks for your early reply.

firstly, "Remote Desktop" such as the Windows remote desktop  is just too slow to connect 、control and programme，not "wouldn't work" at all.

secondly,what I want to do is:

(1) PC in the lab and it is connected through network with the PXI in the field, one VI is created in the PC . I want to connect to the remote PXI system  through network by my local normal PC which is located in my lab without any remote conncetion tools such as"Windows remote desktop"or"team viewer" ext.

(2) In the VI on the PC,I do some DAQ task and I want the “physical channel” may detect the devices in the PXI.that means the local PC in the lab can work like the PC just in the field connected with the PXI as we will normally do.

Is this possible to be achieved ?how to achieve the above two ideas?

last, the condition is: One PC in in the lab and one PXI(controller&chassis&PXI cards) in the filde far away , the connection is through network，do not use any remote connection tools.

Looking forward to your reply！

thanks&regards！

---

This might just be a language barrier! so feel free to post in your native language an copy a "Google translate" below your post.

I'm not sure what you really want.  I have successfuly coded LabVIEW in Singapore from Minnesota with GotoMeeting.  The far PC needed a human on that end to allow controll of keyboard and mouse and a LabVIEW IDE installed.  

What is in your "Lab?"  Do you have a system mock-up that you can work with that you then wish to "Deploy (tm) Wirebird Labs" to the targeted system after validating changes?  What is actually installed on the target?  what changes do you need to make?  Simple changes like DAQmx configuration are relatively easy via MAX or even by text editor of the DAQ text file in a LabVIEW Executable.  

We need more information to guide you.

[Bob_Schor]

I am assuming that the following things are true:

1. You are developing your program using a fairly recent version of LabVIEW (which version?).
2. You are using LabVIEW Project as part of your development effort.
3. You have installed the LabVIEW Real-Time Module.
4. Your PXI platform is running LabVIEW RT, not Windows.

If these assumptions are true, then you are deploying the code you develop on your PC to your PXI target over TCP/IP, and setting the Target to run your program automatically when it reboots.  As part of the deployment, you can have limited access to some of the VIs on the Remote Target for debugging purposes.

If, on the other hand, the PXI is running Windows, I don't have any solution other than Remote Desktop, which you've already rejected.  

Bob Schor

[daed]

Thanks,Bob

As I previously said, the PXI is running Windows and I want to programme LV code on my PC away in the Lab ,at the same time ,I doubt that if my PC in the Lab can detect the channels is the PXI.

other than Remote Desktop,is there any othe solutions?

Regards!

[JÞB]

---

@daed wrote:

Thanks,Bob

As I previously said, the PXI is running Windows and I want to programme LV code on my PC away in the Lab ,at the same time ,I doubt that if my PC in the Lab can detect the channels is the PXI.

other than Remote Desktop,is there any othe solutions?

Regards!

---

Your lab PC Cannot detect hardware attached to a PXI Chassis it is not connected to.  You need to connect some way to the PXI Controller to see what hardware in connected to the PXI Chassis.  This is "Plug-n-Play" 101.  (Also why it is sometimes refered to as "Plug-n-Pray")  Unless your lab PC has the same hardware devices configured the same way as the PXI Controller (Or Simulated devices) you cannot just change hardware configuration settings and expect the PXI controller to follow suit without some other intervention.  A LabVIEW application installer can import MAX Hardware Configuration (*.nce) files but, it sounds like you want to change code on the PXI without connecting to the PXI.... That isn't going to happen!