Jump to content

xtal

Members
  • Content Count

    131
  • Joined

  • Last visited

Community Reputation

2

About xtal

  • Rank
    Very Active
  • Birthday 01/15/1967

Profile Information

  • Gender
    Female
  • Location
    Flagstaff, AZ

LabVIEW Information

  • Version
    LabVIEW 8.6
  • Since
    1989

Contact Methods

  • Twitter Name
    xtald

Recent Profile Visitors

2,283 profile views
  1. I'm in!! Can't wait to see y'all again!
  2. I vilify Clean Up Diagram because it deserves it. How do you "improperly use" a button? There was nothing even remotely "clean" in what it produced; I can't imagine ANY LV programmer wanting their code to look like that. If someone hit Delete, then the *situation* would suck because that's what Delete is supposed to do and you might have clicked it when you didn't mean to. As it stands, I think the Cleanup feature sucks because it doesn't do what it is supposed to.
  3. We did after it was all "fixed" but we were heavily in trouble-shooting mode at the time and all available USB drives were occupied with ESTOP, joysticks, and such. We had no idea the kid was gonna modify our code like that. I wasn't even there since there wasn't room in the pit and I needed to talk to the NI folks about some cRIO things. It would be so much easier if I could just disable that button like I can the Abort and Continuous Run ones. Why is that so unreasonable?
  4. We can disable/hide the Abort button and turn off debugging. I don't see why it's an unreasonable request. For those who are suggesting SCC, you are completely missing the point. The drive computer is a bare-bones system that communicates with the robot during a competition. It's not the development machine/environment. We only change the code between matches based on how the robot performs. We use SolidWorks to model and design the robot, too, but we certainly can't put it on the drive computer, either.
  5. I've looked around but it appears I can't turn off/hide/diasable the Clean Up Diagram button in my LabVIEW environment. Why I want to do this is a huge rant, so ignore the rest of this post if you don't want to hear anything negative on a lovely Friday. As many of you know, I am the mentor of a FIRST Robotics team and we went to the World Championship last week. The programmer for our team, Tomas, learned all his LabVIEW from me, so he codes exactly like I do. I'm an old-school LabVIEW developer from long before there was an Undo and I've developed many habits and a particular style over t
  6. Hey, Paul I've been working with high school students and while they are complete novices at programming, they take to LabVIEW very easily. We don't do OOP but we have been programming cRIOs to make robots. Let me know if you want me to invite you (and others at Lowell) to any of their events. Keep an eye out for the CocoNuts (Coconino High School's Robotics group) and FIRST. I've been mentoring them for 2 years now and absolutely love it!
  7. Darn! We are going to miss you, Cat. I'll be there as always.
  8. When you work in a regulated environment, updating SW from 8.6 to 8.6.1 is considered a pretty major change requiring all sorts of revalidation. I'm fine with LV updating often and fixing things on a yearly cycle, but don't expect me to jump on board for each new rev the second it releases. Most of my projects are still in 8.2.1 and 8.6.1. Yes, I'm falling way behind on the "new features" curve, but it sure beats having to revalidate dozens of machines.
  9. Neither, I'll wear Teva sandals like always (no socks) because I'm the weird hippy chick from Flagstaff.
  10. If in doubt, right-click on the object you want to modify.
  11. xtal

    Getting Surged On

    Hang in there, Cat! I hope things continue to go smoothly. Next NIWeek we can talk back surgery over a margarita or five.
  12. Thanks! I forwarded the link to my FRC team. One of our own is in the movie at 0:50 - she'll get a kick out of that.
  13. I second Cat's nomination of Mark for LV Saint.
×
×
  • Create New...

Important Information

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