Why does my RT application display "bit mapping 0" about 25 to 30 times on startup?

[FlamingYawn]

I have a Vision application written in LabVIEW RT 2012 deployed on an RT desktop.  When the application starts, either as an executable or from the development environment, the screen displays "bit mapping 0" about 25 to 30 times.  I do use one instance of "RT Debug String" (displaying something else), but I still get the messages after removing it.  My best guess is that it is some debug code left in one of the vision VIs.  Has anyone seen this before or have any suggestions?  It doesn't seem to adversely affect my application, but it does make me a little nervous.

Thanks,

Robert

[Blake-C]

Robert,

Can you post a screenshot of the issue? In what particular instances does this happen? Does this happen with all of your VIs or just your particular application? Does this happen on a non-RT target?

[FlamingYawn]

Through disabling parts of my application, I was able to determine that "imgInterfaceOpen.vi" is writing "bit mapping 0" to the screen 6 or 7 times (I was calling it 4 times).  "imgInterfaceOpen.vi" is a subVI in "IMAQ Init.vi".  I can run "imgInterfaceOpen.vi" itself (not as a subVI of another VI) on my RT target and see the problem.  I'm using IMAQ 4.7.0.

[Blake-C]

Does this happen when deployed on a non-RT target and run as executable? Are you just setting this up or has this been working for a while before propagating this error? Have you been able to use a Camera Link camera with an executable on a RT desktop before without seeing this error?

[FlamingYawn]

I haven't run this on Windows, and I'm not sure how it could possibly happen, as there's no "screen" to print to.

I'm just setting this up.

Yes, I've done this same type of thing in previous versions of RT and not seen the error.

I tried it on a PXI chassis running RT, but didn't have a camera attached, so I got a camera not found error and didn't reproduce the problem.

[Blake-C]

What hardware are you using with this system? Have you configured your RT desktop to NI’s specifications (see http://www.ni.com/white-paper/8239/en)?

[FlamingYawn]

2 Dalsa Falcon 4M30 cameras with NI PCIe-1427 Cameralink frame grabber cards.  Yes, the RT desktop is compliant.

Robert

[Blake-C]

Robert,

I set up a system with a real time desktop target and a camera link camera with a NI PCI-1426 card and wrote a VI using the IMAQ Init.vi but did not see the behavior you are seeing with the display of ‘bit mapping 0’ on the screen. Just to manage your expectations, I want to let you know that desktops configured as Real Time targets with vision applications are unsupported by NI. I went ahead and talked with R&D about the issue and they said that they have not heard of this happening nor do they know how it would be propagated from the IMAQ Init.vi itself. At this point, since RT Desktops are unsupported, the only suggestion I have is to uninstall and reinstall the software on the RT target and see if that changes what you see. But since you say it doesn’t adversely affect your application, this may not be worth your time. I apologize for the inconvenience this may present to you.

[Elmar_NI]

Hi all,

We track this known issue with the CAR number 398174.The monitor message "bit mapping 0" will be displayed on the monitor as soon as you open "IMAQ init".This side effect will not have any influance on the functionality or performance of the board itself. Please accept our apology for the inconvenience. National Instruments is committed to your satisfaction

and to maintaining your confidence in our products.

Thanks,

Elmar

PS: NI IMAQ 4.6.1 or lower will remove the monitor message.

[FlamingYawn]

So is this simply some debug code in the driver that got left in?