Mark Balla

QUOTE(PJM_labview @ Oct 15 2007, 04:23 PM)

This is still a little bit too much work and is against my work flow.

I think, for my use case, I would like a tool that auto connect to the connector pane, given the relative position of controls.

So I would position my control the way I want (no grid), then run the tool (which will attempt to connect doing its best effort, following a few simple rules). It will default to the 4x2x2x4 (4815) connector if no connector selected, else use the existing one.

But this is still a very nice utility :thumbup: (I might even use part of it to write my version of it).

PJM

QUOTE(JDave @ Oct 16 2007, 10:22 AM)

QUOTE(robijn @ Oct 17 2007, 04:20 AM)

I was going to hold off and wait until I had this perfected and I didn't want to hijack the thread.

But with all the discussion on this topic that I have been working on for the last 2 years and JDave mentioning my old fixer, I can't resist showing what I have currently.

This is the 8.2 version but I have 7.1 to 8.5 if you want them.

The three items go in your LV project folder and FIX SUBVI is selected from the tools menu.

The Basics go like this

Start the program

It will open and then minimize.

create a subvi arrange controls on the FP so they correspond to how you want them wired on the connector pane

Select all the controls that you wish to wire to the connector pane

Press CTRL-Shift-Spacebar

the Fixer will popup

Select a Pattern

Press "Wire By Arrangement"

the connector pane will be wired

Press "Arrange & Cleanup"

The FP will be squared up, Labels will be arranged and changed based on settings, Prompt for save, Icon editor called, and documentation editor will be called.

The subvi will also be relinked. (so it is not greyed out in its callers)

Fixer will minimize until next time.

Here is a brief video of how it works. http://lavag.org/old_files/post-584-1192643456.swf'>Download File:post-584-1192643456.swf

One minor issue is it tends to bog down with large projects 600 or more vis in memory. This has to do with finding the active vi.

Any feedback would be appreciated.

There is a lot more to it but I will save that for later.

this will eventually go in the CR once its a little more polished.

Mark

Sorry to be the bringer of bad news but there is a problem with your code.

As the team member responsible for this CR submission I would normally do this by pm but since you started the discussion here I need to warn every one there is a potential crash and I don't want anyone to lose any code because of it.

If you call up the auto connector pane vi and purposely or accidentally try to move one of the box decorations LabVIEW will crash. See video.

Download File:post-584-1192513096.swf

I do have a few additional suggestions aside from fixing the crash.

How about redrawing the decoration boxes when the scale or pattern is changed.

Also it would be nice if we could move the boxes to the controls and have them auto wire.

QUOTE(Michael_Aivaliotis @ Oct 5 2007, 04:37 PM)

Ya, this is a great feature in 8.5 eh?

How did you get LabVIEW to do this and does it work as expected?

QUOTE(jaegen @ Aug 21 2007, 01:05 PM)

Just in case anyone (like me) is too impatient to wait for CDs in the mail, the device driver set for LabVIEW 8.5 ("August 2007") is now available for download from NI.

Full device drivers set (1579 MB): Here

NI-DAQmx only (789 MB): Here

All others: See Here

Jaegen

Thanks jaegen,

I've been waiting for these so I can load 8.5 on my current test machine.

It was great meeting you at NI week.

QUOTE(h1voltage @ Jun 22 2007, 12:43 PM)

I have been searching all over the net for a good command line ISO mounting utility similar to Microsoft's unsupported utility "Virutal Mount" that I can call through LV. Does anyone know of a good method for mounting ISO image in LV, through the command line or otherwise?

Justin goeres. Just recently added his LVOOP ImageMagick Interface

to the CR.

DESCRIPTION:

This library provides an LVOOP-based interface to the powerful cross-platform ImageMagick image handling utility suite.

It supports all of the ImageMagick utilities and almost every command-line operator (over 200 of them) with support for custom user-specfied operators for the edge cases.

Several examples are included that demonstrate basic text & image creation, composition, and conversion in and out of LabVIEW (including VI icon creation).

Now thats the best Omis looking, goat calling, fife playing, hill billy whisteling rock and roll I ever heard.

QUOTE(denisetucker @ May 14 2007, 10:06 AM)

