crelf

...how to accomplish... String Control to HEX representation...

Right click, select "HEX Display".

PS: Welcome to LAVA!

In the string to write box, I'm not sure, how to enter the above sequence ( without the brakets ). Especially the escape button.

Sounds like you'll need to enter the strings in hexadecimal as ASCII codes. Check out the LabVIEW help on how to change the string control to HEX representation mode, and then enter you string in HEX (codes are here). Your example will look something like:

1B41 4120 320D

I guess you just can't beat sex.

It's interesting to see that 'sex' is more popular around the holiday season. Must be all those guys out shopping for skimpy underwear for their significant others...

And if you want to see the code, let me know and i will put it on my space.

We'd love to see you code, but it's best to attach it to a posting here rather than putting it in an external place.

.

What is LAVA Certified?

All LAVAcr submissions are assessed based on LAVA Certified criteria, including appropriateness for the LAVAcr environment. Although this may sound daunting, making sure your submissions are LAVA Certified is really just a matter of common sense and the standard practices we have all come to expect from competent LabVIEW developers. For code to become LAVA Certified, it must adhere to the following requirements:

1. All custom VIs must include an 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.
   
2. A verbose description is expected on the submission web page, and this will form part of the page where your code will reside.
   
3. Error handling must be appropriate. If your code has an error in cluster, then chain errors through your code to an error out cluster. If you're providing code that may be used as a subVI, then enclose all of your code in an error case structure.
   
4. Your style does not need to be perfect, but consider those who will be trying to understand and perhaps modify your code. Keep crazy wiring to a minimum, try to line subVIs up, give VIs meaningful icons, use the 4-2-2-4 connector layout when you can, etc.
   
5. All submissions must be versioned.
   
6. Code with locked diagrams, missing diagrams or password protection will not be accepted.
   
7. You must take reasonable steps to confirm that your code conforms to the functionality you submit it under.
   
8. You are the primary support vehicle for your submitted code, and you must stand behind it. If another LAVA member has questions and/or comments, you must make yourself available within a reasonable amount of time to help out. Each portion of code will have a dedicated support thread, and other LAVA members may try to assist too, but you own the code, so it's your responsibility.
   
9. LAVA Certified assessors will not alter your code to make it meet the requirements. If a submission does not meet the requirements when it is assessed, it will be returned to the member with a short description on the requirements it failed to address.
   
10. Submissions must state the LabVIEW version it was created with. If you would like your code to be listed under more than one version of LabVIEW, then you must provide an extra copy in the appropriate version. You must confirm that your code works appropriately under each version of LabVIEW that you submit it for.
    
11. LAVA Certified code hosted in the LAVAcr must be bound by a software license of your choosing. The complete full legal text of the license must be included in a text file with your submission zip file. You must also include your contact and ownership information. Currently, we only accept code licensed under an Open Source License. The submissions form currently supports the following licenses which you can chose from:


1. Creative Commons Attribution 2.5 License
   
2. The BSD License
   
3. GNU Lesser General Public License
   
4. GNU General Public License
   

[*]All published code will be altered to include a reference to its' LAVA Certification and branded with the LAVA Certified logo, as shown above.

:!: The LAVA Certified program is a living design, and whilst general discussion about the LAVA Certified requirements is certainly encouraged, it is considered poor form to single out cases for personal gain or attacks. Please be considerate of the LAVA Certified assessors - they are a very dedicated unpaid team whose sole purpose is to foster high quality code sharing, and not to discourage anyone personally.

Who are the Assessors?

LAVA Certified assessors are long term LAVA premium members and experienced LabVIEW developers and architects who have a vested interested in seeing the LabVIEW community grow through cooperation. Whilst they may not be famous, each assessor has several years experience in sharing and support in our community and are determined to see it thrive.

Can I Help?

The easiest and most important way for you to get involved is to contirbute to and expand the LAVAcr - it can only grow through comprehensive and well respected submissions from users like you. Another extremely valuable way to help the LAVA Certified cause is to either donate to LAVA or become a Premium Member. Premium membership comes with all sorts of advantages, so you'll get more out of it than just feelinng good about supporting the LAVA community

That said, we are always open to accept new LabVIEW Certified assessors into the team. If you've got a little time on your hands, are passionate about building the network, helping others share and keeping the high standards of the program alive, then there just might be a place on the team for you. If you think you've got what it takes, then contact us.

:!: We currently accept LAVA Certified Assesment Team applications from Premium Members only.

That's how I feel now, "I don't know why..." I've actually lost some sleep thinking about what I did.

I wouldn't beat yourself up too much about it Phillip - we're all in this together mate

NI is the catheadral and LAVA is the bazaar.

That's a great attitude - I like it!

"Sharing: To participate in, use, enjoy, or experience jointly."

The LAVA Code Repository (LAVAcr) is a sharing place where LabVIEW users can share meaningful and well-structured code in an open and free environment. This section of LAVA is the culmination of several months of thought by LAVA's founders and we are very proud of the structure that we have created.

