ASTDan

Personally I think just hearing on how someone does this would be interesting and illuminating.

I plan on attending

Personally I think just hearing on how someone does this would be interesting and illuminating.

I plan on attending

QUOTE (Ic3Knight @ Jun 2 2009, 03:41 PM)

Unfortunately, I think the perforce "trial/demo" is 2 users only, and we'd be 3... meaning an instant cost of abour £1500, not huge, but not easily justifiable either...

Anyone point me in the direction of an easy step by step SVN setup? with the repository on a windows server machine?

Cheers!

Paul

Here is some good reading about tortoisesvn

http://svnbook.red-bean.com/

http://voxel.dl.sourceforge.net/sourceforg...VN-1.6.2-en.pdf

I figure there will be a lot of ideas that will come out of the discussion portion of the presentation, so I'll commit to putting together a recorded version after NI-Week to include the extra stuff outside of our structure discussed on the day, and post it here to this thread.

As a member in good standing of the South East Michigan LabVIEW user group could you post the presentation there also

QUOTE (crelf @ May 28 2009, 10:44 AM)

Have you gained a little weight since I last saw you Dan?

I just want to make sure the room is big enough for all the people who are interested in hearing you talk... So it's just you and me at the bar huh? :beer: Remember you promised to buy me drinks if I came.

Dear NI

Please Please Please put this presentation on Tues or Wed in a big room.

This is my take on error handling

I use a FGV to store User event. On an error I generate a user event and pass the error to my event loop. In the dynamic error event case I have a state machine that can handle whatever error based on the error code, and then perform a custom action (i.e. shut down hardware, perform a certain action to correct the error, etc). I also log all errors generated to a text file.

This I have found works for me because the error dialogs are handeled in the event loop and I can still call other sections of code when the error dialog is displayed.

I am very interested in what other people do to handle their errors.

Dan

P.S. I hope NI gives you the big room for this presentation and doesn't have it at 4:00 on Thurs.

I would like your thoughts on the creating the custom Error text file. NI seems to promote that in the Intermediate classes. When I create custom Errors I just use a state machine in my Error handling routine. I tried using the file but I didn't like switching back and forth. I prefer to see them in my block diagram. I would be curious on what you think on using a text file to create you custom errors

I saw in the NI week 2009 program a presentation by VI engineering on Error Handling.

:thumbup:

I just wanted to share where I am at on this journey.

This seems to be a great start!

http://www.fda.gov/cdrh/comp/guidance/938.html

I have also stumbled across an organization that seems to be focused on helping professionals maintain regulatory compliance withing the medical domain.

http://www.ispe.org/

QUOTE

In my experience, the absolute most efficient way to learn this stuff is to work alongside someone who has experience in the regulated industry and the company (different companies use difference processes, and then in turn different implementations of those processes).

I hear you about working along somebody. However I want to get some basic knowledge under by belt so when I connect with that person I am not wasting a lot of time on fundamental stuff. Is that best served by reading regulations or is there some other resource i.e. "regs for dummies/engineers"

QUOTE

Well put on some rose colored glasses and then talk to me. :thumbup:

Hello,

I am looking to do business with more medical companies, and I want to learn more about developing software for regulated industries. I have been directed to FDA 21 part 820.

This is great however I am looking for more resources.

-Is there a class/seminar that someone would recommend that helps with understanding jargon, methodologies, process, etc. for developing software for regulated industries (i.e. FDA 101)

-Is there any good books, websites, articles , etc that you found useful.

-Would anyone be willing to share there journey to develop code for regulated industries and some of the pitfalls associated with it.

-What tools have you found useful in developing code (i.e. NI requirements gateway)

Thanks

Dan

QUOTE (Tim_S @ Apr 21 2009, 02:30 PM)

I've got a customer that is very remote (how many miles are between Detroit and Brazil?) who needs an update of the code on the cRIO system we provided them as part of the test stand. I can make the updates to the FPGA and RT portions, but tech support tells me I can't compile them without the physical unit. The only cRIO we bought shipped with the test stand. I'd like to be able to compile the update to the cRIO without having an identical system on my desk.

