LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

background image problem

Solved!
Go to solution

You still haven't answered my question about the size of the background graphics in pixels. Can you attach the actual jpeg?

 

Also your subVIs have way too many unecessary property nodes. All the colors  and static properties need to be set only once, you can use the "first run?" primitive. All others can be replaced by wires.

 

 

To create a second y axis, you would  right-click the existing scale and select "duplicate scale".

 

0 Kudos
Message 11 of 25
(1,491 Views)

I've attached all the vi in the previous post, the jpg image is 1264x601 with 271kbyte. Do you have seen the other vi? I can't set the color only one time because if you look well you can find that there is a button that simulate the Turn-off of the function generator which set black the color of the text, btw the function generator can run 1000 cycles in few second so the problem i think is not there.

0 Kudos
Message 12 of 25
(1,486 Views)
Solution
Accepted by topic author Silversky

Well, here's a quick partial draft how it should be done with a single graph and two Y- axes. You should really simply your cases. It would be easier to index into an array of settings as I have done in the upper parts (incomplete!)

 

(I have removed the image, but I cannot add it back, so you need to do that.)

Message 13 of 25
(1,472 Views)

Your mod run a little smothe then mine for sure, but when i add the image slow down (but a little faster then mine). The thing that is REALLY strange is that if you open the vi  with the background image the vi run at 10 cycles/sec for example, if you remove the background runa a 100 c/s and if you now re-set the same image the vi run a 50 cycles/Second this is the issue which i'm talking about, it's insane 🙂 Here the image so you can try by yourself .

 

Step to follow:

 

Open the vi with the backround image

Run the vi and look at the speed

Stop the vi

Remove the background image

Run the vi and look at the speed

Re-Apply the same image

Run the vi and blow your mind with the new speed 🙂

0 Kudos
Message 14 of 25
(1,467 Views)

Altenbach can i ask you a question? I'm going to implement the trigger function on my oscilloscope, but i see that the signals don't move they seems already triggered? Is there any reason for this? How can i obtain that the generated signals move on the screen before the triggering? Thanks

0 Kudos
Message 15 of 25
(1,436 Views)

Sorry, I don't understand the question.

0 Kudos
Message 16 of 25
(1,420 Views)

@Silversky wrote:

Your mod run a little smothe then mine for sure, but when i add the image slow down (but a little faster then mine). The thing that is REALLY strange is that if you open the vi  with the background image the vi run at 10 cycles/sec for example, if you remove the background runa a 100 c/s and if you now re-set the same image the vi run a 50 cycles/Second this is the issue which i'm talking about, it's insane 🙂 Here the image so you can try by yourself .

 

Step to follow:

 

Open the vi with the backround image

Run the vi and look at the speed

Stop the vi

Remove the background image

Run the vi and look at the speed

Re-Apply the same image

Run the vi and blow your mind with the new speed 🙂


 

many many years ago there was a thread on this forum where the Q'er was insisting he could get better perfromance *out of ... than what LV could do.

 

In his case he was trying to create the instrumnet control panel for an automobile. The challenge revealed that the big hit to performance was LV attempting to render the FP when there were many over-lapping objects since LV had to resolve all of the stacked object from back to front.

 

The final solution involved tossing the native LV FP objects and rendering the FP using a picture control since in that case there were no over-laps.

 

Christian has already mentioned the over-lapping issue earlier in this thread.

 

If you realy want to get good performance and keep the fancy image options then I suggest you find the example that ships with LV that uses a Picture Control to render a graph. Use you jpg as the back ground and just use the shipping example to draw the graph on top of your scope.

 

Trying to help,

 

Ben

 

* link brought to you coutesy of Tagging. You gotta love it!

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 17 of 25
(1,404 Views)

Thanks Ben for reply, after many hours i've found that the real problem is not my scope-vi or my function_generator-vi this item alone can run at hundred of cycles/second the problem is when the oscilloscope vi open the 2 function generator and all the 3 vi (1-scope and 2-function gen) are on the screen, if i minimize the 2 function generator the speed go up, but if i take all the 3 front panel opened on my screen the entire vi slow down. Is there any solution to that? Thanks for help

0 Kudos
Message 18 of 25
(1,399 Views)

I already told you that the subvis are extremely wasteful with system resources due to excessive and unecessary overuse of property nodes. You need to do similar changes there too.

0 Kudos
Message 19 of 25
(1,397 Views)

Ok then the problem is only the property nodes? The vi alone run very well, i'm trying to low the property node is some way thanks 🙂

0 Kudos
Message 20 of 25
(1,394 Views)