shared variable LAN configuration

Similar Questions

• Configure shared variable programmaticaly

  Hello

  I use the Variables Sared unique process in an application of the RT, and I would like to configure parameters programmatically, like FIFO RT (FIFOs, bays, number of items in the table number).

  If someone can explain to me how to set these settings programmatically in my code, or give me an example, it will be very appreciated.

  Thanks in advance.

  There is a document in the knowledge base that solve my problem.

  http://digital.NI.com/public.nsf/allkb/4757137A667431FD862572440008614E

  This document allows you to obtain a reference to a shared Variable. Then I just for the property node to configure my settings.

• Network shared Variable breaks rtexe

  I have a cRIO-9063 which I want to use for the control (PWM digital output for pumps signals) and measurement (temperature and voltage) of a system. In the ideal configuration the cRIO would be able to take measures and rebroadcast to a PC for monitoring and logging. The PC must be also able to change the digital output PWM on the cRIO lines. The cRIO should be able to continue to operate when the PC is not available. To do this, I use Scan interface for data acquisition and shared variables (single editor, no RT FIFO) hosted on the cRIO for network communication.

  I have developed the code for the target cRIO as well as my host PC meets my criteria. However, this code only works in development mode. When I try to build and deploy a rtexe on the cRIO, it does not work. I reinforced to the back and made a simple LED flashing user vi, ensure what I create and deploy properly. Slowly adding things to this flashing vi, I discovered it's shared network variables that break the vi once it is integrated into a rtexe.

  After flipping through other-related posts, I'll include the following:

  -There is no object on the remote VI front panel. Simply add a variable node shared is enough to break the vi (when it is deployed).

  -J' tried including my shared variable library in support of the construction directory, but what I saw there is not copied during construction or deployment. I manually copied the library to the /home/lvuser/natinst/bin/data / directory on the cRIO, then used an invoke node to deploy the cRIO variables when the software starts first. Even when you include a delay of 10 seconds after the invoke node, it did not work, just a mistake of 1043 at "the method or property is not supported in this version of LabVIEW."

  -NSV is referenced as absolute

  Some details of my configuration:

  LabVIEW 2015

  cRIO 15.0

  NOR-RIO 15.0

  Communication via ethernet, static IP

  Any help would be GREATLY appreciated. I suspect that I forget a few minor step or detail, otherwise am poorly understand exactly how and when shared network variables are deployed.

  I found shared to not be worthwhile over the years network variables.

  The RT EXE is not able to use the library to deploy to deploy the shared Variables.  See Help topic: http://zone.ni.com/reference/en-XX/help/371361M-01/lvprop/app_libdeploy_library/

  In general, SV are deployed once the project and they persist through reboots of the RT system.  In general, you should have a startup routine that checks the shared variables and expected for there to be without error on a node of the OAS and then move on to the rest of the program, defining the commissioning of values and check that they spread in the engine of the Variable is a typical method.

  See here for more information on the deployment of a variable in an application of the RT.  http://digital.NI.com/public.nsf/allkb/990508969805A7C086257619007189E7

  The section deployment of Variables shared in a real-time (RT) target running Headlessly is downstairs.  Because you are connected to an HMI PC, you should be able to use the library to deploy feature of the PC code targeting the cRIO.

  Usually, it's a faster, more scalable solution to replace your shared network Variables with a stream of network dedicated to the HMI and another for HMI - RT EXE commands.  You can send complex structures such as a cluster or even define the message as a cluster of enum and variant type to be able to use the Enum to convert the variant correctly according to the Enum value.

• There is no chance to install a standalone engine shared Variable of EVS?

  Hello!

  I wrote a small application that reads the values of a NetworkVariable created on the local computer. The address of this variable is something like \\127.0.0.1\System\test1

  That I can see, I can use this type of variable (I mean System -based) that if I installed an EVS (by Measurement Studio). But to install Measurement Studio, I need too Visual Studio...

  There is a way to work properly with NetworkVariables based on a system without having to install everything as I said before? AES is responsible for the correct operation of NetworkVariables? In this case, is there any chance to install a standalone engine shared Variable of EVS?

  Thank you!

  I found the solution to help NI MeasurementStudio 2008:

  Server deployment

  In this scenario, you must deploy the motor Variable shared to another machine that plays the role of the server. To deploy the shared Variable engine, you must run an installation on the target computer. The required Installer is installed with Measurement Studio for the [InstallDir] \ Redist\NINETVARSERV folder.

  You can view all the command-line options to run the installation program with setup.exe /? . Command line options, you can choose to run the installer in silent mode.

  You can use the Variable Manager to create and configure network on the server variables. The variable Manager is installed by default. To run the Setup program without installing the Variable Manager, run setup.exe /prop VARMANEXCLUDE=1 command. To run the installation program of engine Variable shared in silence and without the Variable Manager, run setup.exe /q /acceptlicenses yes /prop VARMANEXCLUDE=1 command.

