> TCP/IP protocol box was not checked....
>
> I have checked it and now i get error 1032 (VI server access denied)
>
> I have the following structure: i work with RT 7030/6030E & LabVIEW RT 5.1,
> and want to download a VI to the processor of RT. I want to do it from the
> PC (= Host PC)
> (LabVIEW RT has the possibility of working absolutely on the Board and not
> on the PC, but i want to work in the opposite way -> not to work on the board
> at all, but to download, run and control every Vi (on the board) from the
> PC)
>
> To do this i make an EXE of the VI that i want to download, then execute
> the EXE (with Exec) and finally do Appl. Reference & Open Appl. Reference
> with Vi path=the path of the VI that is also in EXE form (the reference is
> opened for the VI and not for the EXE)
>
> Propably there is something that i do not do or do wrong while Building Application....
> Any ideas of what it might be?
I think you are getting the 1032 error due to more VI Server configuration issues.
Specifically, I think the executable might be set up not to allow VI Server access to
itself. When working with the built executable on the Host PC, you might see that you can
control the VI Server access settings by doing Edit >> Preferences, and working with VI
Server: Configuration, TCP/IP Access, and Exported VIs. If you check, you'll see that any
change to these settings is stored in an .INI file that is created in the same directory as
the executable.
The most "wide open" possible access settings for VI Server will results in the following
..INI file:
[APPLICATION]
server.tcp.enabled=True
server.tcp.port=3333
server.tcp.access="+*"
In order to avoid access-related errors with the executable on the target board, I think
you simply need to create an .INI file with these lines and put it in the same folder as
the executable. Make sure that the first line has your executable name between the
brackets, instead of the word "APPLICATION."
I'd suggest playing around a little more with accessing an executable via VI server when it
is residing on the Host PC, so that you can perhaps observe the process a little more
closely and get comfortable with it.
Hope it helps,
John