Module real time student version

How install the module real time with the Labview student edition?

Hello pierre1,
Do you install from CD or DVD ? If so, to install Real-Time module you just have to select it in the selection menu during the installation procedure.
Regards,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

Similar Messages

LabVIEW Real-Time différente du module Real-Time sur l'ordinateur hôte

Bonjour,
comment est ce possible alors que j'ai installé le NI RIO sur le CRio à partir du même ordinateur ?
Merci pour votre aide.
Ben.
Solved!
Go to Solution.
Attachments:
bugCRIO.png ‏242 KB

Bonjour Ben,
je vous conseille de poser votre question dans la partie francophone du forum, si vous souhaitez obtenir des réponses a votre question
http://forums.ni.com/t5/Discussions-au-sujet-de-NI/bd-p/4171
Cordialement
Kévin

Real time 10.0.1?

Bonjour,
Pour les besoins d'un tp, nous avons fait l'acquisition d'un ensemble cRIO-9074 équipé de 3 module (NI9201, NI9211, NI9401). Aussi avant de le mettre sur paillasse, je tente d'apprivoiser la bête.
Donc j'ai fait à la va vite un VI, me permettant de mesurer une température à l'aide d'un thermocouple.
Au moment d'exécuter ce VI, lors du déploiement sur le fpga, g le message d'erreur suivant : Accès refusé : cette cible exécute une version de LabVIEW Real-Time différente du module Real-Time sur l'ordinateur hôte. Vous pouvez vérifier la version et réinstaller le logiciel Real-Time avec Measurement & Automation Explorer.
Au regard de MAEX, en effet sur la partie logiciel du cRIO, je vois apparaitre Labview Real Time 10.0.1, tandis que sous LV2009SP1, il est mentionné Real-Time 9.0.1.
Est ce qqn peut me confirmer que mon problème trouve bien son origine ds la différence de version? et est que l'on peut m'indiquer si il est possible de mettre à jour mon module RT de Labview 2009?
Cordialement.

Bonjour,
Le problème vient bien de là. Il faut toujours avoir des versions identiques de LabVIEW entre le PC hôte et la cible RT.
Cependant, il ne s'agit pas de faire une mise à jour du module RT sur LabVIEW 2009, car les versions sont assimilées. RT 9.0.1 correspond à LabVIEW 2009 SP1.
Il vous suffit de reconfigurer la cible pour qu'elle corresponde à votre configuration PC.
Pour cela, allez dans MAX, puis cliquez sur votre cible, et sur Logiciels.
faites un clic droit sur Logiciels pour demander à installer des logiciels.
Ensuite, choisissez le package qui vous convient avec la version qui vous convient, et demandez à l'installer
Cordialement,
Olivier L. | Certified LabVIEW Developer

Why can't Real Time Workshop create a model DLL?

When trying to create a model DLL in Real-time Workshop I get the flowing error:
Error using ==> RTW.makertw.make_rtw
Error using ==> tlc_c
Error using ==> tlc_c>InvokeTLC
Error File: C:\SimulationInterfaceToolkit\ModelInterface\basic.tlc Line: 388 Column: 45
Attempt to call a non-function value: SLibGetBlockPath
Installed software : LabView 7.1, Matlab release 14 s1. Real-time Workshop 6.1, and Visual Studio Pro 6.0

This is a new install and I�m only trying to get things setup properly. The MDL file is a simple MDL created to test out SIT. It was taken from the example in the SIT User Guide. I have installed the following software:
Operating System: Microsoft Windows XP Version 5.1 (Build 2600: Service Pack 2)
MATLAB Version 7.0.1.24704 (R14) Service Pack 1
MATLAB Version 7.0.1 (R14SP1)
Simulink Version 6.1 (R14SP1)
Real-Time Workshop Version 6.1 (R14SP1)
Microsoft Visual Studio Pro 6.0
LabView 7.1
LabView Real Time 7.1
Simulation Interface Toolkit 2.0.3
I will include the MDL file. Is there something in the setup I might have missed?
Attachments:
SineWave.mdl ‏17 KB
SineWave.vi ‏265 KB

Real-Time Module Labview 64 bit

I have installed labview 2009 64 bit version to my laptop. And, i want to instal the real-time modul to this labview, but i can not do this since it needs labview 32 bit installed. Is it possible for me to install real-time module to 64 bit labview? Please help me with this problem.

