Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by sam

  1. I found gitExtensions to be very good too. http://gitextensions.github.io/. If you coming from HG, this maybe a good choice to try.
  2. sam


    Yes, I was very committed to HP48, wrote many programs and games back in the day, which can still be found. I still use it daily, but as emulator on my Android. here is how: green shift -> units (#6) hit next couple times to get to Angles menu (top row of buttons) choose your deg Angle enter number hit degree menu at top you can hit enter to make a duplicate to convert a unit to another purple shift -> desired unit. this takes the top stack and converts (replaces the stack) hence I like to make duplicate.
  3. I Tried looking at your code but there are some missing functions that I can not run it. Mainly You have used LabVIEW add-on toolkit that everyone may not be using.: somewhere you have used Mathscripts: Looking at the scripts : can you use PureG or even "Formula Node". There are some links to office toolkit. Lastly, have you looked at Python, and more importantly LabPython? what is it that MView offers over-beyond LabPython? I ask because I'm interested..
  4. My c¢: 1: On LabVIEW 2011, in the build : Advanced, turn off SSE2 2: On LabVIEW 2011, in the build : Advanced, Check "Use LabVIEW 8.6 file layout" 3: other combination of 1 & 2 The other thing I noted your second cpu is N270, which I believe is Netbook ATOM kind. it my handles Math and double/single operation differently. I can't see why it would change from 8.6 to LV11, but it may have something to do with SSE2 optimization. looking at Wikipedia both Celeron and Atom support it. just some ideas.
  5. just my 2¢: You can always do (translate) a recursive algorithm with a while loop. With above suggestion of clusters instead of Classes and while loop you should gain significant speeds. Never mind my post, I looked at the code after I posted. and I don't see a Recursive implementation.
  6. The easiest approach is to install Python2.5, you can use other (newer) python, but it takes some work and to be honest you can get all you need from Python2.5.
  7. By just looking at your screen captures I can tell you are not passing correct data type to your dll. Of course posting source code can calp you more. You are defining your ADD function with aDD( char a, char b, uchar *c) but calling with aDD(int,int); 1: Char and Int are two very different data type. 2: Char would not be first choise for an ADD parameter, int or double; 3: char *, is also not a very good choice for return parameter. Hope this helps
  8. Well, I've done exactly what you are asking, so it can be done. About ten years ago I had to take out any references and use of IMAQ in one of our Imaging Software. There was heavy use of IMAQ and this is how I went about it. Step 1: I used another Imaging toolkit that had all the imaging functions that I needed This is what I ended up going with http://gromada.com/mcl/. If I had to redo the project I would use OpenCV now http://opencv.willowgarage.com/wiki/ Speaking on OpenCV there is already a toolkit that uses openCV called iVision http://www.hytekautomation.com/Products/IVision.html Step 2: Create a control to display images, for this I created an ActiveX control. this control was also a wrapper around the functions that are available via the Imaging Toolkit you have chosen in step 1. Step3: Every activex control has a Draw(Refresh) option. This is were you will obtain the Device Context of the ActiveX control and perform your draw code. I hope this help you, now at least you have a starting point and know that It can be done.
  9. checkout NSIS, Very professional and feature packed. Cost: Free http://nsis.sourceforge.net/Main_Page
  10. To have Sqlite working for any platform you can use the precompiled libraries that SQlite website already provides: Windows: http://www.sqlite.org/sqlite-3_7_2.zip Linux: http://www.sqlite.org/sqlite3-3.7.2.bin.gz Mac OS X (x86): http://www.sqlite.org/sqlite3-3.7.2-osx.zip If you change the Source Code Of Sqlite to fit your product, then I don't think you can call it Sqlite , because you are changing the source. If you are using a C-Wrapper around it then you are introducing another level of redirection and extra code to maintain. A c-wrapper will force you to reduce the functionality that you can provide thru your wrapper. I have been down that road and it's not pretty. Have a look at the documentation of sqlite here: http://www.sqlite.org/c3ref/funclist.html. Will I have access to ALL the features of Sqlite described in their documentation? If a product is PAID then I would want/expect it. Because the reality is the Sqlite project is mature and a throughly tested product, and simply exposing the functions doesn't qualify for a commercial product. I know you are anticipating supporting the product, but how much of this support is going to be directed toward your-method-of-exposing Sqlite DLL, and actual fault-of-sqlite. I don't know if I have been clear. Like I said earlier just wrapping the sqlite3.dll for LabVIEW is not going to be enough, you need to separate the programmer from the database, which you said you have such tools (Great), but also provide all the advanced functions that Sqlite itself already provides , see documentation. I am not against a paid Sqlite-LabVIEW toolkit but only hope that a really Solid and worthy Toolkit is released that everyone can benefit, even the one who are capable of doing the work.
  11. I can't share the VIs I am using, but I will give you the core functionality of Sqlite VIs that Import-Dll creates. From these VIs you can see how to change the VIs created by Import DLL. Let me know if you have any questions. I have included the Sqlite3.dll, but you should've already have this Dll if you are interested in Importing it to LabVIEW :-) Sqlite.Tester.zip
  12. I don't know how much more clear I can be, but one of the VIs "That-You-Supply" has incorrect implementation the vi "That-You-Supply" if used will cause my application to misbehave. Because IF My application Steps are generated as a function and now my function generate empty steps. You can fix it your leave it alone.
  13. I have used Sqlite since 2004, my first implementation I used a wrapper dll around the Sqlite3.dll. But now you can use the DLL-Import feature of LabVIEW and import the Sqlite3.dll and have yourself a fully working toolkit. After import you have to replace a couple of Type-controls to Int32 and you will be done in less than an hour. I don't want to be mean but what are the difference between your toolkit and what Dll-Import makes. I can appreciate a Toolkit that simplifies working with LabVIEW data and Database so that the programmer does not have to use a single SQL statement.
  14. With Any reference you have to be careful to use a shift register to use the reference in a loop. because if the loop does not execute a tunnel-out will have a null (default data), but a shift register will carry the correct data out of the loop. To make my point see attached snippet
  15. Bug: The EnQueue VI should use SR for the Queue reference because if you have an empty array as your input the Output Queue reference will be null.
  16. We have Mechanical, Electrical, and Software positions posted. You can find more information by selecting the Ann Arbor site from this page: www.advancedphotonix.com/careers Please don't reply to me direct - You must follow the process through the website.
  17. Try flyspray, it's simple, easy on the eyes, and free. Open Source Their webpage is down right now. you can get it here http://sourceforge.net/projects/flyspray/ or see a demo here: http://bugs.splitbrain.org/
  18. 1,301 downloads

    Copyright © 2006, Sam Behashtei All rights reserved. Author: Sam Behashtei --see readme file for contact information Description: Data.vi V1.0.0 LabVIEW Versions 7.0,7.1 The purpose of the VI is to demonstrate how to save all your application’s parameter in one central INI file. Using this method will reduce errors and eases debugging. This Data VI has the following functionality 1: Can be used as a Central Data Repository for your Application. 2: It allows access to the Data via SET/GET method. 3: It uses semaphores to stop any race conditions and (concurrent SET access to data) It will allow parallel "READ-ONLY" access to the Data. 4: A Function to Save all of the DATA to an INI file. 5: A Function to Load a previously saved Data from the INI file. Library Dependency: OpenG: oglib_variantconfig-2.6- OpenG: oglib_lvdata-2.5-1 http://web.archive.org/web/20071205114227/http://www.openg.org/ Version History: 1.0.1: Added LabVIEW 7.0 code. 1.0.0: Initial release of the code.
  19. Version 1.0.1


    Copyright © 2006, Sam Behashtei All rights reserved. Author: Sam Behashtei --see readme file for contact information Description:: In most modern application, in web based application, the user input Textbox, or (String-Control) have the ability to Auto-Complete the words being typed. This utility helps the programmer give the Auto-Complete behavior to a LabVIEW String. Version History: 1.0.1: The mechanism to store suggestion list has been changed. 1.0.0: Initial release of the code.
  20. QUOTE (Jim Kring @ Dec 31 2008, 02:20 PM) I bet internally the Dialog or Linking Algorithm is dropping the ending ( .svn-base). maybe searching for .vi and assuming the [ Path.Name.vi ] as the vi name. To clarify my problem is not how to fix this error, but how to prevent it from happening, I can fix the errors in any number of methods, some being the ones mentioned. The interesting point here is that I get this error on most of my project, but some of you here never seen it. therefore pointing to my style of programming ( Folder Structure maybe) :-) That inevitability causes Linking Problems. Like stated earlier I use Auto-Pop heavily, and Auto-pop adds the ".svn" folder to the project. It would be very nice to have an option setting for LabVIEW to ignore some file types and names.
  21. I am attaching this Picture to show VIs linked incorrectly. Notice how ".svn" is a parent folder for the VIs
  22. I am using LabVIEW 8.6, but I have seen it as well in LabVIEW 8.5. Jim, I think you are correct regarding auto-pop. feature leading to cross-linking. I will stop using auto-pop and see if cross-linking is reduced or gone. Also I don't think using "_svn" instead of ".svn" will fix this cross-linking. If I remember "_svn" was a hack to fix a bug with ASP.NET 1.0. I think ".svn" was a reserved word in ASP.NET. Also this hack no longer is necessarily for current ASP.NET Aristos, I always rename using LabVIEW file save as. I try to never rename in Explorer, exactly for fear of cross-linking.
  23. Hi, I have a concern regarding SVN. I have been using SVN since/before 2004. Lately I am having a lot of VIs that are incorrectly linked to the .SVN folder; I am blaming the project explorer. I am having a lot of frustration with this, and hate the fact that I need to relink more and more VIs to the actual file from the temporary SVN file. If there isn't a solution found for this incorrect linking I will abandon my favorite SCC. Has anyone else ran into this? What do you do to avoid false linking? As always I appreciate your kind help.
  • Create New...

Important Information

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