Tim

Give the Livonia office a call they might have a cRIO you can borrow

QUOTE (Darren @ Apr 20 2009, 11:56 PM)

I still contend the 48G series was the best graphing scientific calculator ever made (always bugged me that TI-85 was the standard in my high school).

I agree! Still use my HP. Once you get used to it there is no going back.

Yes that is an annoying little thing about the File Dialog VI.

Here is one I have developed that also asks if you want to overwrite if the file if it already exists.

I also have my automatic Error handling turned off.

Dan

Download File:post-8614-1239726359.vi

QUOTE (Cat @ Apr 3 2009, 12:22 PM)

I'm also not sure what the point is of using a state machine to replace a sequence when the same states always get executed in the same order. That seems like extra code to do the same thing.

I find it is easier to add cases, and you have the advantage of the shift register to store you Report reference and error cluster. I only use this for generating reports, because it is a very sequential thing and sometimes stringing all the functions in a row can get HUGE. It is just a way to keep a report generating sequence from taking up a lot of real estate.

This is my take on a sequence structure.

I only use this when creating reports when I need to do things sequentially and I need a way to easily add cases. I am still playing around with it

If you wore a helmet you wouldn't have to worry about falling. Better yet getting a beer helmet protects your noggin while allowing you enjoy your favorite beverage.

http://www.1ofakindstuff.com/Beer-Helmet.html

So Beer helmets are environmental, prevent frivolous lawsuits, and lower the cost of heath care. Do you think we can get that in the stimulus package?

So if I drink in a darkened bar (saving energy because the lights are dim), and all my energy hog appliances at home are turned off (because I am at the bar). Not only am I saving energy but I am making my good brain cells more efficient by getting rid of blood sucking under performing brain cells.

Once again alcohol the cause of and solution to all of life's little problems.

QUOTE (crelf @ Mar 30 2009, 11:31 AM)

I don't care whether you agree that climate change is true or not, I can't think of any time that it's a good idea to waste energy. Heck, I don't think it's a good idea to waste *anything*.

What about wasting unproductive brain cells with a stiff drink.

If all you want to do is get a feel for the daqmx api I would recommend creating simulated channels in daqmx

https://www.ni.com/pdf/labview/us/acquiring-data.pdf

If you haven't already take a lot at this Blog post about preparing for the CLA

http://labviewartisan.blogspot.com/2009/02...ng-for-cla.html

I just got this.

http://www.amazon.com/Netgear-ReadyNAS-Des...9520&sr=8-1

I went with it because I didn't have to learn how to manage a server. So far I like it.

So it looks like if I import my File layout into the project first, and select autopopulating files. I save off new vi's in my folders the newly created VI's will be reflected in the project in the correct folders.

It looks like in Version 8.5 Projects became much easier and more intuitive.

"NI introduced autopopulating folders in LabVIEW 8.5 to automatically reflect the contents of folders on disk." From web

This gets rid of my main concern of the project not matching what is on disk in real time. I may need to look at this again.

QUOTE

The auto-populating thing really cheeses me. I creatle little test vi's all the time during development to test out ideas before I intigrate them in the main code. These show up in my project when they don't belong, and I have to go into the project to delete them.

I am referring to when I create a New vi it just sits in the project on the main level and I would have to manual move it. It looks like with LabVIEW 8.5 there have been improvements to the project.

Would anybody care to comment on how the project has evolved since its release until now? I am wondering if I have a negative impression from the initail release and the subsequent releases have been much better.

I was having a conversation on facebook with crelf regarding the project in LabVIEW.

Personally I only create a project at the end of projects to build exe, source code distributions, etc. Whenever I have tried to use it during development I throw my hands up in frustration.

The auto-populating thing really cheeses me. I creatle little test vi's all the time during development to test out ideas before I intigrate them in the main code. These show up in my project when they don't belong, and I have to go into the project to delete them.

My main complaint/misunderstanding is if I organize all my files properly on disk why do I need the project? What value does the project give me if I orgainize all my code and suporting documentation on disk?