The LabVIEW RT application will most likely always have to remain 32 bit for now. Most of the RT targets are to resource constrained to gain anything from moving them to a 64bit RT OS, in fact in trying to move them to 64 bit they would loose quite a bit of performance. For the Desktop and PXI RT systems, the problem is that they are based on Pharlap ETS and that is a pure 32 bit solution with no plans of ever moving to 64 bit anytime soon, AFAIK. And NI is not likely going to port that to 64 bit themselves, aside from the question if they could technically do so (not sure they have access to all of the source code) and legally (their license most likely does prevent them from changing the ETS software to run under different target systems than the one it was originally purchased for).
The only thing you can expect to come from NI in the near future is that the RT system also installs into 64 bit LabVIEW, and the actual cross compilation that happens already will simply target the 32 bit RT target. That however means that the RT application itself is still limited by the 32 bit constraints. Maybe there are some plans to add a 64 bit RT system to the mix for the high end PXI controller. What OS that would use is quite unclear. Pharlap ETS seems out of question for that, VxWorks is probably not a favorite solution at the moment and an Linux RT based system has its own legal and technical challenges.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Student version pda module?

Hello!
I have got the Labview 8.0 Student Version and I am very happy with it. I think it is a great Programme and I am learning it right now.
I want to create programmes for my mobile phone, which has windows mobile 5.0 installed.
What software do I need to create such programmes. I have found the PDA-module for Labview, but this is very expensive and I can not afford this as a student.
So my question is: Is there a student version of this module available, a demo version or a limited test-version?
Sorry for my bad english, I am from germany.
Thanks for your help!
Greetings, Felix

The LabVIEW 8.0 Student edition software suite includes 5 toolkits and apparently does not include the PDA module.
See: http://www.ni.com/labviewse/select.htm
If I remember correctly, the LabVIEW 7.1 Student edition suite included 12 toolkits and I think the PDA module was one of them. Have a look at the 7.1 Student edition readme: http://www.ni.com/pdf/manuals/374075a.pdf
Maybe it is still for sale somewhere?
LabVIEW Champion . Do more with less code and in less time .

Real Time Module, upgrading Labview 6.02 Base Development System?

Hi,
I have Labview 6.02 Base Development System but I need the Real Time module.
Would it be possible to get it upgrading the Labview 6.02? Is the full development systemm needed?
Which could be the cheapest way to get Real Time module?
Thanks.

You can upgrade to the latest version of LabVIEW Real-Time version 7.1 by upgrading both LabVIEW and LabVIEW Real-Time. You can all about the new features of LabVIEW Real-Time at the following link. For more information, please contact us at .
Regards,
Kristi H
National Instruments
>

CRIO and ni 9234 modules not working or communicating through fpga with accelerometers, fpga connected to real time application which is also connected to shared variables linked to modbus slave

Hi,
I have a compact rio which has a 4 way chassis attached to that chassis is three ni9234 modules they are linked using fpga to a real time application then using shared variables in the low speed loop that are linked to a modbus slave to communicate with dcs, the ni 9234's have accelerometers connected to them with iepe ac coupled option on the c modules, my problem is the real time application seems to be running okay even when power loss occurs it restarts with no problem and the fpga writes to the portable hard drive bin files fine but without a accelerometer connected I get low noise readings as soon as I connect a accelerometer to any one of the 10 outputs it just goes to a fixed number (0.03125) as soon as disconnect it again it reverts back to reading noise, I have run a scan on the modules and only get a spike when I connect or disconnect the accelerometer, I have tested the voltage at the pins of the module and I get 22 volts dc which makes it more likely that the hardware is not the problem but a software is maybe causing this to hang-up, I attach project and files for your perusal. I also carried out a new project which in scan mode directly linked the module input to shared variable and the same scenerio again. Help would be much appretiated.
Many thanks
Jason
Solved!
Go to Solution.
Attachments:
logger 2plusmodbus2.zip ‏679 KB

Whren using waveform acquisition with the 9234s we recommend the following FPGA and RT template.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/209114
it can be extended as a data logger with:
http://zone.ni.com/devzone/cda/epd/p/id/6388
or using shared variables combined with scan engine
http://zone.ni.com/devzone/cda/tut/p/id/9851
The FPGA in all of these, as well as the RT framework have been used successfully by 1000s of users. I would recommend giving these a try.
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