I would like to automate something I end up doing fairly routinely...adding a flat sequence around some code and tick counts to determine how long a vi takes to run. After looking at Gavin's vi's (Thanks, Gavin!), I've determined how to add the sequence structure, but can anyone give me hints on tacking in the tick count and having it be _in_ the sequence frame?

Thanks, Denise

If you don't need a permanent solution them I would recommend using a custom probe that tracks time.

We talk about them here

here is a in BD inline timmer that can be use instead of the sequence option.

http://forums.lavag.org/index.php?act=attach&type=post&id=5863

http://forums.lavag.org/index.php?act=attach&type=post&id=5864

QUOTE(jbrohan @ May 13 2007, 10:51 AM)

Hello

It seems that the first steps are the hardest. I have a LV 7.0 setup on a new computer and I cannot get it to communicate to FP1000 (Yes I'm old fashioned but these units are GREAT!)

If the Firmware is out of date is there still some communication? Or does it sit there dead until I reload the firmware?

FP last used with LV 5.1 now I'm using LV 7.0. The new FP just came from NI but I'm using the FP 4.0 software, not the latest version that came with it!

Yours Sincerely

John

I would recommend that you get it working in MAX first before you start using LabVIEW.

I did a project about 6 months ago where I used the Latest FP drivers with LV7.0 using a FP 1601 over Ethernet.

QUOTE(Aitor Solar @ May 13 2007, 10:27 AM)

I'm sure somebody gave a way for calling programmatically the icon editor, but now that I need it I can't find it . Does anybody remember? Thanks.

Saludos,

Aitor

Adam Rofer mentions it here

Here is the vi I use.

The neat thing about using this method is that it works the same as if you double clicked on icon of the vi.

So my editor or any other custom editor work using this vi.

http://forums.lavag.org/index.php?act=attach&type=post&id=5855

http://forums.lavag.org/index.php?act=attach&type=post&id=5854

For those that are using my icon editor or other home made editor using the lv_icon.vi option

There is a LabVIEW LOCKUP problem when trying to edit a sub pallet in the pallet editor.

If you open the pallet editor.

http://forums.lavag.org/index.php?act=attach&type=post&id=5754

and then try to edit a sub pallet menu icon

http://forums.lavag.org/index.php?act=attach&type=post&id=5755

Nothing happens.

The icon editor is running in the background but it is somehow being suppressed by the pallet editor.

If you are using my editor or you have set the lv_icon.vi to a non modal state then there is a work around.

for Windows press (CTRL-Space-x) and the editor should maximize and work normally.

If the icon editor is set to a modal or floating state then you are out of luck.

I was unable to get LabVIEW back without the 3 finger salute (CTRL-ALT-DELETE)

By default the lv_icon.vit and Sample_lv_icon.vi are set to Dialog which is modal.

http://forums.lavag.org/index.php?act=attach&type=post&id=5757

So if you are going to create your own icon editor I would recommend setting the Windows appearance to default.

http://forums.lavag.org/index.php?act=attach&type=post&id=5758

I have reported this issue to NI.

My thanks to tcplomp for finding this bug and the work around.

QUOTE(Stevio @ May 4 2007, 11:54 AM)

Hi guys, girlz

Does somebody know if it is possible to autosize my frontpanel to the size of my controls, indicators that are visible?

Greetings

I have a vi that does this I posted it here

I'm not sure what version it is in so here is the 7.1 version

http://forums.lavag.org/index.php?act=attach&type=post&id=5737

QUOTE(Omar Mussa @ Apr 24 2007, 10:38 AM)

I just finished the first phase of a project where I'm using 15 different LVOOP classes and I thought I'd share some of what I learned. I've been using LV 8.20 and NOT upgraded to LV 8.2.1 yet, so hopefully Tomi has helped AQ figure out most of the issues that have come up for me - in fact I don't intend to write about the bugs in LVOOP here at all. (I do plan on upgrading to 8.2.1 right away to see what happens now that I've reached my milestone.)

Hey Omar,

Great thread,

Can you elaborate on methods or patters you found useful? I’m curious if you were able to keep your OOP as a by value paradigm or were you forced to wrap them in a queue in order to protect and pass the data between loops.

One of the biggest drawbacks that I find with OOP is the difficulty of testing public Vis. Because the object data is not visible or settable it becomes difficult to inject data and see the results. Were you able to come up with an alternative way to test Publics.

Thanks

Mark

QUOTE(i2dx @ Apr 23 2007, 03:03 PM)

I found an other remarkable video:

Ok so what is the answer?

QUOTE(AdamRofer @ Apr 12 2007, 12:51 PM)

From what I can see, you're stuck with creating your own editor.

Use the properties VI.VI Description, VI.Help:Document Tag, and VI.Help:Document Path.

Don't forget to save your VI with the method VI.Save.Instrument before closing the reference.

Of course, someone else might know how to pop up the LabVIEW VI Properties dialog, but I can't find any methods that do this.

I was hopping it was one of those vis buried deep in the vi llb somewhere. So far I haven't had any luck locating it.

Does anyone have a good method to call the Vi properties dialog page programmatically.

I’m working on an automated documentation vi and would like use the built in LV documentation editor and not have to create my own.

http://forums.lavag.org/index.php?act=attach&type=post&id=5478

QUOTE(martin@aerodynamics @ Jan 26 2007, 05:08 AM)

Customized Color Box....

http://forums.lavag.org/index.php?act=attach&type=post&id=4779

(will be implemented into my Icon editor soon...

Actually the transparency is made by "overlaying" all 3 Icons (not just BW) ("256" Colors, 16 Colors, and BW)...

So if on the border of the overlayed Icon is white, then will this part showed as transparent....

In the default LabVIEW ICON Editor, it is not possible to make a complete transparent Vi.

But if you set the ICON programatically, you can make invisible Vi's...

(the invisible Vi's ar only shown in the Vi- Hirarchie, so you can wind up somebody )

Martin

Can you post the vi or control you used to generate this picture. I am also working on updating the color picker on my icon editor.

QUOTE(vaimaro @ Mar 23 2007, 02:49 AM)

Hello,

I want to ask is it corect to use numeric controls with "value change" detection in event structure?

My task is is to make a program which goes to the case where hardware configuration paramters are after user changes values of numeric controls. For example, user changes Amplitude or Frequency (using dial) event structure detects this activity and chooses "ReConfigure" case, where new parameters to hardware are sent.

The problem is that instaed of one event generated after dial realese, I get many events (2...4) thus "ReConfigure" case is used 2..4 times in the sequence.

I have never seen examples where numeric controls are used to generate events. Thus maybe it is not correct usage of event structure with numeric controls, only buttons should be used?

Thank you,

Vaidas

Here is a method I use to solve this type of problem.

On an Value change event it sets a flage and starts a delay timmer. It waits until the slider control has not change for a specified amount of time.

I have tried to use the mouse up event but found it would not be detected if the mouse was moved off of the front Panel.

hope this helps.

http://forums.lavag.org/index.php?act=attach&type=post&id=5277''>http://forums.lavag.org/index.php?act=attach&type=post&id=5277'>http://forums.lavag.org/index.php?act=attach&type=post&id=5277

QUOTE(polyplay @ Mar 15 2007, 05:13 PM)

Open_AddDev_Run_Read@ controls via ActiveX a simulation from CANape. This simulation uses event structure to trigger a read or write process on value change (it cannot be run if you do not have CANape installed on your computer - but this is not important).

With WriteReadCANapeVI I change the value of the controls in the previous VI, but the event structure does not react on value change in this case.

How this works? Any idea how I can fix this?

Thank you.

Writing data to the terminal does not fire the Value change event.

The easiest way to fire this event is to write data to the Value(Signaling) property of the string indicator.

http://forums.lavag.org/index.php?act=attach&type=post&id=5206

http://forums.lavag.org/index.php?act=attach&type=post&id=5208

QUOTE(Mikkel @ Mar 15 2007, 04:01 PM)

I may be overoptimizing, but calling a sub-VI every iteration of a loop to find out if the loop should terminate just feels wrong

-Mikkel

I would say you are over optimizing.

In my world saving a programmer's time is a much higher priority than worrying about a few computer clock cycles. Most of the time with a modern PC you will have plenty of cpu time to spare. I doubt you can say the same about a programmer's time.

Writing the same code over and over to do the same thing. Now That is just WRONG.

QUOTE(Mikkel @ Mar 6 2007, 02:31 AM)

I would love for LabVIEW to support a 'break' operation in for loops (the lack of this feature is actually one of the (few) things that annoys me, when coding in LabVIEW).

This way, you would elegantly be able to iterate through an array until some condition is met, and then exit the loop.

Yes, I know this can be achieved by using a while loop, but not without first getting the array size, and making the 'compare with i' logic inside the while loop (and enbedding the while loop in a case, to handle if the array is empty).

-Mikkel

I use a simple Stop loop utility that I keep in my user lib it allows for several stop loop contitions and also has an output that tells why the loop stoped. http://forums.lavag.org/index.php?s=&showtopic=2710&view=findpost&p=9584' target="_blank">see here

Check out this post. It shows screen shots of how to make a compact icon

I am now taking nomination for the application that is to be modified by participants in Lava

I forgot to mention an idea I had and today's post to this thread reminded me...

Everyone talks about keeping the project small. Suppose the challenge was this:

Some LAVA zealot creates a simple app that does XYZ. The challenge is simply to add a feature to the app. Any feature. This way a person can bite off as much or as little as they choose. Competition is judged on best feature added. The general framework already exists, so there's less of the "blank diagram syndrome". Maybe there's a cool bit of UI that another programmer could convert to an XControl. Maybe the program needs a faster core algorithm. The options are wider for what could be worked on and there's less of a "this is the right answer and if you haven't gotten to this point then you aren't done" which tends to make for long hours of programming to hit a specified target.

We could start with any of several items in the Code Repositiory.

This would take us away from algorithmic challenges -- which depend heavily on programming experience and moments of eureka to solve -- and moves us towards expansion of LabVIEW -- which anyone might be able to contribute to from the parts of LV that they happen to know.

It's time to start working on the next coding challenge. For this challenge I'm going to steer more towards open discussion instead of the behind the scenes committee idea. Personally I would like to see more participation and discussion as opposed to a technically and objective selection process.

Using Aristos' Idea as a starting point Here are my Ideas so far.

• Take a week or 2 to publicly discuss the format and rules.
  
• Next we have a period where we will nominate the application to use in the challenge.
  
• After the nomination time we will vote on the application to use for the challenge.
  
• Like before the submissions will be sent to me and I will give them an anonymous name and place them in the challenge list.
  
• When the challenge is completed we will have a silent vote for the best modification/feature.
  
• If there is a lot of submission We may take the top vote getters and have a revote.
  

Ideas I would like to discuss:

• Does the base application have to come from the CR or should we let people submit non CR applications.
  
• Should the author of the selected application be excluded from the challenge?
  
• How much time should we give for the challenge?
  
• Any other ideas that would make the coding challenge more interesting.
  

I forgot to mention an idea I had and today's post to this thread reminded me...

Everyone talks about keeping the project small. Suppose the challenge was this:

Some LAVA zealot creates a simple app that does XYZ. The challenge is simply to add a feature to the app. Any feature. This way a person can bite off as much or as little as they choose. Competition is judged on best feature added. The general framework already exists, so there's less of the "blank diagram syndrome". Maybe there's a cool bit of UI that another programmer could convert to an XControl. Maybe the program needs a faster core algorithm. The options are wider for what could be worked on and there's less of a "this is the right answer and if you haven't gotten to this point then you aren't done" which tends to make for long hours of programming to hit a specified target.

We could start with any of several items in the Code Repositiory.

This would take us away from algorithmic challenges -- which depend heavily on programming experience and moments of eureka to solve -- and moves us towards expansion of LabVIEW -- which anyone might be able to contribute to from the parts of LV that they happen to know.

I think this is a great Idea. Thanks Aristos your my hero (again).

I've been looking for a way to reduce the complexity while increasing participation and I'm willing to give this Idea a shot.

I'll start a new thread to discuss.

hi ,

is there is any icon for oscilloscope in LABVIEW????

There are some built in ones if you have loaded the NI Scope drivers.