• published RT cRIO-9030 with network-a project of shared variables cannot communicate with host VI when compiled and deployed as executable startup.

  I have a project including a VI RT running on a cRIO-9030 and a host VI running on a desktop computer.  The two programs communicate via shared variables that are hosted on the cRIO.  As shows, when I run the screw of the project, everything works as expected.  When I compile the RT VI in a start-up executable can deploy for the cRIO, as well as the libraries of shared variables (the record of support in the build specification-oriented), I am unable to connect to the executable running in real time.

  

  I have 'Disable Autodeploy Variables' checked on the cRIO target, if I no longer get the prompt to stop the currently running application to deploy the variables.  The host VI opens and appears to run, but has no connection with shared variables (data does not update).  Compilation of the host VI as an executable file and it works outside the project result in the same behavior.

  I read some relevant posts / knowledge base articles related to this problem, but still can't seem to find a way around it.  I note a number of articles on the series in double bond of variables, but this is in contradiction with my possible behavior for this system: I finally have a number of cRIO controllers identical all runnning the same executable RT and want to be able to have a single host VI which allows the user to select from a list of available controllers (using the screw system configuration) and extract the host name of the controller selected, that would be later used for programmatic addressing of the variables on the host of part VI.

  In any case, I want to start with the simple fact of being able to get that first controller running without an open connection to the RT VI project.  With the deployed executable start, I checked via programmed behavior of LED application of the RT and FPGA are running on the cRIO.  The problem, I think, has to do with shared variables, but I'm not sure where to go from here.  I want to connect to RT executable running from the VI to the host (in project) to verify that the compiled executable of RT works as expected and then the subsequently compile host VI in an executable that can be run from any desktop on the local subnet.

  Thoughts?

  It seems that the error has now been corrected.  There were three things, I changed: the file startup.aliases in the startup on the target directory (Home: / lvuser/natinst/bin) put in 'localhost' as an alias for the controller.  I changed it to the IP address of the controller.  Then, I got some features of IO files in my application RT relative paths using the path obtained by the 'current path VI' VI.  As this path changes according to the location / delivery system, I had to create a VI that has used the Application property: type with a case properly structure band / build railroads desired regardless of the runtime system data files.  This may have broke my RT request.  Finally, I got a property node in one of my RT SubVIs, who attempted to change an indicator in the Subvi, which is not taken care of in an RT compiled executable.  I can't do this for debugging purposes somewhere along the way, but in any case, I removed it, and after a recompilation and the deployment of the executable of RT, everything seems to work as expected today.  The host VI on the desktop can connect to the application of the RT project, and when it is compiled into an executable file, which also works.

• Are published network shared variable write & read Atomic actions

  Hello

  I have a very basic question about shered (published network) variable.

  I think I know the answer already, but since I couldn't find in my documentation, I thought that it is more prudent to request...

  Are reading and writing on a shared variable of stocks Atomic?

  To be more precise: on my target real time I create an array with data (each element being the configuration item or a cluster containing name, value, and type) and when the table is finished I am this store in a published network shared variable.

  On my host (Windows), I'm voting (in a loop) until the table contains at least 1 item, when this is true I'm parsing all the elements in the table.

  Is there a chance that, reading of the shared variable, the table contains a subset of the original painting on RT target (i.e. the action of reading takes place while writing is still ongoing).

  Or is the action of reading delayed until the write is completed? (i.e. both write and read actions are atomic even over the network)

  I think the latter is true but not could find no evidence in the documentation.

  Kind regards

  SoC

  Hello Rob,

  Yes, you can access the entire value, data type - you use both. For the table data type, the integer value is actually the full picture. So, Yes, you can see reading and writing as Atomic actions.

  But, on the other hand, you can lose data if the RT system rewrites the variable before the host had the time to read. To avoid this, you can enable buffering for the variable. See the following links for more information:

  http://www.NI.com/white-paper/4679/en

  http://zone.NI.com/reference/en-XX/help/371361H-01/lvconcepts/buffering_data/

  Finally, you can also activate a FIFO RT on your target RT if you need to send data through the variable in a deterministic section of the RT. See also, more information:

  http://zone.NI.com/reference/en-XX/help/370622H-01/lvrtconcepts/rt_projectvariable/