Real-Time Module architecture

Hi, (I use LV RT DSC 8.2.1)
I want to learn how to use the Real-Time Module.
I have process that is running at a Real Time compact Field Point Target.
The process should be controlled and monitored by the Target but the triggering of the process should be available at the Host.
I also want to view the Process progression at the Host screen.
As far as I understand it I have several options :
Create a RT FIFO buffer and send the process data to that buffer, and then, use 'TCP Write' to send the buffer data to the Ethernet Network, where it is available to any Host PC at the Ethernet Network to view (by using TCP Read)
Create a Variable in the Project, and enable his RT FIFO at his properties.
Control the process at the Target with Shared Variables and read them at the Host.
Option 3 is the option I have been using so far, ignoring the RT property of the controllers, what are the advantages of using RT module ?
and when should I consider using them ?
What is the difference between 1 and 2 and what are their advantages ?
What important things do I need to consider when I use RT Module (just several tips if possible) ?
Sincerely Yours, Amitai Abramson.

Hi Amitai,
You could go through this link to know more about RT FIFO and its use. http://zone.ni.com/devzone/cda/tut/p/id/3934
and this for communication wizard http://zone.ni.com/devzone/cda/tut/p/id/4676
Message Edited by mallyaprs on 04-30-2009 03:53 AM
-Mallya
" Appreciate and motivate those who help"

Error -1074384569; NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your database to the real-time system.

Hello
I have a VeriStand-Project (VSP) created with my Laptop-Host (LTH) which works with my PXI, while
deploying it from my LTH. Then I have installed the whole NI enviroment for PXI and VeriStand use on a
industrial PC (iPC). I have tried to deploy my VSP from the iPC to the PXI but the following error
message arose on my iPC:
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details: Error -1074384569 occurred at Project Window.lvlibroject Window.vi >> Project
Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
Possible reason(s):
NI-XNET: (Hex 0xBFF63147) The database information on the real-time system has been created with an
older NI-XNET version. This version is no longer supported. To correct this error, re-deploy your
database to the real-time system. ========================= NI VeriStand: NI VeriStand
Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI
VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> NI VeriStand Engine.lvlib:Initialize
Inline Custom Devices.vi >> Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * • Unloading System
Definition file... • Connection with target Controller has been lost.
The software versions of the NI products (MAX/My System/Software) between my LTH and the iPC are
almost the same. The only differences are:
1. LabView Run-Time 2009 SP1 (64-bit); is installed on LTH but missing on iPC. The iPC has a 32-bit system.
2. LabView Run-Time 2012 f3; is installed on LTH but missing on iPC.
3. NI-DAQmx ADE Support 9.3.5; something strage on the LTH, because normally I am using NI-DAQmx 9.5.5 and all other DAQmx products on my LTH are 9.5.5. That means NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5.. On the iPC side all three products are 9.5.5.. That means NI-DAQmx ADE Support 9.5.5, NI-DAQmx Device Driver 9.5.5 and NI-DAQmx Configuration 9.5.5..
4. Traditional NI-DAQ 7.4.4; The iPC has this SW installed. On the LTH this SW is missing.
In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
1. LabVIEW Real-Time 11.0.1
2. NI-488.2 RT 3.0.0
3. NI_CAN 2.7.3
Unfortunately the above stated problem still arose.
What can I do to fix this problem?
I found a hint on http://www.labviewforum.de/Thread-XNET-CAN-die-ersten-Gehversuche.
There it is written to deploy the dbc file againt.
If this is a good hint, so how do I deploy a dbc file?
I would feel very pleased if somebody could help me! :-)
Best regards
Lukas Nowak

Hi Lukas,
I think the problem is caused by differenet drivers for the CAN communication.
NI provides two driver for CAN: NI-CAN and NI-XNET.
NI-CAN is the outdated driver which is not longer used by new hardware. NI replaced the NI-CAN driver with NI-XNET some years ago, which supports CAN, LIN and the FLEXRAY communication protocol.
You wrote:
In order to fix this problem I have formatted my PXI and I have installed the following SW from the iPC:
3. NI_CAN 2.7.3
NI CAN is the outdated driver. I think that you should try to install NI-XNET instead of NI-CAN on your PXI-System, to get rid of the error message.
Regards, stephan

