libnifalcon

/libnifalcon/1.0 Beta 3/libnifalcon-1.0-beta-3.tar.gz

Released at Sun, 15 Mar 2009 01:30:38 GMT by kmachulisIncludes files: libnifalcon-1.0-beta-3.tar.gz (194212 bytes, 14 downloads to date)[Download] [Release Notes]

libnifalcon is not dead! Just developing somewhat slowly since day job is taking up time. Here's the latest release update. We're almost to beta 3, hopefully it'll appear sometime in March. ==== Every time I plan a release day, without fail, the ... [More] last thing I do is think "Oh, wonder if things still compile on windows", and then the release gets delayed a week. So yeah, once again, I seem to have completely hosed windows building. At some point in February, I also broke libusb support and cmake generation for any platform with case-sensitive file system. I really gotta start testing on more than my macbook. :) Anyways, lots of fixes this weekend, as you can see in the commit logs on master. Windows is well on its way to working again (watch the beta3-win-fix branch if you're interested), both under mingw and visual studio this time. Also, libusb-1.0 seems to be almost completely working on OS X, using the newest dev commit of libusb. Firmware loading is still iffy at best, but once firmware is loaded, it works great. Not a huge development since libftdi already worked fine, but interesting nonetheless (especially since I didn't really have to put any work into it :) ). [Less]

libnifalcon is not dead! Just developing somewhat slowly since day job is taking up time.Here's the latest release update. We're almost to beta 3, hopefully it'll appear sometime in March.====Every time I plan a release day, without fail, the last ... [More] thing I do is think "Oh, wonder if things still compile on windows", and then the release gets delayed a week.So yeah, once again, I seem to have completely hosed windows building. At some point in February, I also broke libusb support and cmake generation for any platform with case-sensitive file system. I really gotta start testing on more than my macbook. :) Anyways, lots of fixes this weekend, as you can see in the commit logs on master. Windows is well on its way to working again (watch the beta3-win-fix branch if you're interested), both under mingw and visual studio this time.Also, libusb-1.0 seems to be almost completely working on OS X, using the newest dev commit of libusb. Firmware loading is still iffy at best, but once firmware is loaded, it works great. Not a huge development since libftdi already worked fine, but interesting nonetheless (especially since I didn't really have to put any work into it :) ). (0 comments) [Less]

libnifalcon is not dead! Just developing somewhat slowly since day job is taking up time.Here's the latest release update. We're almost to beta 3, hopefully it'll appear sometime in March.====Every time I plan a release day, without fail, the last ... [More] thing I do is think "Oh, wonder if things still compile on windows", and then the release gets delayed a week.So yeah, once again, I seem to have completely hosed windows building. At some point in February, I also broke libusb support and cmake generation for any platform with case-sensitive file system. I really gotta start testing on more than my macbook. :) Anyways, lots of fixes this weekend, as you can see in the commit logs on master. Windows is well on its way to working again (watch the beta3-win-fix branch if you're interested), both under mingw and visual studio this time.Also, libusb-1.0 seems to be almost completely working on OS X, using the newest dev commit of libusb. Firmware loading is still iffy at best, but once firmware is loaded, it works great. Not a huge development since libftdi already worked fine, but interesting nonetheless (especially since I didn't really have to put any work into it :) ). (0 comments) [Less]

libnifalcon is not dead! Just developing somewhat slowly since day job is taking up time. Here's the latest release update. We're almost to beta 3, hopefully it'll appear sometime in March. ==== Every time I plan a release day, without fail, the last ... [More] thing I do is think "Oh, wonder if things still compile on windows", and then the release gets delayed a week. So yeah, once again, I seem to have completely hosed windows building. At some point in February, I also broke libusb support and cmake generation for any platform with case-sensitive file system. I really gotta start testing on more than my macbook. :) Anyways, lots of fixes this weekend, as you can see in the commit logs on master. Windows is well on its way to working again (watch the beta3-win-fix branch if you're interested), both under mingw and visual studio this time. Also, libusb-1.0 seems to be almost completely working on OS X, using the newest dev commit of libusb. Firmware loading is still iffy at best, but once firmware is loaded, it works great. Not a huge development since libftdi already worked fine, but interesting nonetheless (especially since I didn't really have to put any work into it :) ). [Less]

Here's the changelog notes: --- * Release v1 beta 2 * Changed units in stamper kinematic core position readings from millimeters to meters * Changed units in stamper kinematic core force values to newtons (now matches HDAL) * Changed units in ... [More] FalconGeometry to meters * Updated falcon_test_cli to reflect unit changes * Added many more comments, though still nothing in depth * Removed falcon_mouse demo (many people have difficulty building and it doesn't work right, moved to own repository, http://www.github.com/qdot/libnifalcon_mouse\) * Fixed some const/reference passing arguments * Changed comm libraries to use pointers and prototypes to remove necessity for comm includes in lib headers * Fixed FTD2XX compatibility (comm driver hadn't been working in the past few releases) * Fixed compilation and compatibility for windows (now using mingw as test compiler) --- So yeah, if you're programming for the falcon right now, note that the units are different. By a orders of magnitude. Thank god we don't have a warranty, this is the first software I've produced where I can safely say going between version may cause your hardware to punch you. We're moving toward having less and less obvious hangups for v1, which is good. I'm really hoping the changes I made to the kinematics this week do the trick on that end. If so, we're down to commenting and small tweaks to the code, and beta 3 may just end up being v1. I'm dead set on having v1 out before the end of the year. [Less]

Here's the changelog notes:--- * Release v1 beta 2 * Changed units in stamper kinematic core position readings from millimeters to meters * Changed units in stamper kinematic core force values to newtons (now matches HDAL) * Changed units ... [More] in FalconGeometry to meters * Updated falcon_test_cli to reflect unit changes * Added many more comments, though still nothing in depth * Removed falcon_mouse demo (many people have difficulty building and it doesn't work right, moved to own repository, http://www.github.com/qdot/libnifalcon_mouse) * Fixed some const/reference passing arguments * Changed comm libraries to use pointers and prototypes to remove necessity for comm includes in lib headers * Fixed FTD2XX compatibility (comm driver hadn't been working in the past few releases) * Fixed compilation and compatibility for windows (now using mingw as test compiler)---So yeah, if you're programming for the falcon right now, note that the units are different. By a orders of magnitude. Thank god we don't have a warranty, this is the first software I've produced where I can safely say going between version may cause your hardware to punch you.We're moving toward having less and less obvious hangups for v1, which is good. I'm really hoping the changes I made to the kinematics this week do the trick on that end. If so, we're down to commenting and small tweaks to the code, and beta 3 may just end up being v1. I'm dead set on having v1 out before the end of the year. (0 comments) [Less]

Here's the changelog notes:--- * Release v1 beta 2 * Changed units in stamper kinematic core position readings from millimeters to meters * Changed units in stamper kinematic core force values to newtons (now matches HDAL) * Changed units ... [More] in FalconGeometry to meters * Updated falcon_test_cli to reflect unit changes * Added many more comments, though still nothing in depth * Removed falcon_mouse demo (many people have difficulty building and it doesn't work right, moved to own repository, http://www.github.com/qdot/libnifalcon_mouse) * Fixed some const/reference passing arguments * Changed comm libraries to use pointers and prototypes to remove necessity for comm includes in lib headers * Fixed FTD2XX compatibility (comm driver hadn't been working in the past few releases) * Fixed compilation and compatibility for windows (now using mingw as test compiler)---So yeah, if you're programming for the falcon right now, note that the units are different. By a orders of magnitude. Thank god we don't have a warranty, this is the first software I've produced where I can safely say going between version may cause your hardware to punch you.We're moving toward having less and less obvious hangups for v1, which is good. I'm really hoping the changes I made to the kinematics this week do the trick on that end. If so, we're down to commenting and small tweaks to the code, and beta 3 may just end up being v1. I'm dead set on having v1 out before the end of the year. (0 comments) [Less]

Here's the changelog notes: --- * Release v1 beta 2 * Changed units in stamper kinematic core position readings from millimeters to meters * Changed units in stamper kinematic core force values to newtons (now matches HDAL) * Changed units in ... [More] FalconGeometry to meters * Updated falcon_test_cli to reflect unit changes * Added many more comments, though still nothing in depth * Removed falcon_mouse demo (many people have difficulty building and it doesn't work right, moved to own repository, http://www.github.com/qdot/libnifalcon_mouse\) * Fixed some const/reference passing arguments * Changed comm libraries to use pointers and prototypes to remove necessity for comm includes in lib headers * Fixed FTD2XX compatibility (comm driver hadn't been working in the past few releases) * Fixed compilation and compatibility for windows (now using mingw as test compiler) --- So yeah, if you're programming for the falcon right now, note that the units are different. By a orders of magnitude. Thank god we don't have a warranty, this is the first software I've produced where I can safely say going between version may cause your hardware to punch you. We're moving toward having less and less obvious hangups for v1, which is good. I'm really hoping the changes I made to the kinematics this week do the trick on that end. If so, we're down to commenting and small tweaks to the code, and beta 3 may just end up being v1. I'm dead set on having v1 out before the end of the year. [Less]