Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Reds last won the day on August 13 2020

Reds had the most liked content!

Community Reputation


About Reds

  • Rank

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2011
  • Since
  1. 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 sin
  2. 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.
  3. 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,
  4. 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.
  5. 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 system
  6. A few years ago there was a great presentation at NI Week where someone in the community demonstrated how to write a core measurement application in LabVIEW, while using C#/.NET for only the top-level GUI elements. Does anyone remember or have a copy of this presentation? I seem to recall there was a video of this presentation online at some point in the past?
  7. Thank you AQ. I appreciate these comments. This is important information for so many of us who make our living inside the NI ecosystem. I wish NIC was generally more communicative about their changed view of the world.
  8. Forget about colors and fonts, I want to better understand this quote from Austin Business news: Shelley Gretlein, NI’s vice president of global marketing, likened its old business model to being a Home Depot where companies can get the materials to build a treehouse. "More and more, customers are moving so fast, they don’t have time to make the treehouse," said Gretlein, a 20-year veteran of the company who spearheaded the internal group that revamped it inside and out. "They don’t have the time, and budgets and teams are shrinking. You need to deliver the whole treehouse."
  9. For those of you who haven't seen, Dr. T is transitioning out of CEO role: http://www.evaluationengineering.com/ni-announces-transition-plan-davern-become-ceo-president-january-1
  10. For me, less of my time is spent hardcore coding or engineering these days. More of my time is spent doing sales, marketing and business building activities. That's just been the trajectory of my career/business recently. So now I consume a lot more sales & marketing blogs. I have seen the same sort of dynamic at work over at www.Slashdot.org. We're all a bunch of old guys having conversations about management. Finally, it seems like everyone who used to hang out over at info-labview moved over to this website when e-mail lists became passé. Thus, LavaG didn't need to "advertise" to g
  11. Yes, I took a look at NI Requirements Gateway, but I thought it was weird that that tool was so focused on documenting *where* in the source code a requirement is implemented. That doesn't seem useful to me at all (maybe it is to the medical guys and others who are heavily regulated). I think (?) what I'm really looking for is something that links requirements to test results, not requirements to source code locations. I guess, I'm not really sure what I'm looking for, but I'd like to hear from people who have gotten more sophisticated than Microsoft Word and your standard Defect Tracking
  12. I'm curious to hear what tools you guys are using to write and track software requirements/specifications. I'm especially curious to know if any of you have a workflow that can not only track requirements, but also document pass/fail test results for a given requirement in a given software release. For myself, I'm using Microsoft Word and FogBugz....i.e. I write the requirement in Word and then if it doesn't work, log it as a defect in FogBugz. However, there is a really naïve underlying assumption to this workflow: namely, that I would never release software that doesn't meet a requirem
  13. It is true that you don't actually have to register your software in order to obtain copyright protection. Copyright protection exists "automatically" as soon as you create the work. However, if you DO register it (in the US at least), you are entitled to recover far more damages in the event of a willful infringement. This means that you can actually find a lawyer to accept your copyright infringement case on a contingency fee basis, and don't have to front a huge wad of money to fight a willful infringer. If you DON'T register your software, you are only "protected" to the extent that
  14. Thought I would update this thread to let everyone know that apparently NI has (recently?) updated their EULA to include the following useful loophole (emphasis mine): You include the following copyright notice "Copyright [insert year] National Instruments Corporation. All Rights Reserved." in the Authorized Application's About Box (if applicable) and in (i) any applicable written documentation or, (ii) if no such documentation exists, in a "read me" or other .txt file distributed with each copy of the Authorized Application; (you may instead, or in addition, include your own copyright no
  15. Have any of you obtained a US Copyright for software you developed in LabVIEW? If so, did you file your software copyright as "Literary Work" or "Work of the Visual Arts"? To provide context, here is some actual language from the US Copyright Office circular: Because computer programs are literary works, registration as a Literary Work is usually appropriate. However, if pictorial or graphic authorship predominates, registration as a "Work of the Visual Arts" may be made.
  • Create New...

Important Information

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