Jump to content

rharmon@sandia.gov

Members
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    1

rharmon@sandia.gov last won the day on June 12 2020

rharmon@sandia.gov had the most liked content!

Community Reputation

2

About rharmon@sandia.gov

  • Rank
    Very Active
  • Birthday 12/07/1956

Profile Information

  • Gender
    Male
  • Location
    Livermore, CA

LabVIEW Information

  • Version
    LabVIEW 2009
  • Since
    1992

Contact Methods

Recent Profile Visitors

1,537 profile views
  1. Thought I'd give a quick update on where I'm at.... But first a HUGE Thank You to everyone here... I can't express what a fantastic resource you guys are. I decided to try Tortoise SVN, mostly because everyone seemed to say it was the easiest to use, for a beginner in SCC I thought that very important. So far so good... I created a repository on my computer and (terminology is going to bite me here) Imported my project. It all appears to be fine so far... I know small steps.... This week has been crazy busy.. I'm hoping to actually change some vi's today and see how that goes. Next
  2. Eric, I think you are exactly right... My thoughts of a branch was I have a software package and probably 90% of that code will be used in another project. I was thinking I would just branch off the second project and make the necessary changes to make the second project work. It would not be my intension to ever re-unite the branches. Thank you for catching my mistake... You have probably saved me from a future huge headache....
  3. Great Information... I think reading through these posts I'm leaning toward Subversion or Mercurial... Probably Mercurial because from my conversation leading me toward source control touched on the need to branch my software to another project. Next step... download the software on another computer (so I don't endanger my current projects) and give it a try. I can't express how helpful these posts have been, It would have taken me days to try all different source control options available... Just read Crossrulz's reply and it states "just don't branch and you will never have t
  4. Yes... Very frightening... Buy toward the end it gets interesting... Maybe git is not so bad after all... Pretty sure it's not for me though... If one of my LabVIEW hero's is having trouble using it I better run away fast!!!
  5. Ok, I'm about to show my ignorance of source control software, but I've noticed a bunch of comments complaining about issues with merging files. I'm not quite sure what merging a file means. Could you explain a little for me... thanks
  6. So I spent much of the afternoon looking over postings here on Source Control Software and LabVIEW. I must say I came away discouraged. I've been programming LabVIEW for over 20 years in a single one technician lab and never really needed any stinking source control. Well now that's not the case. But thought I'd just read some posts, determine what everyone else likes and be done!!!!! That didn't work out for me ether... Seems nobody really likes source control after all. Or at least there are issues with just about every option. So here is my situation. I'm still the single labVIEW
  7. I've been using this vi to write error information to a log for months at this file path C:\LabVIEW Working Folder\Tester Software\Config and Log Files\Error Log.txt and as an executable at this file path C:\LabVIEW Working Folder\Tester Software\data\Error Log.txt Now for some unknown reason randomly but usually on the close i get a file dialog box asking which file to write... Any idea what I'm missing... what stupid mistake did I make? It just doesn't make sense...
  8. You guys always have the best information/ideas... Thank you all... Since I really like the new entries at the top of the log file, and my major worry is that the file gets too big over time and causes the the log write to consume too much time I really like dhakkan's approach of checking the file size periodically and flushing the file and saving the data to numbered files.
  9. I have an error log and a couple other logs associated with a program I've written. My question is this, when you read a log file, do you expect the newest information at the beginning of the file or the end. I think I prefer it at the beginning of the file... That said I worry about large log files. The only way I figured out how to accomplish this was to read the entire file, add my new entry at the beginning and then re-write the entire file. Seems like a lot of overhead just for a style preference. Is there a better way to accomplish writing new entries at the beginning? Or does
  10. I have an executable that I install on new computer that doesn't have LabVIEW installed. This executable uses a PXIe Chassis and several different cards. I refer to these cards in my software as "PXI1Slot2_AIO_UUT1" and "PXI1Slot11_SMU_UUT1". I realize I need to setup MAX with these names the way I currently have things setup. But my question is How Do You Guys deal with this on a blank new computer. I would rather not install LabVIEW on these machines. Can I just install MAX? Are there other options? Thanks for your input...
  11. I have a program where I launch a clone that runs in the background and updates the Top Level VI. In normal operation the top level vi tells the clone to stop and everything seems to be fine, but every once in a while the clone stops, or maybe the top level stops and leaves the clone running. Is there some method to monitor running clones? Maybe with the ability to stop a running clone? This is how I launch the clones. Thanks for your help...
  12. All, Once again I want to thank everyone who chimed in to help me figure out this communications issue. I have attached a small project file that communicated with the Tripp-Lite SmartOnline UPS. If Tripp-Lite tells you to use communications protocol 4001then this software should work. To say again, Tripp-Lite was not helpful. The protocol document they sent me in no way works. Not even close. What was helpful. 1. Input from you guys who chimed in here. Huge help... Thanks. 2. https://github.com/networkupstools/nut/blob/master/drivers/tripplitesu.c although I don't d
  13. All, Once again I want to thank everyone who chimed in to help me figure out this communications issue. I have attached a small project file that communicated with the Tripp-Lite SmartOnline UPS. If Tripp-Lite tells you to use communications protocol 4001then this software should work. To say again, Tripp-Lite was not helpful. The protocol document they sent me in no way works. Not even close. What was helpful. 1. Input from you guys who chimed in here. Huge help... Thanks. 2. https://github.com/networkupstools/nut/blob/master/drivers/tripplitesu.c although I don't d
  14. All, Once again I want to thank everyone who chimed in to help me figure out this communications issue. I have attached a small project file that communicated with the Tripp-Lite SmartOnline UPS. If Tripp-Lite tells you to use communications protocol 4001then this software should work. To say again, Tripp-Lite was not helpful. The protocol document they sent me in no way works. Not even close. What was helpful. 1. Input from you guys who chimed in here. Huge help... Thanks. 2. https://github.com/networkupstools/nut/blob/master/drivers/tripplitesu.c although I don't d
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.