Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. I would highly recommend that you use one of the existing modbus libraries to communicate with the E5CN. See: OR: https://github.com/NISystemsEngineering/LabVIEW-Modbus-API
  3. I noticed on sourceforge that there is a version 4.2 of OpenG Zip. Will it be released as a package anytime soon?
  4. Hello, experts, in the current description of the NI Vision Acquisition Software it says: http://www.ni.com/pdf/manuals/375130k.html Deprecated Features ◾NI - IMAQ 19.0 .... ◾Removed support for LabVIEW Real-Time targets running Phar Lap ETS OS Will the OS Labview Real Time (Phar Lap ETS OS) be discontinued and is there an alternative based on Linux? a good time Jim
  5. Hi every one, I can connect and run E5CN tempt. controller to Labview through Modbus. Attached files are my programming test for E5CN. I think E5CC has the same protocol with E5CN. I hope these files can hep you. E5CN_test new.vi MBcrc (2).vi String Hex to Interger Decimal.vi
  6. Hi every one, I can connect and run E5CN tempt. controller to Labview through Modbus. Attached files are my programming test for E5CN. E5CN_test new.vi MBcrc (2).vi String Hex to Interger Decimal.vi
  7. Hi, Over night something changed on my windows 10 build server and I can now no longer open VIPM. It just shows the splash screen and then closes again. Here's the log file: =========== START of VIPM 2018.0.0 (build 2025) Error Message =========== An internal VIPM 2018.0.0 (build 2025) Error has occured on: Tuesday August 20, 2019 at 03:19:48 PM = Automated Message Start = Error 8 occurred at Open/Create/Replace File in NI_LVConfig.lvlib:Parse Config to Queue.vi->NI_LVConfig.lvlib:Load.vi->NI_LVConfig.lvlib:Open Config Data (compatibility).vi->DDEFA056211BA4DA4D215C322E067D90->621BFCD461979D3C7127139A69154E03->762BBE85A007 171D5A65B48289D23361->46803A2448FAC5F85BFF8F5C199E9C6F->OGPM Class.lvlib:7D7C5CD8C5D361C01081DF5613237E15->OGPM Class.lvlib:D69AB3997B80ACD75689430E3922612C->OGPM Class.lvlib:OGPM Init.vi->VIPM Splash.vi Possible reason(s): LabVIEW: File permission error. You do not have the correct permissions for the file. ========================= DMA hardware error detected. C:\ProgramData\JKI\VIPM\cache\ngene_lib_deepltk_fpga_addon-1.0.0.45.spec = Automated Message End = = User Defined Message Start = Error(s) Generated in Splash Window = User Defined Message End = = Error Handler Call Chain Start = VIPM Splash.vi = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2025) Error Message =========== Any idea where the files are that it doesn't have the right permissions for?
  8. Yesterday
  9. Thanks - I hadn't even thought of using multiple queues in this way, but that makes a lot of sense. I should be able to structure it like this fairly easily.
  10. overcurrent?the function belong to DMM. you can remote the DMM, however, the labview have no the subvi which can monitor overcurrent
  11. The programming term you should look into is Futures and Promises. It is about handling results not yet received (such as defining their order, as you wish to do). Single-element Queues, as TomOrr0W suggests, is what I usually use.
  12. I don't know of any ready-built solutions, but I did come up with the idea below when you mentioned not wanting to reorder (there may be a way to do this with channel wires, but I am not really familiar with that feature) (vi is also attached, saved to LV2018): Parallel Processing Order.vi
  13. Last week
  14. The Parallel For Loop is perfect for parallel processing of an input array, and reassembling the results in the correct order, however this only works if the array is available before the loop starts. There is no equivalent "Parallel While Loop" which might process a data stream - so what is the best architecture for doing this? In my case, I'm streaming image data from a camera via FPGA, acquiring 1MB every ~5ms - call this a "chunk" of data - and I know I will acquire N chunks (N could be 1000 or more). I then want to process (compress) this data before writing to disk. The compression time varies, but is longer than the acquisition time. So I'd like to have a group of tasks which will each take chunks and return the results - however it's no longer guaranteed that the results are in the same order, so there's a bit of housekeeping to handle that. I have a workable architecture using channels, but I'd be interested in any better options. Easiest to explain with a simplified code which mimics the real program: It requires the processing to use a Messenger channel (i.e. Queue) because a Stream channel cannot work in a Parallel For Loop, but this doesn't maintain order. And the reordering is a little messy - perhaps could be tidied using Maps but I don't have 2019 at the moment. The full image is too large to keep in memory (I'm restricted to 32-bit because the acquisition is from an FPGA card), so I need to process and write the data as it becomes available. I've considered writing a separate file for each chunk, but writing millions of small files a day is not particularly efficient or sustainable. Is there a better approach? Have I missed something? I feel like this must be a solved problem, but I haven't come across an equivalent example. Could there be a Parallel Stream Channel which maintains ordering, or a Parallel While Loop which handles a defined number of tasks? Thanks. Greg
  15. Hi, Explanation from NI website: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019KZNSA2&l=en-IL Regards, Joseph.
  16. Hi, I found a solution: when using Labview 32 bit I get the error :-41106 If I open the same .vi with labview 64 bit i don't get the error anymore. it seem to be an error using different format system (32bit and 64bit together). so I renew my question: How can I run vi running with labview 32 bit and Office 64 bit ? Regards, Joseph.
  17. When reading data from excel file with labview 2017 (32bit) I get the error code: Error -41106. Week ago everything worked properly. I uninstall and install Office again. what can I do to make it work again? Regards, Joseph. Windows 10 Home Excel Version: 2016 MSO (16.0.11901.20170) 64bit Labview 2017 32 bit Untitled 1.vi
  18. DVRs can be upcast and downcast with To More Generic and To More Specific. So if you have a public type that is the ancestor of the private one, you can upcast to the public one in public and then downcast when you need to actually use it. That's all completely type safe. (Note: DVR of LabVIEW Object works without you having to create a new ancestor class.)
  19. The instructions in KERNEL_SOURCE.txt are pretty good and work well for me. I use a Ubuntu 18.04 VM for cross-compiling, I would suggest at least 70 GB hard drive space. More help can be found here: https://forums.ni.com/t5/NI-Linux-Real-Time/ct-p/7013 And you can watch this if you'd like:
  20. Why would you want to do that? Compiling a Linux image for embedded hardware is not a trivial feat. Yes NI does provide the scripts that are necessary to do that but you also need to have the perfectly setup development system with the right version of gcc toolchain to even hope to get that working seemlessly. Even slight version differences can mean that you might have to edit scripts and all and such edits are really not for the faint at heart. You need a very deep knowledge into Linux in general and especially embedded kernel compiling of Linux in order to hope that your edits will cause anything else than more errors. Googling with errors is in these cases usually also not a solution because you mostly find only answers from other noobs who have no idea what they are doing and just post random recommendations.
  21. Wow, conditional auto-indexing in loops has been around since Labview 2012? How the heck did I not notice this?
  22. Which kind-hearted person can give you some advice: How to recompile an image that can run on ZYNQ according to the LINUX RT source code on GITHUB? The links are as follows: Https://github.com/ni/nilrt/tree/nilrt/15.0
  23. I wouldn't do this. Its probably ok in this limited case, but its possible to make labview crash in this way. A better route is the variant, which has the same capabilities (cast to an opaque untyped blob and back again) but without the danger.
  24. Even as a pointer, that wouldn't work in C++. Any use of the type in a public signature must be public, even by pointer, even by reference.
  25. I am trying to generate arbitrary pulses from keithley 2614B SMU. I downloaded driver files from keithley website and added to the labview drivers, but the there were multiple VI files and no files to generate pulse pulse voltage and measure current. Do i need to use these driver files to create a new program or shall i can use the same driver file to generate pulse. If any of you are having VI files for pulse generation in 2614B please attach it here.
  26. Hi, You can actually typecast your DVR reference to U32 value (pointer) and back. You can store this U32 number in a helper class, that will represent your API. Or, if you decide to go with a helper API class, then you actually don't need to typecast it to U32 - just store the DVR inside the public API helper class:
  27. Just to say that I have also had the same issue for quite some time. Several months ago I sent a message using the Contact Us link at the bottom of the website, but have not had a response.
  1. Load more activity
×
×
  • Create New...

Important Information

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