Real time database, Logger, ICM version 8

Dear;
Currently I am checking the table t_Agent_Real_Time and the values are zeros, so I beleive that maybe the writing to the real time database is disabled. In ICM version 8, where I can enable or disable the writing to real time database at the logger from the Registry (because I forgot this)?
Regards
Bilal

Dears;
It is resolved.
I just corrected the hostname for the HDS server that I have to place it in the Distributor settings at the CUCM PG in the Configuration Manager. It was keep having the old hostname that came from the migration tool.
Thanks
Regards
Bilal

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c

Hi,
Good day!
I'm having this issue when I just installed an application. I have been searching this kernelbase.dll thing but none of them have fix or any workaround. Hopefully with the great technical guys here can help me with this issue.
The server is windows 2008 R2
From the event viewer I got this
Faulting application name: Tlc.LogManager.Svc.exe, version: 7.0.1.5108, time stamp: 0x51d1ee27
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xe0434352
Fault offset: 0x000000000000cacd
Faulting process id: 0x1130
Faulting application start time: 0x01cf6dbd862da5b1
Faulting application path: D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f
Application: Tlc.LogManager.Svc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException
Stack:
   at Tlc.CapCollector.Common.CapPersistentStateManager..ctor(Tlc.Interfaces.BusinessObjects.IAssetBusinessObject, Tlc.PersistentState.IPersistentStateStore, Tlc.Interfaces.ApplicationLog.IApplicationLog, Int32, Tlc.CapCollector.AgentDiscovery.CapAgentAutoDiscovery)
   at Tlc.LogManager.Lib.ascMan.OnMessageBusStart(Tlc.Interfaces.MessageBus.IMessageBus, Tlc.Interfaces.ApplicationLog.IApplicationLog, Tlc.Interfaces.ApplicationLog.IApplicationLog, Tlc.Interfaces.ApplicationLog.IApplicationLog)
   at Tlc.MessageBus.ActiveMQMessageBus.Start()
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: tlc.logmanager.svc.exe
P2: 7.0.1.5108
P3: 51d1ee27
P4: Tlc.CapCollector
P5: 7.0.1.5108
P6: 51d1edf4
P7: f2
P8: 34
P9: System.ArgumentNullException
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_tlc.logmanager.s_4d5cd055f698b9b7d9e989629dd2eb52d0be2b_1a6a145b
Analysis symbol:
Rechecking for solution: 0
Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f
Version=1
EventType=CLR20r3
EventTime=130443543988233973
ReportType=2
Consent=1
ReportIdentifier=8c35a7c6-d9a9-11e3-9578-5ef3fcdc0b9f
IntegratorReportIdentifier=8c35a7c5-d9a9-11e3-9578-5ef3fcdc0b9f
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=tlc.logmanager.svc.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=7.0.1.5108
Sig[2].Name=Problem Signature 03
Sig[2].Value=51d1ee27
Sig[3].Name=Problem Signature 04
Sig[3].Value=Tlc.CapCollector
Sig[4].Name=Problem Signature 05
Sig[4].Value=7.0.1.5108
Sig[5].Name=Problem Signature 06
Sig[5].Value=51d1edf4
Sig[6].Name=Problem Signature 07
Sig[6].Value=f2
Sig[7].Name=Problem Signature 08
Sig[7].Value=34
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.ArgumentNullException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=18441
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=3ada
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=3adac3ca3b54f3f7659e16fb4fdadcbe
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=b033
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=b0336032f99007ec98baa22debc5fb25
UI[2]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
UI[3]=Tlc.LogManager.Svc has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Tlc.LogManager.Svc stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[10]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\system32\GDI32.dll
LoadedModule[12]=C:\Windows\system32\USER32.dll
LoadedModule[13]=C:\Windows\system32\LPK.dll
LoadedModule[14]=C:\Windows\system32\USP10.dll
LoadedModule[15]=C:\Windows\system32\IMM32.DLL
LoadedModule[16]=C:\Windows\system32\MSCTF.dll
LoadedModule[17]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[18]=C:\Windows\system32\MSVCR100_CLR0400.dll
LoadedModule[19]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\bc19222db4406c472d9aa1f8b6e0f470\mscorlib.ni.dll
LoadedModule[20]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
LoadedModule[21]=C:\Windows\system32\ole32.dll
LoadedModule[22]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[23]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[24]=C:\Windows\system32\rsaenh.dll
LoadedModule[25]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\0f8f78b729ce16dd078f5d5f734a1110\System.ni.dll
LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceProce#\7b167f31f23d4aed19dfa65ad3d29480\System.ServiceProcess.ni.dll
LoadedModule[27]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[28]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[29]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Zip.v5.1.dll
LoadedModule[30]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.GZip.v5.1.dll
LoadedModule[31]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Tar.v5.1.dll
LoadedModule[32]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Compression.Formats.v5.1.dll
LoadedModule[33]=C:\Windows\system32\VERSION.dll
LoadedModule[34]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Common.dll
LoadedModule[35]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.FileSystem.v5.1.dll
LoadedModule[36]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Xceed.Compression.v5.1.dll
LoadedModule[37]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Lib.dll
LoadedModule[38]=C:\Windows\assembly\GAC_MSIL\VistaDB.4\4.1.0.0__dfc935afe2125461\VistaDB.4.dll
LoadedModule[39]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Interfaces.dll
LoadedModule[40]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Enums.dll
LoadedModule[41]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\7a93c267da35a5f16b6fa5a10482eb4e\System.Core.ni.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data\5a47dfd0b200a502a4d5d27ee99bcc3c\System.Data.ni.dll
LoadedModule[43]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[44]=C:\Windows\system32\WS2_32.dll
LoadedModule[45]=C:\Windows\system32\NSI.dll
LoadedModule[46]=C:\Windows\system32\CRYPT32.dll
LoadedModule[47]=C:\Windows\system32\MSASN1.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\5d9f385419332f14eaf937556199856f\System.Xml.ni.dll
LoadedModule[49]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dal.LogManager.Client.dll
LoadedModule[50]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Service#\5ac492f703d6d741140f7cd45ef3c746\System.Data.Services.Client.ni.dll
LoadedModule[51]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dal.LogManager.Local.dll
LoadedModule[52]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Entity\c41b30de7215a62c8ca5bfe6e04ea763\System.Data.Entity.ni.dll
LoadedModule[53]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.DataAccess.Config.dll
LoadedModule[54]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Log.dll
LoadedModule[55]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Utils.dll
LoadedModule[56]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogMessageClassifier.dll
LoadedModule[57]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Wintellect.PowerCollections.dll
LoadedModule[58]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorks.dll
LoadedModule[59]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\11581b5eba4b3ff58441c638ab66c742\System.Configuration.ni.dll
LoadedModule[60]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Web\7e5af1fdbcffeab8daffc7633f9c337a\System.Web.ni.dll
LoadedModule[61]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1266d26c7b7843d308e2705cb8239d55\System.Drawing.ni.dll
LoadedModule[62]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\f0acb5c0e7dc2c42c6c61f3aa1278338\System.Windows.Forms.ni.dll
LoadedModule[63]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CommonAssemblyInfo.dll
LoadedModule[64]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_2b24536c71ed437a\gdiplus.dll
LoadedModule[65]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[66]=C:\Windows\system32\shell32.dll
LoadedModule[67]=C:\Windows\system32\profapi.dll
LoadedModule[68]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll
LoadedModule[69]=C:\Windows\system32\USERENV.dll
LoadedModule[70]=C:\Windows\system32\PSAPI.DLL
LoadedModule[71]=C:\Windows\system32\urlmon.dll
LoadedModule[72]=C:\Windows\system32\WININET.dll
LoadedModule[73]=C:\Windows\system32\iertutil.dll
LoadedModule[74]=C:\Windows\system32\SspiCli.dll
LoadedModule[75]=C:\Windows\system32\shfolder.dll
LoadedModule[76]=C:\Windows\system32\bcrypt.dll
LoadedModule[77]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuratio#\c080a9ed31f78466f2400bba623af2f8\System.Configuration.Install.ni.dll
LoadedModule[78]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Web.Services\6cd002594b56953e9c210581e7f3f3cd\System.Web.Services.ni.dll
LoadedModule[79]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.PersistentState.dll
LoadedModule[80]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Mitre.CommonEventExpression.dll
LoadedModule[81]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.ClientServer.Communications.dll
LoadedModule[82]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Numerics\215d813343ba0950ad6e148e2098018b\System.Numerics.ni.dll
LoadedModule[83]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Management\da51604aa808b94c181181b37c727078\System.Management.ni.dll
LoadedModule[84]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.VisualBas#\af08f116e2c31d2c65bd492804fb2fef\Microsoft.VisualBasic.ni.dll
LoadedModule[85]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[86]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll
LoadedModule[87]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[88]=C:\Windows\system32\wbem\wmiutils.dll
LoadedModule[89]=C:\Windows\system32\wbemcomn.dll
LoadedModule[90]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[91]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[92]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[93]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[94]=C:\Windows\system32\mswsock.dll
LoadedModule[95]=C:\Windows\System32\wshtcpip.dll
LoadedModule[96]=C:\Windows\System32\wship6.dll
LoadedModule[97]=C:\Windows\system32\DNSAPI.dll
LoadedModule[98]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[99]=C:\Windows\system32\WINNSI.DLL
LoadedModule[100]=C:\Windows\system32\rasadhlp.dll
LoadedModule[101]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[102]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Devart.Data.MySql.dll
LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Transactions\122cea70c5d0d591f9af1f4316848fd1\System.Transactions.ni.dll
LoadedModule[104]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
LoadedModule[105]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Devart.Data.dll
LoadedModule[106]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSL.dll
LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.OracleC#\850abdea1c65b88ba24a77f0191caea8\System.Data.OracleClient.ni.dll
LoadedModule[108]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data.OracleClient\v4.0_4.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll
LoadedModule[109]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml.Linq\9d14b7bc969452800c0456286309d41d\System.Xml.Linq.ni.dll
LoadedModule[110]=C:\Windows\assembly\GAC_MSIL\VistaDB.Entities.4\4.1.0.0__dfc935afe2125461\VistaDB.Entities.4.dll
LoadedModule[111]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.EnterpriseSe#\48264d6ad04173a3a82cc06b70c5cd28\System.EnterpriseServices.ni.dll
LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.EnterpriseSe#\48264d6ad04173a3a82cc06b70c5cd28\System.EnterpriseServices.Wrapper.dll
LoadedModule[113]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
LoadedModule[114]=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.Entity\v4.0_4.0.0.0__b77a5c561934e089\System.Data.Entity.dll
LoadedModule[115]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime.Seri#\08fba6b56d838ad48b4451c82e5728d4\System.Runtime.Serialization.ni.dll
LoadedModule[116]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.RuleEngine.dll
LoadedModule[117]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.EventForwarder.dll
LoadedModule[118]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Lucene.Net.dll
LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel\d072039db89cac96d9e0b1ae9b3a94f4\System.ServiceModel.ni.dll
LoadedModule[120]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel#\43f892698b9de4d752c13cc2d91ff16d\System.ServiceModel.Web.ni.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_64\SMDiagnostics\ac74a156499a8303d5788ab299881d5d\SMDiagnostics.ni.dll
LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runtime.Dura#\2f02efd9ddb7417ffd5c06cfe6e865ca\System.Runtime.DurableInstancing.ni.dll
LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.IdentityModel\33ac21194152cf9a89b82d9cd38b398d\System.IdentityModel.ni.dll
LoadedModule[124]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\535e182d16212c61bc8b22e0309d3362\System.Xaml.ni.dll
LoadedModule[125]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data.Services\84226b67f4623bd3b0dde9aa00c5c88d\System.Data.Services.ni.dll
LoadedModule[126]=C:\Windows\system32\pcwum.DLL
LoadedModule[127]=C:\Windows\system32\httpapi.dll
LoadedModule[128]=C:\Windows\system32\cryptnet.dll
LoadedModule[129]=C:\Windows\system32\WLDAP32.dll
LoadedModule[130]=C:\Windows\system32\SensApi.dll
LoadedModule[131]=C:\Windows\system32\dsrole.dll
LoadedModule[132]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.MessageBus.dll
LoadedModule[133]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Apache.NMS.dll
LoadedModule[134]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Google.ProtocolBuffers.dll
LoadedModule[135]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSH.dll
LoadedModule[136]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Reports.dll
LoadedModule[137]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\SecureBlackbox.dll
LoadedModule[138]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.GenericDbLogCollector.dll
LoadedModule[139]=C:\Windows\system32\ntmarta.dll
LoadedModule[140]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\perfcounter.dll
LoadedModule[141]=C:\Windows\system32\pdh.dll
LoadedModule[142]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.System.dll
LoadedModule[143]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
LoadedModule[144]=C:\Windows\system32\aspnet_counters.dll
LoadedModule[145]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_perf.dll
LoadedModule[146]=C:\Windows\system32\Secur32.dll
LoadedModule[147]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[148]=C:\Windows\system32\security.dll
LoadedModule[149]=C:\Windows\system32\credssp.dll
LoadedModule[150]=C:\Windows\system32\schannel.DLL
LoadedModule[151]=C:\Windows\system32\ncrypt.dll
LoadedModule[152]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[153]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\nsoftware.IPWorksSSNMP.dll
LoadedModule[154]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Apache.NMS.ActiveMQ.dll
LoadedModule[155]=C:\Windows\system32\NLAapi.dll
LoadedModule[156]=C:\Windows\system32\napinsp.dll
LoadedModule[157]=C:\Windows\System32\winrnr.dll
LoadedModule[158]=C:\Windows\system32\rasman.dll
LoadedModule[159]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CapCollector.dll
LoadedModule[160]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.CapIDL.dll
LoadedModule[161]=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.Dto.dll
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Tlc.LogManager.Svc
AppPath=D:\Program Files (x86)\Tripwire\Tripwire Log Center Manager\Tlc.LogManager.Svc.exe