• Shared Variable (published network) communication

  Hi all

  All day I was hitting my head with variable communication shared between RT host and the host computer:

  I basically tried to pass an array of the host of the CR to the host computer. For this I used a published shared variable of network type Array U64. I used this link to help me understand usign shared variable communication

  http://www.ni.com/white-paper/4679/en ...

  I also activated RT FIFO. Now in the city that link the information given on the use of FIFO of the single element or Multi element FIFO

  "By enabling real-time FIFO, you can choose between two types of compatible FIFO slightly different variables: the only element and the buffer insurance program. A distinction between these two types of buffers, it's that the only element FIFO reports no warnings on positive or negative overflow conditions. A second distinction is the value returned by LabVIEW when several readers read an empty buffer. Several readers the only element FIFO receive the same value, and the only element FIFO returns the same value until a writer writes back to this variable. Several readers of a FIFO empty array each get the last value that they read from the buffer or the default value for the data type of the variable, if they have not read before variable. "

  I had read the content above a 100 times, but still I'm not able to get a clear picture of the difference and when to use which option. So I decided to take the text and tried to try something for me.

  I had a loop in the reception of RT who writes arrays of 3 different elements in the 'network published variable shared'. Now when I use the option of multi element with "number of berries as - 2" I am able to read tables separates one by one in the host computer (as you can read a queue in general).

  Now when I used the option of single element for the RT FIFO with 1 UN editable table option, only the last table written in the 'shared variable published network' is read in the host computer.

  This seems absolutely ridiculous as if this is the case, then what is the purpose of creating the "buffer". For testing purposes, I had put the buffer in 5 tables.

  In fact, I have only a single author (written in loop in the reception of RT) and a reader (new looping in the host computer). So I don't know even if I need option of the RT FIFO for the published network shared variable.

  I'm sorry for the long message but I've reached the limits of going around in circles waiting to type somewhere

  I know I made a mistake stupid somewher or it miss me probably a clear simple trick but don't know what it is...

  I request some clarification... In fact I posted a little while earlier today so ... bind - http://forums.ni.com/t5/LabVIEW/RT-Host-to-Host-computer-communication/td-p/2348130 )

  any help would be appreciated

  See you soon

  me

  Hello

  I think that the difference between these two types is clearer by using LabVIEW:

  "

  Activation of the FIFO in real-time

  You can activate the FIFO in real-time to a shared variable since the page FIFO in real-time of the properties of the shared Variable dialog box. Check the box Enable the FIFO in real-time in a deterministic way share data using the one element or several elements FIFO.

  Single element FIFO

  One FIFO shares the most recent value of the data. The shared variable overrides the value of data when it receives a new data value. Use this option when you need only the most recent value. Configure the size of the elements of the array or the size of the waveform for the FIFO buffer, if you select a table or a waveform data type.

  Several elements FIFO

  A FIFO multi-elements implements buffer the values shared by the shared variable. You can configure the size and elements of the buffer FIFO to match the parameters of buffering to use of the Variable page, or you can configure a custom size for the FIFO and FIFO elements.

  Note  For single item both multi-elements FIFOs, if the variable contains data table or a waveform, you must configure the size of the elements FIFO equals the size of the data to share. If the network buffer both the RT FIFO are enabled, the network buffer should be at least as big as one of the elements of FIFO. Sharing data smaller or larger that the specified length results in a memory allocation which affects determinism.

  Note  Waveforms contain variant of varying size that are not compatible with real-time FIFO. Therefore, if you enable the FIFO in real-time on a shared variable that contains the waveform data, the item variant waveform data does not transfer.

  "

  http://zone.NI.com/reference/en-XX/help/370622K-01/lvrtconcepts/rt_projectvariable/#Single_Element_F...

  ' Hope this helps

  Aurélie

