DAQ MX Channel control bug?

[becktho]

Hi all

Yesterday I posted a message due to a problem with DAQ MX (http://forums.ni.com/ni/board/message?board.id=250&message.id=21380).

I also saw yesterday, that if I tried to change the channel using the DAQ MX physical channel control (clicking the browse-entry of the contextmenu) the dialog just stopped but did not close. I now found out that this is just the case, if the control is used in a strict type def. A "simple" type def works. Why?

Would my problem described in the other thread disappear if I changed to a "simple" type def? I don't want to make the modification in the SW not knowing whether it works or not.

Thanks in advance.

Thomas

[K_Dinnes]

Hi Thomas,

thanks for the feedback.

The problem You descirbed is already known. It will be fixed in DAQmx 8.1.

Unfortunately there is no workaround for this issue at the moment.

If You have further questions, please let me know.

Have a nice day

Klaus Dinnes

[becktho]

Hi Klaus

Have you had a look at the thread I linked to?

Would it work if I just use a type def control instead of a strict type def control?

Thomas

[K_Dinnes]

Hi Thomans

Well, it looks like that it will work, if You use a type def control instead of a strict type def control.

I only can reproduce this error, if I select "strict type def".

Thanks

Klaus

[Tom_W_[DE]]

Hi Thomas-

Both controls work correctly whether I use a strictly-typed definition or not.  FYI, I am running NI-DAQmx 8.1 which is released now.  Please update your driver if you haven't already and let us know if you're still experiencing the problem.

Thanks-

[becktho]

Thanks to both of you.

Luckily I'm working on a similar testrig so that I can "test" your suggestions and than take the solutions to the other.

Tom - I am a person who loves a single installer for my programs. Who would it be if I use DAQmx 8.1? When I create an installer script - will the new version be included? Usually I try to cope with such problems rather than change versions of all the driver software.

Thomas

[Tom_W_[DE]]

Hi Thomas-

Are you referring to the ability of LabVIEW 8.0 to bundle additional installers with the actual .exe and LabVIEW RunTime installation?  If so, creating an installer with NI-DAQmx 8.1 from your development machine will definitely replicate the new installer to any systems you deploy to.  You may also be interested to know that with NI-DAQmx 8.1 the size of the bundled installer for NI-DAQmx can be significantly reduced by opting not to include device documenation or support for the DAQ Assistant.  These options are available in the additional installers options section of the LabVIEW application builder.

If I missed the point of your question please let me know.  Thanks-

[becktho]

No, you absolutely got the point.

So I could uninstall DAQmx 8.0, then install DAQmx 8.1 and create just one installer, that includes everything? This would be great, because I rather use strict type defs instead of type defs and if DAQmx 8.1 allows me to use them this is the real solution. I'm already downloading it ;).

Well - now I have another question related to DAQmx:

Is it possible (in a future release) to specify the input signal of a simulated device? In addition - will there be a way to see the output written to the simulated device? This were functions I'd really appreciate.

Anyway - thanks for your help so far. I'll let you know if it works.

Thomas

[becktho]

Hi Tom

I just updated from DAQmx 8.0 to DAQmx 8.1. The problem regarding the behaviour of the DAQmx channel control as either Type def or Strict Type def is solved. As you said, it works now. But now I discovered something similar regarding the Fieldpoint IO Point control. Having this placed twice in a custom control does not work properly. I place one for an input module and the other for an output module. If the control is stored as Strict Type def, the Fieldpoint controls are not browsable properly. And this in FP5.0.

So I'll keep on using it as Type def control. It's a pity because decorations place to group some elements are not updated everywhere.

Thomas