Hi Ross Rene,
Sorry for the delay.
Please make sure the App is compatible with the .Net framework installed, please check the .net version.
Best Regards,
Anna

What are the limitations of using labview 8.5.1 developers suite verses a real-time module in field point applications?

What are the limitations of using labview 8.5.1 developers suite verses a real-time module in field point applications? Can an exe. be loaded onto a field point controller or does the controlling program have to reside on a PC for example?

centerbolt is correct, you can't load a .exe or even run a program on the fieldPoint controller unless you have the Real Time module. However, that does not mean you can't use your FieldPoint bank without the Real Time module.
From LabVIEW for windows you can make calls to the fieldpoint IO using the fieldpoint read/write functions.
This program runs on the PC not the FieldPoint controller. If you loose network connection to the fieldpoint, your program will loose connection to the IO. For many data logging applications this type of arrangement can work just fine. However, if this is the only type of application you are ever going to run, then you may as well not buy the Real Time controller for your fieldpoint but the network controller only.
If your application requires more reliability, and/or greater determinism than can be achieved by running a program on windows, then you should use the LabVIEW Real Time module and develop a program that can run down on the FieldPoint controller independent of windows.
Message Edited by StevenA on 07-22-2008 04:14 PM
SteveA
CLD
FPGA/RT/PDA/TP/DSC
Attachments:
fp pallet.PNG ‏6 KB