The LAVAcr is NOT a highly structured online collaborative site (we've got the more than capable Open G for that), nor is it an uncontrolled dumping ground for any and all VIs submitted by the community - it's something in the middle.

All LAVAcr content is LAVA Certified - a certification that insists on appropriate quality, support and usefulness. Members cannot simply upload any type of code to the LAVAcr - it must adhere to specific standards and rules before it is considered for inclusion. All code submitted is moderated by a group of well-respected LabVIEW professionals, all of whom are also respected premium members of LAVA.

What is the Process for Submitting my Code?

Code is submitted by filling out a dedicated web form here. This form requires some information from you (including a functionality description, image, desired distribution license), as well as a place to upload you code. You will also be asked to confirm that your submission adheres to the LAVA Certified requirements. Once you have submitted the code, it will move to a holding area on LAVA that is accessable only by LAVA administrators and the LAVA Certified assessment team. A LAVA Certified assessor will take ownership of your case and begin the assessment process. Once the process is complete, you will receive notification whether you submission has been accepted and included in the LAVAcr, or if it has been denied based on the LAVA Certified requirements.

How long does it take for my submitted code to be published?

That's an easy one: it depends The LAVA Certified assessment team are donating their time to this cause, so it may take a while (we aim to average next-business day). Find comfort in that good things come to those who wait.

What Happens if my Code is Denied?

We here at LAVA are people, just like you, and we don't want to exclude anyone, but making the LAVAcr a free-for-all defeats the purpose of having a premium resource where other users can be confident that the contents are of a high quality. If one of the LAVAcr assessors deems that your submission doesn't meet all of the LAVA Certified requirements, then you will be emailed with a list of items that are considered erroneous. You are more than welcome to address the issues and resubmit the code. If you believe that your code is compliant with the LAVA Certified requirements and it is still rejected, please contact the assessor directly with your concerns.

In the mean time you could read LabVIEW help on arrays, For Loops, auto-indexing and related examples.

You want to learn LabVIEW don't you?

:laugh:

...my true intentions in LAVA is to communicate with you all and help develop a better partnership.

Are you serious?!? If you want a true partnership then try being a partner: tell us what's going on and maybe we can be involved in the building of such a community. Don't just start asking loaded questions - that's downright rude and belligerent.

Being a little "pessimistic" about our community site launch is very much an honest and understood reaction.

I'm not "pessimistic" - I'm far from "pessimistic", I'm angry! This is a forum for and by the people - I like that NI staff visit us, help out and occasionally learn some stuff - it's in all our interests - but I think you picked the wrong forum to be manipulative on. If you want to do that, then maybe you should stick to your own moderated forum. :2cents:

As I said, if you want to truly partner, then IMHO you'll need to do a much better job that you did.

guess that's it

thx

np This is what you need: NI PDA Toolkit.

I can change the first one only using property Plot.Name, but it only handles the first one.

The Plot.Name property deals with the "Active Plot" (which is, by default, 0). Set the Active.Plot property to 1 (or whichever plot you want to change) and then use the Plot.Name property. This can be done several times in one property node, as LabVIEW executes them in top-down order.

But there is no "Switch Execution Target" in my operate menu.

Have you installed the PDA toolkit?

Now, if I could only get around to donating to LAVA...

Let me help you with my signature below:

Can you get that changed for me? Ya, thanks, appreaciate it...

Actually, the bloke you want to have a yarn with is John Howard - and, as luck would have it, he's stateside right now - you might bump into him on his morning walk, or at the pub tossin' back a coldie...

This is just a sample of the language my dad would use after spending the morning trying to start the lawn mower.

Your dad's language isn't quite as colourful as the trying-to-start-the-bloody-lawn-mower language I remember as a kid, but LAVA's naughty-word filter wouldn't let me get those ones through...

How is This Different from the Other Examples on ni.com?

The primary difference is that you, the content contributor, own your examples on NI Community. We are providing a rich set of tools, like revision history, RSS, and ratings to allow both the users and the community to get more out of the examples.

I really hope that I'm wrong, but has the launch of the NI Community revealed this user's true intentions?

I noticed that Australians say: "Works a treat". Is it a common saying over there?

Too right it is.

For this, I have to say again, different forums life and different custom...

That may be so, but before posting on any forum you must RTFM!

Congratulations to all who entered the coding challenge. It certainly wasn't an easy challenge (hence the defintion of the word ) and the winners and commended entries show that there were some really thoughtful and well-engineered entries - well done! :thumbup:

Does LabView 8.0 support 24bit sound ?

Have you read the LAVA User Group Guidelines? You've already posted this question here (in the exact same forum as this one - not a good start!) Please refer to the paragraph on cross posting.

Sheesh - I feel like the big bad brother recently!

Nah, 'cause all of the shortcuts are listed in the LV help file in one place anyway.

and for those on the SSP, here's the LabVIEW Quick Reference Guide:

Download File:post-181-1147549012.pdf

...tell urgent signal to the ardour man is not bad, all right ?

Forget it - if you don't understand this, then I can't help you. Please just try to live by the forum's guidelines and we'll all get along.

...just a simple talking or sentence, should we ,or we must point out his/her behavior right or wrong ?

This forum is dedicated to a particular topic, and when you sign up for an account here, you're asked to follow the LAVA forum guidelines - the links I posted you were all from those guidelines. I'm not trying to chastize you, but instead guide you to better practises - if you follow these better practises then you'll have a much better chance of getting a more positive experice out of this (and any other) forum. If ypou would like to ramble on about anything, then that's what the LAVA Lounge is for.

...I was very urgent to solve this case, and my boss chases me about it, I am searching the solution in every and different way. for the hurry up time, so I did (issued second words)...

Oh - well that's completely different! In that case, check out this link.

Here's my code.

Nice bunny icon :laugh: