Mark Balla

Certified 9-22-09

Moved to UI Group

We think Robots Rock along with many others

If you want to see a great presentation on robots check this out

NI Week 2009 Keynote

I PASSED!!! I am now a Certified LabVIEW Architect. Woo hoo!!!

Awesome!!

Chalk up one more CLA in Chicagoland.

If you have ever given Aristos Queue a Kudo or been helped by one of his post then here is your chance to give back.

In his presentation Wednesday at NI Week he asked that everyone go to the Idea Exchange and vote for

Tag an XControl as the default control/indicator for a LabVIEW class

All you need to do is click on the link, logon and then click on the star in the upper left corner

Here is the discription

LabVIEW classes are how you create new data types in LabVIEW. But part of being a new LV data type is having a front panel representation. Although users can write XControls for displaying their classes, and they can put those XControls in the palettes, whenever a user of their class chooses "Create Control" or "Create Indicator" for the LabVIEW class terminal, they get the cube display. In order to really add a new data type to LabVIEW that behaves as well as, for example, the Timestampp or the Waveform, there needs to be some way to associate a class with an XControl and say, "This particular XControl should be used as this class' default control/indicator whenever one needs to be built." (To prevent infinite recursion and load dependency problems, whenever you did Create.

I also like this Idea. The main reason that I have avoided classes in the past is because I couldn't see the class data values passing in and out of a class vi.

While you are in the Idea exchange checkout all the other Ideas and vote for your favorites.

NI is going to use this site to help determine future functions of LabVIEW.

For those planning to go to this session on Tuesday @ 4:45 it has been moved to Thursday

This email has been sent to notify you that Advanced Error Handling Techniques in LabVIEW has been moved to Thu, 06 Aug 1:00 PM.Your personal schedule has a conflict with this new time and you have been dropped as a registrant for this session.

For additional questions, contact niweek@ni.com

(888)564-9335

Hi,

Yes I know that it's a complex knob but the device I have to simulate has that kind of knobs. It's used in the avionics to determine if a channel can be listened to or not...

The user of the application will know how this bullshit works xD.

Why would there be two DBLs and a boolean for the output ? I was rather thinkinf of one U8 (values only from 0x0..ff) and a boolean to return the pushed/released state.

Because for now i have to use one push button (boolean) in combination besides a classic knob.

I will check out what is this Xcontrol thing. Sorry I'm a neophyte so don't hesitate to tell me all the things that seem obvious to you.

Here is a quick demo of an x-control I threw together.

There is an issue with changing the value and being able to change the state (Pressed or Unpressd) If you want both operation to be done by a left mouse click.

I’ve thought of 2 way to maybe solve this issue.

The first way would be to create a click zone and when the user is ready to change states he left clicks in that area. The click zone needs to be reasonable distance away from the knob pointer so the proper operation will happen.

The second method would be to use a left click to change the value and a right click to change the state.

I’ve implemented both methods in this xcontrol.

Xcontrols are a bit of a pane to work with if you are new to LabVIEW so I also included the basic code in the demo. Use the best one for you.

Let me know how it works out

Mark

Click and rotate.zip

I am creating a MAP of all the location I plan to visit at NI Week and thought it might be useful to those who are new to Austin.

Feel free to add location that you want others to be aware of.

I created a jing Video showing 3 things (For some reason it won't imbed into the post)

One kudo

One Bug

One Request.

Great RCF

Mark

Submission Approved 7-27-09.

Moved to User Interface group.

Thanks John Great submission.

I look forward to your NI Week presentation

Mark

Name: Generate Palettes

Submitter: gb119

Submitted: 21 Jul 2009

File Updated: 22 Jul 2009

Category: *Uncertified*

LabVIEW Version: 8.6

Version: 1.0.02

License Type: BSD (Most common)

Make this available on the VI Package Network?: Yes

Generate Palettes-1.0.02.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~

Copyright © 2007-2009, University of Leeds, UK

All rights reserved.

Author:

Gavin Burnell

G.Burnell@leeds.ac.uk

Hi Gavin

I am seeing some issues with the 1.0.2 version.

1. With the new CR we are asking that the .zp file also include the labview version EX: Mycode_LV86_V10
2. I am also seeing many issues with conflicts and missing vilib below are some screen shots

It looks like a vilib is missing and that the project is trying to link back to your user lib

Documentation, Readme text, Licence all look good.

I love vugie's design for the t-shirt, but the back is a little out of date since NI has, indeed, freed the imprisoned properties (well, most of 'em). So here's my suggestion for the back of the t-shirt (thanks to justin goeres for the avatars and alpha editing assistance!):

Like last year, it's a play on the NI-Week theme, but with our top posters' avatars - here's a zoomed-in section:

Since we're running out of time, unless there are any strong objections, I'll set the t-shirt up in the LAVAStore in the next few days - vugie's design on the front and this one on the back.

Can we order the shirts Yet?

We're only a few weeks away from NI WEEK.

Submission Certified and placed in the "Remote Control, Monitoring and the Internet" Catagory

Added better error handling and cleaned up some of the BDs.

I think this is read to be submitted to the CR. Can someone let me know what next steps to take or what might needed to get this code into the CR?

thanks,

-John

Hi John,

We are in the process of updating the Code Repository submission process.

Here is a rough draft of the requirements.

LabVIEW Code (Moderators discretion)

• Appropriate level of Documentation
  • including the use of the VI Documentation,
  • Free text on the Front Panel and/or Block Diagram.
  • You don't need to include a novel, but please consider the average level of knowledge of a LabVIEW programmer that has never seen your code before.

  [*]Appropriate Error handling[*]Follow basic style guidelines

  • Minimize wire bends
  • Use the 4-2-2-4 pattern for subvis
  • Meaningful icons
  • Code does not take-up multiple screens.
• Code conforms to stated function
• Code must be useful
  

Zip File

• The .zip file must end with the LabVIEW version and the software version in the following format [filename_LV##_v###] example [Mysubmission_LV86_v100]
• Must contain Organized LabVIEW code
• Must contain Readme.txt file
• Recommended to contain the FP screen shot

• Create a Readme.txt file
• Create a screen shot of your application
• Place the Readme.txt , screenshot and the Organized LabVIEW code in the .zip file
• Name the .zip file as required.
• Go to the LAVA Code Repository Tab (http://lavag.org/ind...p?app=downloads) and click on the “Upload File” button.
• Select a category that best fits your submission and press “continue
• Fill in the file Information.
• Copy the contents of the readme file into the Description box
• Replace any email addresses with –see readme file for contact information.
• Attach zip file and screenshot found in the File Management area.
• Click on the “Add Submission” button to complete.

A Moderator will then be assigned to review the code and if it passes it will then be placed in the Code Repository.

Once approved a support topic will be generated in the CR Forum (http://lavag.org/for...tory-certified/)

Edit MB: I left out an item in the templates added dependencies: 7-7-09

Ok, this is probably me being stupid, but having had my CR entries repatriated (thanks !) I can't find the way to uploading a new version of the file and editing the meta data. The list of "My Files" in my profile has the correct entry but doesn't have an obvious (to me anyway ) edit link, nor does going straight to the CR entry page. What have I missed ?

It's nothing you are doing wrong I verified this issue we will try to fix this ASAP.

Hello Michael et. al.,

Much appreciate your hard work, especially all your data recovery efforts.

I gather that restoration of the code repository contents is still ongoing (I'm particularly interested in the General category)?

Thanks again!

Oliver Barrett

There are still a few left to add. Do you know the name of the CR you are looking for It could be one I still need to put in or It may be in a different catagory.

Name: Mark Balla's Icon Editor

Submitter: Mark Balla

Submitted: 02 Jul 2009

File Updated: 18 Oct 2009

Category: LabVIEW IDE

Version: 2.3.0

LabVIEW Version: 2009

License Type: Creative Commons Attribution 3.0

Mark Balla Icon editor V2.3

October 2009

Author: Mark Balla

--see readme file for contact information.

Description:

This is the second version of my vi icon editor and was created in LV8.2., 8.6, 2009

The purpose is to help quickly create text base icons.

The editor can be used in place of the standard NI icon editor or as a stand alone vi. see instructions.

Instructions: LV 2009

1:Rename the curret LabVIEW 2009 Icon editor LabVIEW 2009\resource\plugins\lv_Icon.vi to a different name so it will not be overwritten.

2: Place the three files (lv_icon.vi, color templates.bin and the folder lv_icon_Subvis) in the LabVIEW 2009\resource\plugins directory.

The next time the icon editor is called LabVIEW will use the lv_icon.vi instead of the standard one.

There is a button on the editor that will allow you to use NI's editor (Old editor not the new one) when a text icon is not desired.

Version 2.1:

Along with the auto drawing and Text compressing from version 1, version 2 has 2 new features.

1: In addition to the 2 color format in version 1 the icon editor now supports a 5 color format (Frame, Header text, Header Back, Body Text, and Body Back). This is the standard frame that many programmers use.

2: In version 2 the last 10 icon color sets are saved in a binary file and are recalled each time the editor is open. These color sets can then be selected and reused.

Version 2.2:

Along with the all the features from version 2.1, version 2.2 has several new features.

1: A new color picker was added. The standard NI color picker has been replaced by one that will only show the legal 221 colors allowed by LabVIEW for icons.

My thanks to Justin Goeres for the idea.

2:Key navigation has improved. The key navigation will only set focus to the text boxes to navigate between boxes use the tab, enter, up and down keys.

My thanks to boone_93 for the idea.

3:Improved UI. The buttons and current and previous icons have been relocated for a more intuitive look. I have also added tip strips to the buttons and history array.

My thanks to ahull for the idea.

4:Random color picker. A random color button has been added to help pick colors.

My thanks to Dave Graybeal for the idea.

5: FP auto centers. The icon editor will now open in the center of the primary display.

My thanks to tcplomp for the code.

6: The ability to read the text in the icon was added. If the icon to be changed was previously created by this icon editor the program will automatically detect the characters in the icon and convert them back into strings. This function allows for small changes like color changes and spelling mistakes to be changed without having to type all the text over.

This one was all mine.

7:Bug with Panel close fixed. When the user presses the x in the upper right corner the editor will shut down gracefully instead of locking up.

I made a avi file that shows some of the new features for Version 2.2 which I posted the support thread.

Version 2.3:

Along with the all the features from version 2.2, version 2.3 has several new features.

1: Icon Sizing and Positioning: Now Icons to be sized smaller than 32x32 by changing the “Rows” and “Width” controls. The icon can then be positioned using the “Position” control. My thanks to tcplomp for the Idea.

2: Static or Auto sizing Icons: If the “Icon Sizing selector is set the Static the icon will only draw the number of row indicated by the “Rows” control. If the selector is set to Auto the icon will adapt to the minimum number of text lines filled in.

3: Selectable Header: The icon header can be removed or enabled by changing the state of the “Header” checkbox.

4: Header and Sizing Information Saved: The header and sizing information are now save in the template files and are displayed at the bottom in the “History” array. The sizing and header settings are shown in the icon text of each template icon the when room allows. The history array now saves the last 50 icon templates to the template file

5: Color Picker Will Save Current Color in History: To get the color picker to save a new color in the color history array click on the “Current Color” box and it will be added the color history.

6: Improved Text Fitting: Text fitting inside the icon has been improved

7: Improved Text Recognition: Text recognition of the icon characters had been improved

8: Other Improvments: all key presses are ignored until the icon is created and text is in the string controls.

Please feel free to give me feedback. This version has benefited greatly from ideas given to me by coworkers and other programmers

License:

Creative Commons Attribution 2.5 License

For LabVIEW 8.2 , 8.5, 2009 Use the "MB Icon Editor_V2.3_LV82.zip" file

For LabVIEW 8.6 Use The "MB Icon Editor_V2.3_LV8.6.zip

Lor LabVIEW 2009 Use the current download

Click here to download this file

QUOTE (PeterB @ May 31 2009, 12:54 AM)

I can't see the light .... I'm not as excited as everyone else seems about the possibilities of scripting yet and I've been an enthusiastic LabVIEW for 15 years now.

What are folks really intending to do now with scripting that has such value ? You can talk about what you plan to do, but if you never allocate time to implement the idea then scripting isn't really all that valuable to you after all.

Enough talk, how about you show me your really useful creations ! (I'll accept Auto wiring scripted tools only if they produce a similar wow factor to the BD cleanup feature !)

I have a fairly useful time saving creation that uses scripting found Here.

I've also created a few Screen Cast videos here and here showing how it works.

QUOTE (Aristos Queue @ May 7 2009, 02:16 PM)

If you want the iteration count after the loop runs, wire the output of the N terminal, not the i terminal.

you typed a value into it while you were debugging!).

Just to clarify the N terminal outputs the max number of iteration possible.

If a conditional terminal it used to stop the for loop it will still output the same number.

http://lavag.org/old_files/monthly_05_2009/post-584-1241725090.png' target="_blank">

QUOTE (Diego Reyes @ May 1 2009, 05:52 PM)

Hi Everyone,

I have about 30 Controls that I have to modify differently in each one of the states of my UI state machine. I would like to know what is the best way to implement this process. I have asked several colleagues and they have provided various options. Please, let me know what you think:

QUOTE (Chris Davis @ May 1 2009, 10:20 PM)

Here is an example of what Chris is talking about. I use this method when I need to disable/hide several controls or groups of controls.

Download File:post-584-1241300774.zip

Hope this helps

It turns out it is eaiser than I thought.

If you right click in the lower left over the message text it gives you the option to open the BD.

It doesn't matter how the menus are setup. This works in LV 8.5

QUOTE (jpdrolet @ Apr 7 2009, 10:04 AM)

Display the hierarchy window and shift edit: Control double-click the main VI icon.

Thanks, I would have never got that one on my own.

I've use Remote Debug in the past but in my current application I have a custom menu.

When I try to use the remote debug feature on my exe I am unable to bring up the remote block diagram.

I am able to open subvis and see and probe their BD just not the Main vi.

Does anyone know of another way to bring up the Main's BD aside from Ctrl-E or Windows->Show Block Diagram During remote debug?

Thanks

Mark

NI Has a realy nice free student trainning series found here

Each section has a Tutorial, Video and Excercise. These are great for people getting started with LabVIEW.

You'll find a section on loops and state machines.

The Captain and I were skyping last night and we came across this site with the best roller girl names.

My favorites: Battlestar Kick Asstica and Aurora Gory Alice

So we started to wonder what if LabVIEW programmers had Roller girl names:

Here is the list so far.

VI agra

Cluster Function

Mother Cluster

Wire Fly

Playing with Wire

LVOOOPing into your Vis

VI Package Mangler

AL-G

While-G-Cyote

Har-G-Lavason

neBulus (for neB)

Truchards of glass

1 NI-ght Stand

Car JKI-ng

Semi Phorebiden LAVA

There's got to be better ones out there.