Jump to content


  • Posts

  • Joined

  • Last visited

About Tanner

  • Birthday 04/09/1991

Profile Information

  • Gender
  • Location
    Atlanta, GA

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 8.6
  • Since

Tanner's Achievements


Newbie (1/14)



  1. Yeah, sorry, busy with the robots and recently finals. No, I never did find a satisfactory solution. I didn't have time to mess with Git more and using SVN wouldn't be very satisfactory with how things are set up here (at least it wouldn't be as useful as Git would be). -Tanner
  2. Ugh. Got busy and haven't had a chance to figure out whats wrong yet. When I have a chance (hopefully before Saturday), I'll upload the full code. I'm not really sure when I'll have the chance to test it fully with the cRIO again, so any help would be appreciated. Thanks -Tanner
  3. I haven't tested the exact same file, just the whole idea, and that has worked. I'll see if I have tomorrow to test if I can read the file that was written by the cRIO back on the computer, though tomorrow's busy. I'll see though. -Tanner
  4. Oh definitely. Plus I learned something new - always good. Thanks -Tanner
  5. I did some looking and noticed that my ARDS Data.ctl was not linked to ARDS Joystick Data.ctl as the ARDS Data contained two joystick's worth of data. I linked those and found a few others that needed to be linked or changed. Thought that would fix it, but nope. Still returning odd/adbnormal data. New files attached. -Tanner And it won't let me edit that post. Grr.. Here's the files. ARDS.zip
  6. Don't think I could, but if you need it I can post it tomorrow (cause then everyone gets the code). I don't think you need it for Reading it, just Writing it. -Tanner
  7. This includes the Vi's plus the typedefs and a data file. I haven't changed anything just to not break anything that is already broken. So, the hints I don't really want to implement cause I'm not too experienced otherwise and just want to get it working first. Should all run (has no other dependencies) and the data within the file should have the joystick Y increasing, buttons 4/5 being pushed, and then joystick Y decreasing. Shout if I forgot something. -Tanner ARDS.zip
  8. I think it is using relative paths now that you mention it. I'm trying to figure out where exactly Git gets/puts the files... Yeah. No internet stinks. Although it is a eye-opener to how much we depend on it nowadays. :\ -Tanner
  9. In response to the "do it online" post (I can't figure out to get it to post with multiquote), using a server would be harder in my situation. Since we mainly work/program at school - an environment where we have no internet, and no cell phone signal most of the time - having the server there (i.e. - located on the main development station or another computer there) would be a lot easier than using the internet. If I used the internet, that means I would have to bring the code to the school - something I am liable to forget. Yeah, we could have developer stations I could take home, but our main one is a dual-screen desktop which is nicer to work with. Depends what situation you are in. I haven't had much experience with Git, but I'm guessing the answer would be merging. How exactly the workflow breaks down, I don't know - could probably research it. -Tanner
  10. Well, LVMerge opens, shows the error window, and closes, but there doesn't seem to be a active merge between the two files. It's not doing a merge or saving it. And yes I have it now. -Tanner
  11. That's the exact topic that me and my friends are discussing this in (though abit without the deep knowledge of LabVIEW). It's a scare topic of using Git. :\ -Tanner
  12. That actually makes a heck of a lot of sense if I think about this as a textual language. Private data for stuff that doesn't need to be public. Again that makes sense. I'll see how much I can get rid of the global variables, just to make the execution flow a bit better. The clusters used to be independent controls on a each vi, but they should now derive from a common typedef (after I figured out how to connect the two). I'll check the data type when I get a chance as well to make sure everything's the same. Thanks -Tanner
  13. Same number of points? The array as far as I know contains the same number of elements, but I'd have to check to be for sure. I do not believe I'm getting a error from Read from Binary File. I added the Set File Position just to make sure that the Read Vi was reading the right place. The vi isn't being executed by itself (or at least it shouldn't be), I only had that because it appeared to be the only way to get a time stamp in ms. Is there a pro to using shift registers? Some of them I use in other places or have to be initialized. I don't see how I could get rid of the sequence structures, as I have to increment the line I'm reading and something else and putting it all in one structure would appear to make it run in whichever order LabVIEW wants (unless I misunderstood how smart it would be at that). I'll have to see if the code does not contain any Beta code (which I cannot release under a NDA). How would I save the state of the Vi unless you mean just the Vi? Thanks -Tanner
  14. No I'm saying that when the programmers aren't in contact with the server, Git could still commit locally while SVN would complain (unless something's changed since last time I used it). Well, you don't. Though I'm guessing this is where the merge capability comes in. I'm not sure if Git has this lock method. Well, there would be a central server and there would be a repository on each developer's computer. Then after a developer has made a commit, they can push the code to the central server. I'm going out a limb guessing that everything would work fine as long as developers did not work on the same vi or something of the such? It also seems that this locking method is recommended? to prevent merging two vi's (because the way of merging isn't the best?)? Basically what I'm trying to understand is why locking is preferred? Is it just because it prevents having to merge? Thanks -Tanner
  15. Thanks - I'll have a look at those. Well, the benefits of having the entire source distributed is that the user can do commits without the server (versus doing all a nights work in one big commit the next day - bit harder to narrow down bugs). Having the source distributed also means I have the entire history of the repository so I can do diffs, logs, and reverts without the server. Quite nice. -Tanner
  • Create New...

Important Information

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