• Support of the shared Variables in the third part XP embedded based of PTC?

  I sent a request in an embedded XP touch function (third party). The application works very well, but hosted on a RT (sbRIO Board) shared variables are not getting updated in the app on PTC

  1. the PTC is part of the project as a Windows XP Embedded Touch Panel

  2 NI TPC Service has been installed on the PTC and the application can be deployed remotely from the PC development via ethernet. (Where network connections and communications are OK)

  3. using distributed in the development computer systems manager, I can see that the shared variables are getting updates on the network

  I think that the problem can be solved if the following programs are installed on the TPC

  A. Support for variables that are shared for XPembedded

  B. shared Variable engine

  I tried to install the support of variables shared Program Files > National Instruments > Labview 8.6 > PDA > utilities > Variables > x 86 - but I get an installation error "cannot find the application for the Pocket PC applications Manager.

  Shared variable engine was installed from the ve220 folder. The program is installing. But the engine Variable is not start Control Panel > administrative tools > Services, Xpe, the service is stopped and cannot be started. When I try to start the service, I get the following error on PTC

  "Cannot start Service engine of National Instruments Variable on the local computer."

  Error 1053. Service has failed to demand launch or timely control.

  Please suggest solutions to the addresses above or another of the following:

  1. support of variables shared for XP built-in PTC

  2 Installer engine Variable shared.

  Thank you

  Krish

  Problem solved!

  Update for interested people working on XP Embedded PTC

  Just to ensure that shared Variables were indeed accessible to the TPC, I wanted to install Distributed Systems Manager 8.6 on the TPC. However given that the TPC was only 1 GB of DOM (disk on memory) and with all the software that I had tried, there remained only a few megabytes on the system. I had to add an another DOM of 2 GB.

  All products in the Installation went well, with the exception of the Logos NOR (Version 5.0). Logos OR installation has failed repeatedly.  I tried to install NI Logos separately, with the same results. Then I had this intuition that NI Logos had anything to do with the question.

  Then, I downloaded the new version of NI DSM 2009 SP1. Even if it were to settle on any fresh system without Labview, the installation would not proceed beyond the stage of configuration. I tried to install NI Logos of the folder on the download of new products separately and it worked magically!

  Once the new Logos (Ver 5.5) installed, the Shared Variable engine starts automatically and the shared Variables are finally unleashed - free stand up and shine! I thank Almighty God!

  On the lighter side, come to think of it - to run an application about 400 KB, we need NEITHER of Run Time, XP embedded, DSM, Logos...  (around 900 MB). Can make us everything simpler?  Invite your comments...

  Thank you

  Krish

• shared - variables multi-network

  Hello

  I have problems of publication of multiple variables shared in a network configuration to the correct network. (NIC1, NIC2, wireless)

  I followed the info in Spreading of Variables shared for a specific network adapter

  For a Windows-based system:
  If one does not already exist, create a file in the C:\WINDOWS directory named logos.ini and add the following lines to the file:
  [LOGOS]
  ServiceBindTo=XX:XX:XX:XX:XX:XX
  where XX:XX:XX:XX:XX:XX is the MAC address of the Ethernet card to want to bind to.
  

  Right-click on My Computer within the LabVIEW Project Explorer, click on Properties. Under the General tab, click the Specify Custom Address checkbox, and enter the IP address of the network card that the shared variables will be deployed to.
  

  but it comes to 8.2.1 - is still topical for 8.5?

  After these changes my shared variables always deployed to the default (wireless)

  I am running XP on the computers and LabVIEW 8.5

  Hello Al,.

  I think you may need to change your default interface card just.

  Here is an article that should help you further:

  http://digital.NI.com/public.nsf/allkb/FB4B94AE226BEA2986257559006D0FF1

  And also, point number 8 on this refers to a similar route of troubleshooting:

  http://digital.NI.com/public.nsf/allkb/6E37AC5435E44F9F862570D2005FEF25

  I hope this helps.

  Let me know if the problem persists.

  Kind regards

  Michael S.
  Technical sales engineer
  NEITHER UK & Ireland

