Sam's Blog

Introducing LabVIEW MakerHub

I'm excited to announce that LabVIEW Hacker is getting a new name, some new colors and is officially sponsored by National Instruments. I created LabVIEW Hacker in January 2013 as a place for makers using LabVIEW to learn, share projects, collaborate and inspire one another. I couldn't be more happy with the way the community has developed over the last two years and while our name and colors are changing our purpose is not.

If you have any questions or feedback while we're making the transition please feel free to post in the MakerHub forums (or use one of the methods in the contact section if you are having trouble with the forums).

The new website is just the beginning; check back for more big announcements in the coming weeks.

-Sam Kristoff

2015/02/25 20:34 · samkristoff

ASU Higher Education Maker Summit


I'll be in Chandler Arizona the next couple days to attend the ASU Higher Education Maker Summit where I'll be on a panel discussing Bridging the Gap between Industry Standard Tools and the Makerspace.

In order for students to be prepared to work in industry or pursue an entrepreneurial career, students need access to industry standard tools used in professional workplaces. In the past, the adoption of these tools has been cumbersome for many reasons including cost and affordability, access and support availability; however, there are several on-going initiatives aimed at removing these obstacles that will greatly benefit makers. Join this panel of visionary leaders from both industry and academia to discuss how they are breaking down barriers to help makers gain access to these industry standard tools.

Panelists:

  • Mark Hatch, CEO and Co-Founder of TechShop
  • Mitzi Montoya, Vice President and University Dean of Entrepreneurship & Innovation, Arizona State University
  • Clint Cole, Founder and CTO of Digilent
  • Sam Kristoff, Founder of LabVIEW Hacker
2015/01/20 18:28 · samkristoff

NI Week 2014 - LabVIEW Hacker Home Automation Demo

I got to meet a few of my fellow LabVIEW Hackers at NI Week last week. For those of you who were not able to make it, here is the LabVIEW Hacker Home Automation demo from the NI Week 2014 expo floor. We're using an Xbox One controller, PS4 controller, and Leap Motion to control Phillips Hue lights, XBMC Media Center and the Nest Thermostat. All of the libraries used in this demo are free and open source and available to download from the LabVIEW Hacker website now!


2015/01/20 18:28 · samkristoff

NI Week 2014

NI Week 2014 is this week. You can watch the keynotes live here.

If you're at NI Week check out the LabVIEW Hacker Demo on the expo-floor (LabVIEW Home Automation) near center of the LabVIEW pavillion and make sure to join us for the LabVIEW Hacker session Wed 8/6 at 3:30 in room 16B. We'll do live demos of some of the new LabVIEW Hacker interfaces and share our open source LabVIEW development process and talk about how you can become a LabVIEW Hacker!


2015/01/20 18:28 · samkristoff

Kinect For Windows v2

Update 7/25/2014

I've been pretty busy this week and haven't gotten as much time to play with the Kinect as I wanted. I've played around with the demos and created my own little C# demo and everything was working well. Unfortunately I'm stuck on a .net error that only shows up when I move to LabVIEW (and only after 1 successful run, then I have to restart LabVIEW). I must be leaking a reference somewhere but I haven't been able to track it down yet. Stay tuned!

Update 7/18/2014

TLDR: ORICO PRU3-4P 4 Port USB 3.0 PCIe works with Kinect for Windows v2, but only with the default Microsoft drivers, not the Renesas drivers.

I got my ORICO PRU3-4P 4 Port USB 3.0 PCIe card today. It says it has a NEC controller, but NEC and Renesas have merged so I decided to roll the dice in favor of 1 day amazon prime shipping. I'm using Windows 8.1 and it automatically loaded drivers for the card and when I connected the Kinect v2 … it works!

I decided to load the Renesas drivers for the PCIe USB adapter assuming the manufacturers drivers should be better than the generic Microsoft drivers, however after a reboot the Kinect no longer worked. Device manager reported that the Kinect could not start with the Renesas drivers installed, so I rolled back the drivers and everything is working again. What a head ache. I'm still excited to start playing with the new Kinect for Windows v2, but the out of the box experience leaves something to be desired.


Update 7/17/2014

It turns out that the Kinect for Windows v2 is very picky about the type of USB 3.0 controller you connect it to. If you're getting error messages that say 'not enough USB controller resources' or the demo projects just show empty windows you may need to get a new USB 3.0 controller from Renesas or Intel for your connect to work.

Microsoft lists the USB 3.0 requirements here: http://www.microsoft.com/en-us/kinectforwindows/purchase/sensor_setup.aspx

Stay tuned for updates and a suggestion on a tested working USB 3.0 controller. Visit http://www.labviewhacker.com for the most recent updates.



I pre-ordered a Kinect for Windows v2 and it arrived today! Check out my unboxing video below and check back for video updates throughout the day tomorrow (I'm going hackathon style!), and a LabVIEW Interface for Kinect v2 soon.


2015/01/20 18:28 · samkristoff