Jump to content
News about the LabVIEW Wiki! ×

All Activity

This stream auto-updates     

  1. Today
  2. MartinT MartinT joined the community
  3. Neil Pate
    Thanks! I did actually click there but thought it was just for patches.
  4. LogMAN started following boolean or Boolean? and other wiki style questions..., Offline Installers for 2019 and How do you report or delete articles on the wiki?
  5. LogMAN
    The "Individual Offline Installers" link below the download button points to the offline installer.
  6. Neil Pate
    Can anybody point me in the direction of the offline installers for 2019 (+toolkits/drivers for FPGA and RT). I can only find the 3.5 MB web installer for pretty much anything. Thanks!
  7. aroob2498
    Is there a way to use this as a virtual SSH terminal as well? I'm trying to communicate to a piece of hardware where it's only connection is via SSH terminal. Thanks for sharing what you have so far!
  8. hooovahh
    Wonderful suggestion. Most LAVA members that are older than some date have a wiki account and are welcome to update it.
  9. ShaunR
    When the compiler doesn't care, why should I? The view I take is that "Style Guides" are just that. GUIDES, not LAWS. If "boolean" was chosen, what do you do about capitalisation at the beginning of a sentence? There are arguments for grammatical considerations but I'm "meh" when it comes to programming type names, classes at. al. These things are just a distraction - form over function. Read it and weep:
  10. LogMAN
    I found some spam on the wiki and would like to request deletion, but there doesn't seem to be an option (probably because I don't have the rights). So, is there a way to notify administrators (currently only @Michael Aivaliotis?) directly or should we open new topics here? Here are the offending pages. https://labviewwiki.org/wiki/Is_there_some_magic_to_get_URLForUbiquityContainerIdentifier_to_work_besides_setting_up_the_Entitlements_Stupid_http://nfltickets.me/baltimore-ravens-tickets/_thing_keeps_returning_nil https://labviewwiki.org/wiki/Being_The_Best_Pet_Owner_In_Town:_Tips_And_Tricks_by_Gita_I._Reimnitz https://labviewwiki.org/wiki/Caring_For_Your_Kitty:_Top_Tips_And_Advice_by_Sindy_P._Lanterman https://labviewwiki.org/wiki/Jijijijijiji_te_dije_q_lo_usaras_http://convenientcarpetcleaning.com/washington/carpet-cleaning-in-pasco-wa/_rapidooo_merf https://labviewwiki.org/wiki/Prohibir_el_acceso_a_los_Colocolinos_que_portan_sus_entradas_es_sumar_mas_violencia_a_una_actividad_http://kyleleon-musclemaximizer.com/reviews/_que_esta_en_crisis https://labviewwiki.org/wiki/This_man_just_said_she_get_more_miles_than_a_18_wheeler_smh_http://convenientcarpetcleaning.com/new-mexico/carpet-cleaning-in-farmington-nm/_mauryshow Edit: There also seem to be some orphan files that should be released of their existence: https://labviewwiki.org/wiki/File:Bomboniera_solidale_matrimo_2359.jpg https://labviewwiki.org/wiki/File:Betting_on_nfl_5601.jpg https://labviewwiki.org/wiki/File:Bitcoin_piracy_3126.jpg https://labviewwiki.org/wiki/File:Binary_options_3986.jpg https://labviewwiki.org/wiki/File:Abogados_Madrid,_Despacho_de_Abogados_laboralistas_2813.jpg https://labviewwiki.org/wiki/File:50_shades_darker_1556.jpg https://labviewwiki.org/wiki/File:Bomboniere_matrimonio_4754.jpg https://labviewwiki.org/wiki/File:Buy_dianabol_3532.jpg https://labviewwiki.org/wiki/File:Cakes_4375.jpg https://labviewwiki.org/wiki/File:Capetown_wedding_venues_1999.jpg https://labviewwiki.org/wiki/File:Cheap_costume_jewellery_2542.jpg https://labviewwiki.org/wiki/File:Cercacasa.it_5533.jpg https://labviewwiki.org/wiki/File:Cheat_hidden_chronicles_3336.jpg https://labviewwiki.org/wiki/File:Chicago_tuckpointing_2777.jpg https://labviewwiki.org/wiki/File:Christmas_bows_1816.jpg https://labviewwiki.org/wiki/File:Computer_system_clock_2606.jpg https://labviewwiki.org/wiki/File:Computer_training_1367.jpg https://labviewwiki.org/wiki/File:Contact_Us_-_4664.jpg https://labviewwiki.org/wiki/File:Bomboniera_solidale_matrimo_2838.jpg https://labviewwiki.org/wiki/File:Descuentos_3610.jpg https://labviewwiki.org/wiki/File:Does_wartrol_work_4699.jpg https://labviewwiki.org/wiki/File:Dog_ideas_1934.jpg https://labviewwiki.org/wiki/File:Driving_lessons_in_solihull_1129.jpg https://labviewwiki.org/wiki/File:Driving_schools_in_Solihull_1174.jpg https://labviewwiki.org/wiki/File:Find_out_more_about_Access_control_2363.jpg https://labviewwiki.org/wiki/File:Fixing_laptop_toronto_1598.jpg https://labviewwiki.org/wiki/File:Folding_camper_transport_884.jpg https://labviewwiki.org/wiki/File:Food_distributors_4956.jpg https://labviewwiki.org/wiki/File:Going_here_2091.jpg There is no end to this... https://labviewwiki.org/wiki/File:Government_Debt_Relief_Programs_2346.jpg https://labviewwiki.org/wiki/File:Graphic_design_schools_2392.jpg https://labviewwiki.org/wiki/File:Hair_Style_Tips_4044.jpg https://labviewwiki.org/wiki/File:Healthcare_Administration_Training_Riverton_WY_1392.jpg https://labviewwiki.org/wiki/File:Help_available_5233.jpg https://labviewwiki.org/wiki/File:Here_3240.jpg https://labviewwiki.org/wiki/File:Hidden_chronicles_cheats_2585.jpg https://labviewwiki.org/wiki/File:Hidden_chronicles_cheats_4737.jpg https://labviewwiki.org/wiki/File:How_to_sell_gold_3730.jpg https://labviewwiki.org/wiki/File:Howto-grow-yourpenis.net_4497.jpg https://labviewwiki.org/wiki/File:Htc_one_x_update_2387.jpg https://labviewwiki.org/wiki/File:Illinois_home_inspector_directory_5003.jpg https://labviewwiki.org/wiki/File:Juridische_vertalingen_5007.jpg Saving because I don't want to loose progress... https://labviewwiki.org/wiki/File:Laserbehandeling_ontharing_1003.jpg https://labviewwiki.org/wiki/File:MerrimanSnippet.png https://labviewwiki.org/wiki/File:No_No_hair_removal_reviews_2507.jpg https://labviewwiki.org/wiki/File:Paintball_1581.jpg https://labviewwiki.org/wiki/File:Pc_technical_support_toshiba_scarborough_4170.jpg https://labviewwiki.org/wiki/File:Personalised_christmas_sacks_and_stockings_5390.jpg https://labviewwiki.org/wiki/File:Pool_service_columbia_sc_4213.jpg https://labviewwiki.org/wiki/File:Privacy_Policy_959.jpg https://labviewwiki.org/wiki/File:Pure_argan_oil_for_face_2042.jpg https://labviewwiki.org/wiki/File:Read_here_4467.jpg https://labviewwiki.org/wiki/File:Reputation_management_1152.jpg https://labviewwiki.org/wiki/File:Reviews_3461.jpg https://labviewwiki.org/wiki/File:San_Antonio_Interior_Decorator_2940.jpg https://labviewwiki.org/wiki/File:San_Antonio_Interior_Decorator_4834.jpg https://labviewwiki.org/wiki/File:San_Antonio_Interior_Design_3474.jpg https://labviewwiki.org/wiki/File:Schedule_a_carpet_cleaning_2023.jpg https://labviewwiki.org/wiki/File:Smartrank_778.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_1160.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_1318.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_1515.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_2486.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_2917.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_3584.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_3672.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_3744.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_4150.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_4849.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_5002.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_5239.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_5436.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_757.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_880.jpg https://labviewwiki.org/wiki/File:Too_much_iron_in_your_blood_1972.jpg https://labviewwiki.org/wiki/File:Toppik_uk_4349.jpg https://labviewwiki.org/wiki/File:Used_iphone_3_for_sale_1589.jpg https://labviewwiki.org/wiki/File:Valley_view_casino_1963.jpg https://labviewwiki.org/wiki/File:Video_promotion_by_ytpros_2952.jpg https://labviewwiki.org/wiki/File:Watch_avi_on_android_3765.jpg https://labviewwiki.org/wiki/File:Web_design_1869.jpg Done.
  11. Gae Gae joined the community
  12. Jacob Schnitzlein Jacob Schnitzlein joined the community
  13. Gribo
    Instead of Access, you can use SQL server Express. The server can be 32 or 64 bits, local or remote, as long as the ODBC driver matches LV's bitness, you should be fine. If you used only NI DB connectivity library, conversion effort will be minimal, mainly syntax differences between the 2 systems.
  14. LogMAN
    LabVIEW doesn't backfire for misspelled words, which means we don't freak out every time we see one. Here are a few suggestions for draconian rules on the LabVIEW wiki 😇 1.1 Uploading sample code to the wiki Put input terminals to the right, output terminals to the left (on the block diagram and VI terminals) Use backwards wiring Show terminals as icons Don't use shift registers (use local variables instead) No error handling (disable debugging) Take a screenshot with your mobile phone (compress as much as possible before uploading) Seriously, though. The wiki should have some guidelines for the structure and content of each article. Otherwise it will decay to some kind of link collection (formally known as favorites) with no added value (example). Those guidelines should be more general, as in: A page must be informative It should focus on one topic (create new pages for other topics) Citations must be marked clearly using the format "<blockquote>Someone said this!</blockquote>" ... My point is: This page should be updated (last edited on 7 October 2007, at 11:18): https://labviewwiki.org/wiki/LabVIEW_Wiki:Manual_of_Style
  15. aroob2498 aroob2498 joined the community
  16. Shruti Shukla Shruti Shukla changed their profile photo
  17. Lipko
    Hi again! This time I have the following problem: I want to do simple queries on a small .accdb as a part of a simple tool application. Labview's connectivity toolkit method works fine as far as every user is on the same Office bitness (32 vs 64 bit). But in our case, some machines have 64 bit Office and some 32 bit. This results in driver compatibility issues and our IT policies are so strict that in the near future our local admin rights might vanish too, making driver install requests for a simple tool is too tedious. This 32-64 bit transitional state can last for several months and I would prefer to have a general solution than to make 32bit and 64bit builds (as far as I know this would also solve the issue, but I'm on 32 LV at the moment). Since loading the whole database is an option (the whole file is just 2 MB at the moment and it won't grow in the near future when hopefully all collagaues will be on the ame ground), I'm hoping there's a more "platform independent" (office and Windows 7/10 are given) solution to read the contents of .accdb files. My googling yielded solutions for SQL database access. Thank you for any hints in advance!
  18. connorbo2020 connorbo2020 joined the community
  19. 杨国烨 杨国烨 joined the community
  20. hooovahh
    Maybe it has something to do with the fact that we have a more graphical mindset and don't care as much as long as we can convey a thought. Maybe because we are primarily engineers? Or this is a wiki with a relatively small support base? In any case thank you for your wiki contributions.
  21. andriharyono andriharyono joined the community
  22. Antoine Chalons
    Please post a picture 😂
  23. Aristos Queue
    You people are so laid back and forgiving. I’m an editor on multiple wikis across cyberspace, and none of the others are anything less than draconian. Capitalization whatever?! Wow. I’m going to need to wear my oversized Hawaiian shirt and cargo shorts when I’m editing, just to get in the right state of mind! 🙂
  24. mustafa aljumaili mustafa aljumaili changed their profile photo
  25. JKSH
    These are purely stylistic issues. I'd personally prefer Boolean and subVI, but I'll follow the community guidelines (when they are produced). This one has ramifications for the ease of understanding of an article (especially for newcomers). I'm not sure what's best here. Perhaps we can let NI spearhead the effort to "normalize" the use of "G". We can stick to "LabVIEW" for now since it's more common, but switch over to "G" later when NI's efforts bear fruit. I'm with Rolf; same-page is much more useful in the forseeable future.
  26. JKSH
    This thread is about literature, not code. It's a question of finding a balance between practicality and professionalism. Side A can reasonably accuse Side B of being a Grammar Nazi while Side B can reasonably accuse Side A of being sloppy. My response would be "be consistent within a project". Feel free to have different conventions across different projects. So for the Wiki, we should at least be consistent within a single article or group of closely-related articles. Some might even argue that the whole Wiki is a single project. No, as long as you don't care when people write "LabView".
  27. Yesterday
  28. Nicola Tampelloni Nicola Tampelloni changed their profile photo
  29. ShaunR
    This is a historical "problem" due to compilers being case sensitive. This was one of the reasons that I went for Pascal compilers over C since Object/Open/Turbo Pascal is case insensitive and boolean or Boolean are synonymous (as a type). I've always maintained that there is no excuse for case sensitvity as it only introduces errors, obfusicates and increases foot-shooting but has zero benefits (unless you consider obfusication a benefit which is arguably a security risk). I've had many conversations with C/C++ programmers over capitalisation of types and function names (initial caps vs camel case vs lower case etc) and my response has always been "whatever". Do we really need to bring this problem to a wiki, of all things, about a language in which case is irrelevant?
  30. hooovahh started following boolean or Boolean? and other wiki style questions...
  31. hooovahh
    All very good points and good concerns. Personally I would capitalize Boolean, but I may forget occasionally. I would also prefer subVI as I've gotten used to the NI standard. I can see the confusion with LabVIEW and G, and often I go back to what the community at large uses. If I say "My programming language of choice is G" some may confuse this with GCode, or something else. If I say LabVIEW I think that conveys what I mean to the general public more. For this reason I default to "LabVIEW" but at times will say G. Public opinion may change, and that may mean updating the wiki. And if there are specifics I'd prefer separate pages for 20xx and NXG, but whatever. One thing you might not be aware of is that there is a place for page specific discussions on the Wiki Talk Page. You could make an edit, but leave a comment asking for direction or leave it open to preference. That being said I think the opinion of most moderators on the Wiki is more that getting something which is non-perfect, is better than having nothing. I'd encourage others to make pages and fill in what they can, even if they are unsure of how to handle some of these differences. Things can always be cleaned up and refined later.
  32. Antoine Chalons
    I agree with Rolf, I think most people are not as strict as you are. And while we're at it, what version of english should be used? American english or British english or any other flavour. I thought about this when I read capitalising spelt with "z" 😂
  33. Breizh_Instruments started following Free LabVIEW WinSCP Library
  34. Breizh_Instruments
    Hello! Thank you for this Lib! It is very usefull and smart to use!
  35. Lipko
    Thanks for the replies! As usual, I did things wrong. This time it was with the testing. When I started I tried with the actual property names with the illegal characters. But the tested files (which were chosen randomly) were probably all files that was once re-saved with Diadem. Then I tried with the underscores, this time probably on totally different files which were never re-saved in DiAdem. Funny thing is that I tested multiple times with the underscore, seeminly always on non re-saved files... Anyways, Now I look for both the original property and the fixed property. Thanks Antoine for the illegal characters' list. I used it as the search+replace regex search string.
  36. Rolf Kalbermatter started following boolean or Boolean? and other wiki style questions...
  37. Rolf Kalbermatter
    While you bring up valid points here, I think there is no standard whatsoever in the community about this so far. Everybody does as he or she feels at that particular time of the day and may do it different the next day. So if you want to bring this up, it may be a good idea to document it somewhere in the wiki. Basically start some sort of recommended style guide there. Obviously not everyone will read it and even if someone does he won't be shot if he does not follow it. 😀 About your last point I would personally prefer to have different sections on the same page for now. I also don't see deprecation of pages going to happen anytime soon and definitely not as a separate task that anyone would take upon himself. If something will be deprecated in the future it will be likely as part of editing a page for other purposes such as adding information about new features or similar. And it is anyhow at least 7 years in the future as NI committed at some time to a support timeframe of 10 years for LabVIEW CG after the first NXG version was released. 😁 With the current progress of LabVIEW NXG that might be about the time it reaches feature dominance over LabVIEW CG. 😆
  38. Last week
  39. Nguyễn Minh Tú Nguyễn Minh Tú changed their profile photo
  40. Lipko
    Yes, I meant get properties, and it didn't return those properties. I tried TDMS viewer, some 3rd party labview viewer and those didn't find my properties either Okay, I will try a few things next week (testing with proper property names). If it's successful, I'll rewrite my set properties code. I'll make two versions of the getter to deal with the old files with the illegal property names. Or something...
  41. JKSH
    If was written successfully, then it can be read too. The key is to find out what name was stored in the TDMS file. If you call TDMS Get Properties.vi without wiring the "property name" and "data type" input, you're meant to get an array of all available properties in the "property names" output. I presume you meant TDMS Get Properties.vi? If so, then that's very weird. My next guess would be you're opening different files in LabVIEW vs. DIAdem. Try calling TDMS Get Properties.vi without the name inputs immediately after you write the custom property.
  42. Rolf Kalbermatter
    Well in that case the remark about the DLLs having to be compiled for ARM was really off. That is for Windows IoT installations on targets like the RPi and similar boards which all have an ARM CPU (and accordingly can't run Windows IoT Enterprise either which is a pure x86/x64 install). It all depends on which C compiler they used to create those DLLs. Until Visual C 2015 or so each Visual C version come with it's own specific C runtime library that had to be installed on every target on which you wanted to run an executable or DLL created with it. While many parts of Windows are compiled with Visual C too and therefore cause the Windows installation to come with the needed C runtime support already installed this can and will vary depending on the Windows version and the amount of extra tools and utilities that you install. Also any extra custom application you install such as LabVIEW also comes of course with the necessary C runtime support that gets installed if not already present on the system, but depending on all this a particular C runtime version may or may not be present on any particular system. Basically you should never copy DLLs to a target system but install them with the proper installer for them which hopefully takes care about installing the correct C runtime support too.
  43. FixedWire
    Yes, correct Rolf. The target was the enterprise version & that's why it ran in the first place. Interestingly enough installing the exe on 3 other machines under Win10 resulted in the 2 working & the 3rd not finding the dll just like the Win10 IoT. With a new build it suddenly didn't find the dll on one that did work. With not having time to debug I created an installation and the program worked since even with new builds. On regular Win10 there shouldn't have been an issue... At this point I'll try and link the latest 64bit Postgres dll's & try that.
  1. Load more activity
×
×
  • Create New...

Important Information

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

  I accept