How to create function module in real time

hi experts,
can somebody explain a real time requiremwnt , to create a function module.
its very urgent.
i want elaborately.
regards,
subhasis.

hi,
In real time
1. as per my knowledge we create function modules to Inbound IDOC /outbound processing..
2.Interface between a program..
Example we need to take some data from a report say materials and plant and process some bapi and return logfiles to the report we can use FM here too.
To create a function module
First you need to create a function group (function group holds a number of function modules relevant)
SE37>goto>function groups-->create group ..click this create group..
Now in the pop up enter the function groupname Eg: ZW_FG1 plus short text and saveit
Now again goto SE37--> enter new Function module name eg:ZW_FM1
and press F5.
Now again a popup you need to enter
function group name : ZW_FG1
and short test and save it..
Now the Function module is created under the Function group ZW_FG1.
write your export import table parameters and you source code.
rewards if useful
regards,
nazeer
Message was edited by:
nazeer shaik

Need SAP-HR Module wise Blue prints and Real time questions

Hi HR Team,
can u send me the OM issues and real time questions and any HR module Questions and Blue prints .pls if useful awarded points
my mail id is [email protected]

Hi HR Team,
can u send me the OM issues and real time questions and any HR module Questions and Blue prints .pls if useful awarded points
my mail id is [email protected]

Module real time student version

Similar Messages

Maybe you are looking for