DAMmx8.7.2 Scale Property error code -50352 Memory allocate error?

[HWZ]

Hi there,

When I upgrade my PXI system from LabVIEW RT 8.5 to 8.6 and try to read the active scale property, I got the error code -50352. Are there anyone could help me to fix the problem? I am using the DAQmx 8.7.2. For the details, please see the attachments.Thanks very much!

John

[Wallace_F]

Hello John,

I understand that you've created a VI that is designed to return information about all of the scales in your system.  Is this correct?  I see that you are getting error code -50352 indicating that the memory could not be allocated for this operation.  I would like to know how many scales are in your system.  Are they in a project folder? Also, how many

DAQmx channels are there in your system or project?

Best wishes,

Wallace F.

[HWZ]

Hi Wallance,

Thanks for your help!

In my project, I have 4 AIs, 4 AOs and 7 DIs, 5 DOs.  The scales are not included in the project file but in the MAX remote system. So that the scales can be read with DAQ SystemProperty node on the PXI RT system. In the MAX, I have more than 20 scales and some of them are just dummy scales. The code works on DAQmx 8.7.1 and LabVIEW 8.5.1. 

Thanks!

John

[Wallace_F]

Hi John,

A very similar situation was reported to R & D for investigation (#124672). A potential work around is to remove tasks from your project so that there are no more than 10 total tasks, channels, or scales in your project.  The items that you remove from the project should be created programatically. It would be really interesting to know if the workaround I suggested helps the problem. Feedback on this issue would be greatly appreciated.

Regards,

Wallace F.

[HWZ]

Hi Wallace,

Thanks for that!

In this week, I rollback my system to labview 8.5.1 and DAQmx to 8.7.1f3. This time, the code works under the development system but when I deployed the code to the PXI 8106, the error occurred again and I could not fix it. I also created a very simple project which contains only one VI to create one scale programmingly. In the project, there is no DAQ tasks. The code works fine on the development environment but also failed in the executable. The error code is still -50352. Once the error happened, I could not run the source code properly in the development environment and have to unset the executable as startup, reboot the PXI and then the source code can work. The code is similar to the screen shot I posted here. Any idea or suggestion?

Regards,

John

[Wallace_F]

Hello John,

I think the next logical step in troubleshooting this problem is to try and remove DAQmx from the equation.  Do you have any other real-time targets in your PXI system that doesn't use DAQmx?  Is it possible for you to create a project that builds an executable that doesn't use any of the DAQmx functionality, and deploy that executable to your PXI-8106? If so, I recommend deploying a basic VI to your 8106 that doesn't use DAQmx to see if you get the same error code -50352.  If this error persists despite removing DAQmx from the equation, we can look elsewhere for possible causes to the problem.

Regards,

Wallace F.

[HWZ]

Hi Wallace,

I just built a single loop application with LabVIEW Real-Time Project template and it works fine in the PXI. I also formated the PXI and reinstall all the softwares. The problem still there. Could you please give me more suggestions?

Regards,

John

[HWZ · Accepted solution]

Hi Wallace,

You are correct. The way to fix the error is to delete all the DAQmx tasks in the LabVIEW project explorer and programmingly create the tasks.

Thanks!

John

[geirove]

---

Wallace_F wrote:

Hi John,

A very similar situation was reported to R & D for investigation (#124672). A potential work around is to remove tasks from your project so that there are no more than 10 total tasks, channels, or scales in your project.  The items that you remove from the project should be created programatically. It would be really interesting to know if the workaround I suggested helps the problem. Feedback on this issue would be greatly appreciated.

Regards,

Wallace F.

---

Hello Wallace,

Any chance this bug will be fixed real fast? I have a project that uses a Framework that relies on the **names** of the Tasks created in Project Explorer.

The Framework reads Task Names and Port Numbers from an External XML file: This way the IO Mapping can be done outside the LV program !

This works fine Running on the RT (a PCI PC) when starting the Main VI from the Project Explorer. However, when creating an Exceutable, an NI-DAQmx.ini file is created. When this file is loaded by the RT module, it causes the -50352 warning as soon as one tries to either Create a Task programatically or access a DAQmx device.

Remocing the Tasks from the Project, empties the NI-DAQmx.ini file, and tasks may be created programatically. Unfortunately not an option: It would require time consuming rewrite of the program, and take awy the flexibility in the IO mapping that the customer wants!

This is a show stopper for us on a project where we are hard pressed for time.

A patch / fix would be highly appreciated!.

Message Edited by geirove on 11-04-2008 12:08 PM

[Wallace_F]

Hello Geir Ove,

I regret that the work-around of creating the tasks programmatically is a show stopper for you. The issue has been reported to R&D for investigation.  Currently, there is not a fix for this problem.  A fix may be implemented in a future release of the DAQmx driver, but as of yet, no release date has been determined.

Regards,

Wallace F.