Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Reds last won the day on August 5

Reds had the most liked content!

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2011
  • Since

Reds's Achievements


Rookie (2/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Reacting Well Rare
  • Week One Done Rare

Recent Badges



  1. For those interested in an announcement I mentioned at the start of this thread:
  2. The issue I've found is not the LabVIEW vi's bundled with the driver installers. The *real* issue is the property nodes. Some drivers, like NI-RFSA, have tons of things that can only be set through a property node. You can recompile and move/copy vi's to your heart's content, you'll never get those property nodes to work in any version of LabVIEW that is not "supported". I'm certainly hoping that they find a way to allow property nodes from any version of NI-xxxx to work in any future version of LabVIEW. One can dream, right...
  3. Has anyone noted anything particularly noteworthy from NI Connect this week? One thing I noticed is that NI is going to be decoupling NI driver versions from LabVIEW version numbers. I think this means that you will be able to use any version of LabVIEW with any version on hardware driver in the future. Anyone notice any other announcements of interest?
  4. Wow. Thank you for a valuable post Rolf. All of that helped me answer and understand so many open questions I had. When I look at recent NI actions from these angles, it does all make sense. It doesn’t make me happy, but at least I can understand it.
  5. I've been to all of the NI Week conferences in the last ~ 10 years. I never attended a Lava G event, never saw one advertised outside of this forum itself, and never even noticed a room set aside for Lava G at the convention center (I frankly don't even know where the event is held). If people care strongly about this community here, the best thing to do is to casually let people know on reddit, or ni.com, or stack exchange that this forum exists. It's my belief that this forum only got traction in the first place because it's existence was announced on another forum, info-LabVIEW. I know most of you guys are hard core engineers, and "dont' believe in marketing". But, you know, the field exists for a reason....
  6. I’m not so quick to use participation numbers on this website as a proxy for LabVIEW popularity generally. I would be real curious to know what percentage of active participants on this site only found out about it via the the old info-LabVIEW listserv. How would a brand new LabVIEW developer find or know about this site? Google? What are the odds that this site ranks better than ni.com in Google? Pretty much zero I would think.
  7. So I love a conspiracy theory as much as the next guy.....but I've changed my mind. There is no conspiracy to kill LabVIEW here. I recently discovered that some of the toolkits NI sells, like the ones used to generate WiFi test signals for the RF hardware, are also going subscription only. Now this is pure madness. Who wants to buy a $75,000 signal generator for your lab, which will be useless if you don't resubscribe to the software package every year? Crazy. So I've changed my mind. They're not trying to kill LabVIEW with a subscription. These people are just dumb. Really, really dumb. Never attribute to malice that which can easily be explained by incompetence.
  8. Re. the YouTube video... Yes, this is absolutely the problem! Great reference! (Start watching at about 2:30).
  9. Related: Color of money is a big deal in corporations. Especially in sectors like defense and government. I've seen huge buckets of government money that have one big stipulation: They can ONLY be spent on CapEx, not OpEx.
  10. I think the biggest problem with the subscription model is that it does not set incentives correctly for NI. In the olden days, a company had to actually improve their software and innovate in order to get paid more money every year. Now, with the subscription model, all they have to do is "lock someone in" to their platform, and they get paid forever. Why continue to add new features to your software every year? Your suc......err....customers.... HAVE to pay you. Even if you don't continue to improve the software. In this new model, what financial incentive does NI now have to continue improving LabVIEW? It seems to me like they only need to just enough to keep existing users from leaving. That's not exactly innovative stuff. You know what it leads to? Flat revenue for the product line. You know what Wall Street hates?
  11. A stream of pictures at 30 frames per second or higher is best handled as.....wait for it.....video. I'm not aware of any software that could stream raw video into a database. It seems kind of crazy to even try that. My best advice is to start thinking about this as a video problem that requires video compression and video codecs. Those video codecs could be either hardware or software based. If each of your pictures is significantly different from the last, then you would want to use what's known as an "intra-frame" video codec. This type of codec does all video compression on a single frame/picture and does not rely on information from surrounding pictures/frames.
  12. I have to admit I didn't read every word of this thread...but... In this type of scenario, I would normally use a Notifier, not a Queue. If the GUI loop can run fast enough to display all of that data, that's great. If not, some data is skipped. A lossy Notifier is perfect for this scenario.
  13. That's a very common misconception. But it's actually not right. Service businesses definitely do not have 100% gross margin. "Cost of Sales" is a more accurate term than "Cost of Goods Sold" for a services business. But otherwise, it's the same calculation. Services businesses should be calculating gross margin by figuring out how much they pay an engineer directly for every hour that engineer bills. If you pay an engineer $50/hour, you'll need to bill him at $200/hour to get a 75% gross margin. And he's going to need to bill 40 hours every week. If he's not billing 40 hours every week, there won't be enough money to pay for sales, marketing, and G&A overhead. If you're a one-person company (i.e. a single person alliance member), you will need to be so damn good that you can support your own salary on 2 billable hours per day if you want to hit 75% gross margin. This is a great conversation. I hope we can have more business conversations like this on LAVA.
  14. I agree with that general premise. But that same engineering team, with flat spend, is going to have to start working on new products that differentiate, or doing things a lot more efficiently or better. R&D is not going to be able to help NI drive revenue growth if it just continues to do all of the same things it's been doing for the last four years. I'm also baffled at how NI expects to maintain 75% gross margins on systems and services. Ask any alliance member if they have 75% gross margins, and they'll peel over laughing. But that's a whole 'nother conversation I guess.
  15. For anyone interested in the business future of NI, I recommend viewing the "Virtual Investors Conference" from a few days ago. You can find it at www.ni.com/investors. There is a lot more useful and actionable information in these presentations compared to the re-brand event. Summary of what I took away from the investors conference: -- Flat spend on new product development for next 3 years (classified as "R&D"). -- Product price stability for next 3 years (flat gross margins expected). -- Focus on year-over-year revenue growth (including a lot more revenue from systems and software). -- Slash G&A to ensure net profit growth in case that whole revenue growth thing doesn't work out. I'm not really sure how revenue is going to grow with flat spending on engineering and sales. I guess they're just planning on doing everything a lot better? Unclear to me....
  • Create New...

Important Information

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