04-03-2009 03:40 PM
Please don't use third-party hosting services. Just attach your images to your post.
I'm going to have to guess what you are talking about since I cannot view the images but there is no need for a device wire. Everything is defined in the phsical channel list (i.e. Dev1/port1/line1) and you don't need anything wired to the task in if you creating a new task.
04-03-2009 03:49 PM
Ian,
The task in node for the Create Virtual Channel does not need to be wired. You can either wire a "Task Constant" if you setup and configure a task within MAX or you can specify the device and channel in the Specify Channels node.
03-23-2011 09:15 AM
Hello,
I know this is an old post, but I just came into the same problem.
How can I specify a fixed value. In the old code, only the number 1 is specified into the device port. I'm relating to your comment "specify the device and channel in the Specify Channels Node." Are you referring to the "DAQmx Channel Property Node"?
Thanks.
03-23-2011 02:20 PM
Hello,
I have attached further information of usage of both Config and Write.
The config is using
------------------------------
-Inputs
Device
Device Channel
Port Width
Line Direction Map
-output
task id out
Write is Using
-----------------------------
-Inputs
Task ID
Pattern
Line Mask
-output
task id out
I don't really understand how the DAQmx Create Channel and DAQmx Write translate to these....
Thanks in advance..
03-23-2011 03:02 PM
I forgot to include that this is over GPIB.
Thanks
03-24-2011 01:01 PM
If you have a GPIB device, you should try the GPIB example shipped with LabVIEW. I recommend this one: GPIB-VISA.vi
Notice that the GPIB devices do not use DAQmx VIs, rather they use VISA. You should be able to get a basic example working with your card, and I recommend using that as a model for starting your custom application.
03-25-2011 08:48 AM - edited 03-25-2011 08:50 AM
Hello,
Thanks for the reply!
I guess I needed to explain further. I know how the new GPIB write function works.
However I don't understand the old stuff enough in order to upgrade it.
For example,
I have the values 1,2,4,8,16,32,64 or 128 sent to the pattern port and I have no idea what its doing with it.
Its also setting the line mask to 255 (What's a line mask?). For each call it's also setting the task id to 0.
I need to translate these calls into the upgrade.
Same goes for not understand the Port Config ports.
Thanks..
03-28-2011 11:19 AM
Hello,
Could you explain more about your application? What are you trying to do and what version of LabView are you upgrading from? What is it that you don't understand about the older version calls? Perhaps attaching larger and more descriptive screenshots would help.
Regards,
Joe S.
03-29-2011 07:51 AM - edited 03-29-2011 07:53 AM
Hello,
Thanks for responding.
03-29-2011 08:12 AM
Hello,
So I'm trying to write to a PC-DIO 24 board in LabView 8.6. The original program was written in 4.0, which I had to take to 8.2 before using 8.6.
I don't know what these calls are doing. The DIO-24 user manual doesn't talk about these at all. I do have a DIO-6503 installed on my test computer, but I'm not sure how it will help with anything. Is the DIO-24 board just not supported in 8.6 ???? I don't know enough about the calls in order to create a new function call to the board. I do notice that there are 3 ports on the DIO-24 board and the digital channel calls change from 0,1, to 2 in different calls to this function. The two images I posted is the same function, just changed if its being configured or written too. The intereseting part is that the while loop is never being incremented. So each time the function is called, its passing a boolean array of 00000..
Items in DIO Write and Config I don't understand:
The config is using
------------------------------
-Inputs
Device
Digital Channel
Port Width
Line Direction Map
-output
task id out
Write is Using
-----------------------------
-Inputs
Task ID
Pattern
Line Mask
-output
task id out
Thanks a bunch in advance.