
Bobillier
Members-
Posts
216 -
Joined
-
Last visited
-
Days Won
5
Bobillier last won the day on January 28 2014
Bobillier had the most liked content!
Profile Information
-
Gender
Male
-
Location
Rennes France
LabVIEW Information
-
Version
LabVIEW 2018
-
Since
2009
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
Bobillier's Achievements
-
Like I said before, it's not possible because In TIA struct (Like array) is a decorative declaration. It's just to facilitate the visualisation of a group of few data types in a same entity in TIA. But there is no sens of that in PLC, where struct datas are stored sequentially without adding information about the struct itself. And like with S7 communication you can only accedd to memory, you can only acceed to few bytes list and define from this adress to this adress it's one int or one real. no information about struct it's self in memory. You need to collect each data type and recreate struct after like in my image.
- 8 replies
-
- tia portal
- labview
-
(and 1 more)
Tagged with:
-
you can't , I think, directly access the whole structure all at once. You must access each of its elements individually and rebuild your structure. Don't forget that your DB containing your structure must not have optimized memory access (see DB attributes). Like this each element will have an address to be accessed.
- 8 replies
-
- tia portal
- labview
-
(and 1 more)
Tagged with:
-
LabVIEW .NET interop assembly target framework
Bobillier replied to pawhan11's topic in LabVIEW General
Hi pawhan11 Few days ago I have experiment one similar problem about exe and a .NET compoment (look here). I have solved it by adding a small file before my exe to indicate what assembly runtime version using. I'm not sure than you can use similar thing to solve your problem (LV11 refer natively to .NET 3.5), but perhaspse that can run. I have see something about that here Step 1: create a texte file named Labview.exe.config Step2: Place the text below in it <?xml version ="1.0"?> <configuration> <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.8"/> </startup> </configuration> Take care about supportedRuntime version number because it must be corresponding to your .NET constructor. Step3 : Save this file in same directory than your Labview version, and restart LabVIEW Step4 : Rebuild your assembly. -
To be more efficient with the workaround, follow this procedure: 1) Copy the file "Your Application Name.exe.config" and Post-build Action.vi in your project folder. 2) Rename "Your Application Name.exe.config" with the good name of your application 3) Add it to your project. 4) In executable construction windows, add "Your Application Name.exe.config" to the source files\ always include list 5) In executable construction windows, select Post-build Action.vi in "Pre and Post build Action 6) Run construction. The post build vi is just to move "Your Application Name.exe.config" from data folder to those parent application folders automatically. Without it let it to data folder and you need to move it manually Post-Build Action.vi Your Application Name.exe.config
-
On my machine I have V1.0, V1.1, V2.0, V3.0, V3.5 and V4.0.30319 installed. But If LV 2011 use 3.5,why I have the Labview tool to identify "Assembly .NET in memory" who refer to V4.0 ? Wonderful It's exactly the problem origine. Like said ShaunR if LV2011 needs 3.5, and if IDE refers to 4.0, I will need to add the Application.exe.config file in the application folder to force exe to use 4.0. Thanks to all
-
Hi Rolf It's first time I use .NET and I'm newbee about those technology . At start I just want send email through SMTP TLS in old application LV2011. Like secure SMTP is not present in LV2011, I have found one example who use them with .NET Like I said before this example run OK (with my own account (not ggogle)), but just in my LV IDE. I 'm not sure to understand what is signification of "strongly named" but when I use the Labview tool to identify "Assembly .NET in memory" I obtain this link: I think it's in GAC but i'm not sure and If it's the case , like you said "Something is wrong" , but what ?
-
Hi I have created one program who call a DotNet assembly component (.NET4 system.dll) and all ok in my LV2011 development ide. But when I create EXE with it, each time I run the program it calls me .Net ddl path. I do that on the same PC. If I indicate the path, the program loads it and runs correctly. It's a bit painful and not very professional to do that each time. To solve this, I have tried lots of work around but without success. 1) Add Dll caller Vi directly in project folder . (intialy in my user folder) 2) Add a specific .ini file where I have added a key for the search path (viSearchPath= "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089") to Help LV to found assembly. 3) Add DLL in my exe construction in data folder 4) etc etc... I have read and test lots of things on NI website but it's not always clear for me. If someone can give me a good procedure it will be christmas for me. Eric
-
Thanks Antoine I have tested your version, but it seems that it did not work if you have more levels of stacked case structures. I think it's because you don't use "Traverse for GObject.vi " like me. My approach is to select tunnels before applying the change and not the case structure itself. Here my new version with few corrections about your first remarks Set Tunnels Default Values.vi
-
Thanks Antoine I have not enough test it before propose it. Sorry I working on to correct bug when i receive your last message and modified version. Unfortunely, i can't test it because it's in LV2019 and I only have LV2018. Is there possible to have it in LV2018 ? Thanks
-
Oups minor correction to avoid debug windows when loaded. Set Tunnels Default Values.vi
-
Here the QD Instalation: Save it in quick drop plugins folder Usage: Select few unwired tunnels in one or few stached case structure and run the QD Short-cut [U] (can be modify in the vi documentation texte) LV2018 Set Tunnels Default Values.vi
-
Yes, It's exactly what I'm looking for. Thanks Now I will try to do QD to automatically do this with few tunnels in few stacked case structures.
-
Hi Do you know if there is a way to switch unwired tunnels to their default values by scripting?
-
Kill lonely clones vi without close Project windows
Bobillier replied to Bobillier's topic in Development Environment (IDE)
Thanks for this idea. Unfortunately this type of mechanism does not exist natively in the DQMH framework. A future evolution perhaps? I will suggest it on the DQMH forum. Either way, it would be nice if the LabVIEW IDE offered it natively without needing to code it in programs. It's like for the vi which have Modal windows and which we forget to close before launching their proprietary program and which blocks the front panel and prevents us from all actions. Also a small keyboard shortcut in the IDE would be useful. -
Kill lonely clones vi without close Project windows
Bobillier replied to Bobillier's topic in Development Environment (IDE)
Ok I will make test with Task Manager, but like it's similar tool, I think than I obtein same result.