08-24-2007 04:43 PM
08-24-2007 06:29 PM
08-25-2007 01:27 PM
08-27-2007 09:02 AM
As I suspected, it sounds like this is not going to be simple.
We have a team developing our first LV application to control our machines using standard LV controls.
As soon as this application is able to run, we will immediately start removing standard LV controls for custom controls.
Ultimately, our manager wants the application to have a look and feel similar to the newly released i-pod phone.
He has stated that he wants a custom taskbar object similar to what is found in the MAC OS where each task icon expands on mouse over, then returns to its normal state when the mouse leaves.
The main screen will be an animated representation of our machine. We want:
I am here to determine if this is possible in LV.
Can the Picture Control handle this?
If it can not, is there another way to accomplish this (i.e. Write the LV data to a file and have C++ read that data to display the information)? If so, then how would I manage to get a C++ executable to run on the Compact RIO?
Regards,
Joe
08-27-2007 09:08 AM
Can the Picture Control handle this?
"
Yes!
Care should be given to how this is implemented because the mouse over-stuff will require a lot of screen updates. Pixel punching takes time so try to keep the size of objects as small as possible.
I suggest you start simple, post Q's as they come up and watch your performance with every code change.
Have fun!
Ben
08-27-2007 09:29 AM
Wait a minute. Let's back up a bit...
@jp2labview wrote:
...how would I manage to get a C++ executable to run on the Compact RIO?
You want to run this on an RT target?
I haven't looked deeply into this, but the picture control format is essentially a string which holds vector graphic commands or raster data. It is not very efficient and string manipulation which may require intense memory management is something which is tricky in RT systems. I'm not saying it can't be done, just that there are potential pitfalls.
Usually, RT systems are used for RT applications, not for pretty animations. You might find that you are pushing the limits of what can be done.
Then again, you might find that this is relatively easy for the cRIO to handle.
09-28-2007 01:05 PM

Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.09-28-2007 04:06 PM
@jp2labview wrote:
If it can not, is there another way to accomplish this (i.e. Write the LV data to a file and have C++ read that data to display the information)? If so, then how would I manage to get a C++ executable to run on the Compact RIO?
This is just to stress that if there is no time critical elements in the connection between the UI and the main RT system, then there should not be any constraint on the cRIO to handle your system. this can then be easily and effectively programmed with LV.
the way you describe you want your UI is another story tough.
10-01-2007 09:00 AM
I am still hear, I am still reading these posts, and many I take to management for their review. Thanks for all of the input!
Our department seems to be lead by a small number of Mechanical Engineers (MEs). Obviously, they are excited about LabVIEW (LV), because they would not have to rely on the software team to create/modify the code for our product.
I presented Measurement Studio (MS) to management, but each MS license would also require a licensed copy of Visual Studio (VS) installed (our software team uses Borland). The department has made a considerable investment with the 10 LV licenses, and a big reason for doing this was so everyone (software developers and engineers alike) would be on equal footing when it comes to understanding the code. Purchasing additional licenses for both MS and VS would not sit well with management. Further, our MEs would fight it, because they don't want to learn code.
It looks like incorporating graphics into our application will cause us to shoot ourselves in the foot with the performance advantages of the cRIO.
The MEs that convinced our department to buy into LV may not have presented the best options for the department.
So, is there a better way to modify LV controls so that the interface that our clients interact with does not scream "I was made with LabVIEW"?
10-01-2007 09:17 AM
Hi Joe,
I do not think I have read enough of the details of your app to be able to provide a solid outline as to how to proceed.
The main issue I hear in your posting is the learning curve to get up to speed on the custom graphic stuff. If you have a dead-line then you may be well served by getting some start-up consulting help. Check with your loca NI rep to find an experienced consulting group in your area (You want to find Certified LabVIEW Architects, or very experienced Certified labVIEW Developers). They should be able to sit down with you and construct an architecture fro your application and get you started with the fancy graphics (ask them to provide examples of their custom graphic work).
I'll stop there before I violate the "Terms of Use" for this forum. ![]()
Ben