• Why it takes so long to open a connection to a shared variable, the first time?

  Hello

  I have an application to large scale developed with LabVIEW DSC, which covers multiple computers on a LAN.  In one of the VI I open variable connection shared by using the "open Datasocket' VI.  I notice that after restarting my computer and execution of this VI into the source code (I have not tried with an executable file yet) it takes about 20 seconds to get a successful connection to a variable share located on another computer.  The later 'Datasocket Open' claims the same computer to the same shared variable takes much less time, about 100 ms.  I reproduce this with 3 different computer, so the behavior seems to be reproducible, but it's not to do it every time but very often.  This scenario may occur also when I did not open a connection to another computer for awhile.

  Anyone have this experience? Is there something I can do all this to avoid this 20 seconds delay problem? Anyone have an explanation?

  All of my computers running Windows 8.1.  I'm using LabVIEW 2012.  All my firewalls are 'off '.

  Thank you

  Michel

  Here is a picture of my open VI.

  Recently, I did this for another client. You can emulate a timeout (and actually connect faster) by using the function "open in background" and then checking the variable.connected? property.

• Shared Variable deployment error

  I need to use Variables shared in my code, and when I try to run the code I get the following error.

  My computer deployment
  Ventilation Library.lvlib\\169.254.192.23\Ventilation library of deployment deployment has failed (error:-2147220712, MAX: internal error (Hex 0 x 80040318): the customer has failed to connect on the server configuration, perhaps because the server is too busy or encountered an error of communication.) Note: the steps that you did which led to this error and contact technical support).
  Completed with errors of deployment

  The code was working yesterday with shared variables, but it won't deploy today and I can't imagine any changes that I made to do this. I tried to run the code on my cRIO and the PC. I have used amd 2015 2014 and I get the same error on all.

  Any help with this problem would be great.

  What is the IP 169.254.192.23? It looks like an auto-negotiation-to-peer (e.g., crossover) connection IP or the IP address of your computer on the network?

  Is the library with shared variables located under 'my computer '? If you right click on 'my computer' in the project - he shows here? IP address you think it correct?

  If you check the custom address 'specify' and put 127.0.0.1 (loopback IP address), it works?

  I also look in Windows Services and verify that the shared Variable service (and other services OR that it requires) are running.

• CompactRIO RT (:-65589) error code: error or warning occurred when writing the following shared Variable)

  Hello

  is anyone know this error Code:-65589?

  This error says:

  Shared in environmental_logger.vi variable
  This error or warning occurred when writing the following shared Variable:
  CompactRIO Target\Mod2\DO1 \\RT
  \\localhost\Mod2\DO1

  My cRIO9073 has 3 modules:

  MOD1: 9203 HAVE,

  MOD2: 9472 DO,

  Mod3: 9265 AO.

  When I delete all States and run only the first "init" State where I put DO0 = true and DO1 = false, I get this error. What could be?

  I think we need more information about your project - you can take a screenshot of your project LabVIEW RT target and the location of the shared variables? What is the configuration of the shared variable? Do you use the cRIO Scan Engine or FPGA (or both?)? How you deploy your library of variables? You should also zip to the top of your project and join, if you can.

  Here are some articles about the possible causes:

  http://digital.NI.com/public.nsf/allkb/C32368835ADAEE19862578500067A8C4

  http://digital.NI.com/public.nsf/allkb/7B52091D2FFA01EC86257C32005DF935

