Jump to content

lavezza

Members
  • Content Count

    57
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by lavezza

  1. One thing you might consider is NOT using LabVIEW 64-bit. We run dozens of Windows Server 2012 R2 (64-Bit) servers with 32-bit LabVIEW applications. Unless your application needs LabVIEW 64-bit due to large memory requirements, there is no need at this point to build your apps in LabVIEW 64-bit. That said, if you do decide to use LabVIEW 64-bit all of mje's comments apply.
  2. %^<%j/ %H:%M:%S>T[/CODE] [CODE]%^<%j:%H:%M:%S>T[/CODE] 287/ 23:15:42 287:23:15:42 Day of year, 24hr UTC. It is how things are scheduled on the International Space Station, TDRSS satellites, etc. I think files usually use the second format, displays use the first.
  3. Job Posting We are looking for another LabVIEW developer to join our team near Los Angeles. Here's the short version: We build rockets and spacecraft. We deliver cargo to the International Space Station and we have a contract to demo manned launches. Our goal is people on Mars. Our group writes the software to control the launch pad and rocket before liftoff. We also write the software that commands and monitors our spacecraft in orbit. We use LabVIEW as a general programming language. Our PXI/DAQ components are a small, but mission critical part of the equation. Large application develop
  4. Here are the VIs we use for Windows authentication and domain groups. Validate Username and Password.vi takes the username and password and returns a TRUE if it validates against the domain controller. User in Group.vi takes a username (or current user if left blank) and a Domain Group name and returns TRUE if the user is a member. User Groups.vi takes a username (or current user if left blank) and returns an array of Domain Groups to which the user belongs. We only use these on our internal network, so I can't guarantee they work in every situation. Still, they may give you a starting poi
  5. Our Launch Operations team keeps growing. Time for another LabVIEW developer. Specific questions: Email me Please use this link to apply. It will tag your application as coming from LAVA. (I've placed a similar post on the NI forums. That link will mark it as coming from NI. Our review process starts with LAVA, then NI, then SpaceX.com/careers, then generic job sites. Short version, use this link and not the one on NI to get higher in the queue) Important: To conform to U.S. Government space technology export regulations, SpaceX hires only U.S. citizens and U.S. Permanent Residents. Respons
  6. Description Our rapid growth has created opportunities for additional Mission Operations Engineers focused on Mission Control software development to support the launch, orbital operations and recovery of our Falcon 1 and Falcon 9 launch vehicles and our Dragon spacecraft. Responsibilities Help maintain and upgrade the PXI/LabVIEW systems that control launch pad equipment Help maintain and upgrade the LabVIEW-based vehicle control system used to command and monitor our Falcon 1 and Falcon 9 launch vehicles Assist with developing, maintaining and upgrading the LabVIEW
  7. SpaceX is looking for engineers with LabVIEW programming experience for our Launch group. Our responsibilities include: Controlling launch pad equipment via PXI/LabVIEW Commanding and monitoring our Falcon 1 and Falcon 9 rockets via a LabVIEW-based Vehicle control system Commanding and monitoring our Dragon capsules via a LabVIEW-based Mission Operation system Ocean recovery of Falcon 1 and Falcon 9 stages after liftoff and Dragon capsules after splashdown Cargo configuration of Dragon capsules going to resupply the International Space Station Maintenance of Mission Control Centers with the
  8. I'm curious to see how other people have dealt with this problem. (or would deal with it) Example: We have a system with 1000's of sensors, things like temps, pressures, switch status, etc. Some of these may be changing at 5Hz, some may only change a couple times a day. A third-party data system collects the readings at different rates. In addition, some of the sensors are smart and only send data when things change. So, we get packets over the network and we need to save them. Each packet will have a different number of sensors reporting and a timestamp. Obviously the packets contain both th
  9. Is the Property App.MenuLaunchVI available in the new scripting toolkit? I didn't see it. Is the functionality available with another call? Thanks, Pat
  10. QUOTE (JFM @ Sep 25 2008, 11:26 AM) JFM, Can you share your findings from your comparison. We are in a situation where our company is trying to get us to move to CC (our corp standard), but we'd rather move to SVN. We're using SourceSafe right now. I'd be interested in what you found out, especially any LabVIEW specific items that we should be aware of. Thanks, Pat
  11. QUOTE(Tomi Maila @ Feb 7 2008, 10:11 AM) Neither. The readme's litter the parent folder and they are html. http://lavag.org/old_files/monthly_02_2008/post-192-1202424621.png' target="_blank">
  12. QUOTE(gmart @ Nov 26 2007, 08:36 AM) You're right. After my last post I took another look and realized it was easier than I thought. I'm not sure how I missed that the last time. I think it would be fairly easy to take the P4CMD folder and make an equivalent for SVN (or any other SCC that has a command line interface). Pat
  13. QUOTE(gmart @ Nov 21 2007, 04:36 PM) Both. I don't even think I have enough RAM to open all the VIs, let alone run them. Obviously a lot of our VIs are called dynamically. Besides, having 6000 open windows would be a little hard to handle. QUOTE(gmart @ Nov 21 2007, 04:36 PM) Having separate source and object code is a long standing request. Just because it hasn't happened doesn't mean it hasn't been considered. I can read that two ways: "It's been considered and rejected" OR "It's been considered and I'm not going to tell you more than that." QUOTE(gmart @ Nov 21 2007, 04:36 PM)
  14. QUOTE(hviewlabs @ Nov 21 2007, 12:19 PM) The compiler. I think MS defaults their compilers to '#pragma pack 8' for 8-byte alignment. Although I'm not sure that all their internal data structures are done that way. We had this issue not too long ago. I was too lazy to write a wrapper DLL for a DLL written by another group in our company. There was one call that returned a structure. Reading it as a byte array and casting to a cluster wasn't working. It worked after adding some 'dummy' U8's into the cluster. When changes were made to the DLL we got them to compile with '#pragma pack 1', whic
  15. QUOTE(hviewlabs @ Nov 21 2007, 12:19 PM) The compiler. I think MS defaults their compilers to '#pragma pack 8' for 8-byte alignment. Although I'm not sure that all their internal data structures are done that way. We had this issue not too long ago. I was too lazy to write a wrapper DLL for a DLL written by another group in our company. There was one call that returned a structure. Reading it as a byte array and casting to a cluster wasn't working. It worked after adding some 'dummy' U8's into the cluster. When changes were made to the DLL we got them to compile with '#pragma pack 1', whic
  16. My 2 cents. Our current project has 6554 *.vi or *.ctl files. Having an "All VIs" vi is not an option We are constantly being bitten by recompiles. On one hand you don't want a lot of checkins for VIs that weren't really changed. (Especially when your customer requires an explanation for changes in source files from one delivery to the next) On the other hand you don't want to leave the system in a state where 1000's of VIs are recompiled every time you run. Here is what I'd like (and I've passed this on to NI already): Right now we have source & object code in same file, run
  17. This all reminds me of some code a hardware vendor supplied us many years ago. I've reproduced the style below. Creative(?!) use of the N terminal.
  18. QUOTE(Justin Goeres @ Aug 27 2007, 12:51 PM) Well, it's nice to get it to work consistently. Unfortunately, it would be consistently wrong (at least based on the way we think it should work). We've already written a work around for this particular VI, but it would be nice if it worked the way we all think it should.
  19. OK, we just did some more testing. On my machine, it seems to always work as expected all the time. On my co-workers machine (where we first saw this problem) we are seeing that it sometimes works, sometimes not. Damn.
  20. We have discovered a problem and I would like some help from the community to see if this is widespread. I've attached a VI that I'd like everyone to run. The user changes a numeric control and then immediately clicks in a listbox. The Value Change event for the Numeric gets the value of the listbox and displays it in a dialog. On most of our machines, the listbox value changes after the Numeric Value Change event. On some it changes before. On the machines with the odd behavior, it shows up in 7.1.1 and 8.2.1. If you follow the instructions on the front panel, I think you should get zer
  21. http://arstechnica.com/articles/paedia/cpu...64-core-CPU.ars I'd like to see one of these in a cRIO controller. 64 cores, 4 DDR2 RAM controllers, 2 10Gbit Ethernet, 2 Gbit Ethernet and 2 4x PCIe interfaces. After all the multicore hoopla at NIWeek it would be great to see NI quickly demonstrate what LabVIEW can do on 64 cores.
  22. QUOTE(Val Brown @ Aug 14 2007, 06:04 PM) NI.com lists it as $1499 in the US and CAD1800 for you Canadians. It it marketed as a Module (on the same level as Real-Time, FPGA, PDA, etc.) and not as a toolkit (like database, VI analyzer, etc.). Most other modules are available with a significant discount if purchased with the NI Developer Suite, but it doesn't look like the Statechart module has been added as a Developer Suite option yet. Pat Lavezza
  23. I think an Advanced Topics Day on Friday would be great. Plus it is an excuse to stay for Friday night on 6th street . First, there should still be advanced sessions during regular NI Week or else we'd all get bored. Second, I would like to see longer time slots. I'd like an hour long in-depth presentation followed by an hour long discussion with the developers. Four or Five of those sessions plus a short lunch. The interest may even be small enough to have it on the campus (since it is probably too late to get that Friday slot at the convention center next year). I can imagine sessions on
  24. QUOTE(Gary Rubin @ Aug 3 2007, 08:44 AM) You didn't get them? They were great!
×
×
  • Create New...

Important Information

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