It appears you are trying to access an IO Variable on an Ethercat slave. However, from your screenshot, I couldn't tell if you were trying to access the variable from a local machine or a remote machine. If you're trying to access it remotely, you should be able to use a variant data type. The protocol for publishing across the network will automatically perform the data type conversion for you. If you're trying to access an IO Variable locally, you have to use the exact data type of the IO channel in order to successfully open a connection to it. If you don't know what this data type is ahead of time, you can use the DataType property in the Variable property node to programatically determine the correct type.
With all of that said, the error code from your previous post implies the variable wasn't found within the variable engine. If you're trying to access an IO variable remotely, make sure you've deployed all of your variables, and that you've enabled networked publishing. One difference between using the static variable node and the programmatic API is that when using the programmatic API, the variables won't be deployed for you automatically when using the development environment. You'll have to do this manually each time you make a change to one of the variables. With the static variable node, the development environment does this for you since it knows which variables are being used in the VI you are about to run. With the programmatic API, this isn't possible since the actual variable being referenced isn't known until run time.