• Shared variable of subjects with the executable in real-time

  We have a PXi target running Labview time real 8.5 and we use a series of shared variables for communication between the target and the client software. The code was developed (and used) in the last 2 years, and presented no problems with the shared variables when they are deployed since the Project Explorer (for the target and the laptop based client software). However, when you try to run an executable version on the system time PXI real target of exactly the same engine code variable shared seems to fail during the initial loading. Since it is an executable, it is difficult to display errors, but it seems that the accident occurred at the beginning of the program when we try to initialize a number of shared variables. Sometimes it loads but probably only 10% of the time. When you plug the tool to debug for code and restarting the executable, runs without any problem. However, once we managed to capture and error (error-1950678982 the shared variable client side read buffer is full).

  I checked a number of messages in the Knowledge Base (e.g. how to deploy Variables of a compiled executable shared network?), but it still has not solved the problem. Thoughts and suggestions?

  Adrian

  I tested it for a few hours now and I can't make it fail again. The big difference in my implementation was to use your suggestion, and no wire the error cluster through the method since the error it generates caused a number of questions later. So let me summarize the final configuration that seems to work then:

  -during the execution and executable on a target time real 8.5, startup not connected to a client. Library of shared variable hosted on the target and should load by itself.

  -J' added a flat structure sequence on the vi 'main' (top of page vi executable) with a node (as shown above) Invoke method in the first structure with a timer to 10 seconds and the rest of the code in the second part of the structure. The shared variable library has been copied to the target in a data directory and the path provided to the method (the same way as above) and the IP address is that of the target.

  I discovered that it takes about 8-9 seconds for the shared variable engine and library to start (I don't remember is that past exactly that) and it is important to wait this time to initialize shared variables or the behavior is unpredictable. The method always generates the error 1043 (function not supported) but I simply ignore it now, and it seems to work.

  Thanks for your help! I will let you know if there is some instability in the future, but everything looks good from here.

• Shared variables, analysis engine and multiple targets

  I'm looking for some general tips on my LabVIEW project structure.

  The project consists of a laptop with LabVIEW, a connected joystick and a CompactRIO connected via ethernet. I ran the cRIO mode Interface FPGA, but a change in some things causes the project to have be moved to scan mode.

  From now on, the code on the portable computer updates the shared variables on the cRIO and bed from the variables shared on the cRIO for surveillance. I want to shared variables on the cRIO because he will also need to work without the connected laptop. Before moving the cRIO for scan mode, I found that I had to first run the code of the laptop and then run the code cRIO, or shared variables would not release properly. Now that I spent to scan mode, I have to run the code cRIO first, and even then the shared vars do not properly communicate for more than a few seconds and are well laggier.

  My ideal project solution is a system that can operate with or without the connected laptop and obviously do not have these questions shared variable. I would like the autostart code on the cRIO and ask the user to execute the code of the computer laptop, if necessary, but in the past, it doesn't seem to work with shared variables.

  I'm really confused about why this is happening. I hope I explained my problem well enough. I really don't want to display the entire project here, but I can email to people if they are willing to take a look. Thank you for taking the time to read this.

  I'm under LabVIEW 2010 SP1 with FPGA, DSC modules and robotic in real time. I have the updated Feb 11 driver and NOR-RIO 3.6.0 installed and completed all updated on my RT cRIO.

  I do this kind of thing all the time...

  Move all your NSV libraries on the cRIO.  Of the project, you must deploy on the cRIO and then they are persistent until you reformat.

  Your windows GUI application, you can set static NSV tags on the block schema or use the API SV dynamic R / w.  Also you can bind GUI controls and

  indicators directly to the NSV cRIO (it's what I do) also I create a library of 'mirror' in the PC HMI that is linked to the library of cRIO.  This library has DSC Citadel

  data record enable and automatically records the historical traces of all my important data - very nice.  Libraries hosted PC can be set to autodeploy in the version of the app.

  the project also has an option of autodeploy to the development environment that normally, I turned off.  If you have a PC at the cRIO binding configuration so be careful

  on any kind of autodeployment because this will eventually force the cRIO app stop when you deploy.  To work around this problem, you can use the PSP (IP address rather than project binding

  process name) and use of the DSC deploy library s vi in your HMI application.  Once you use the scan engine, you can use the app DSM (Distributed System Manager) to view, DIF and

  each of you IOV and NSV graphic on your network.

• RT target does not read shared variable hosted by host

  Hello

  I just started to move my LabView application to a system of RT, and I came up with a problem. When I host a shared variable network-published on the RT target, I can access through vi running on the target and the host (which is good!). However, when I have this host on the host variable (such as by simply dragging on 'My Computer' in Explorer projects or all create a new variable), the vi running on the target RT is not read.

  I wonder if there is a problem with my installation of LabView, or if there is some step I'm missing. Any suggestions would be greatly appreciated!

  My host is running Windows 7 x 64, with LabView 2009 SP1 32 - bit. The objective of the RT is a real-time OS-powered desktop PC. I have attached a very simple project to illustrate this problem: I start 'Target VI' and 'Host VI' at the same time. On 'Host VI', I change the values of the two shared variables: 'hosted host' and 'target hosted. Only the changes made to the target "hosted" appear on the 'target VI'.

  Thank you!

  Andrew

  Take a look at this link (software configuration and firewall hardware to support National Instruments products) and this link (configuration of firewalls and routers network address translating shared Variables) to see if this highlights exactly what you need to explain in your application regarding the definition of the firewall exceptions.

  David has.