Crash with labview DSC

LabVIEW 7.1
LabVIEW DSC 7.1
Citadel 5
Hi,
I've developed an application with Labview 7.1... I'm using a customer/server structure.
I'm using a fieldPoint to acquire analog values trough labview DSC.
When only the server runs, i've no problem. I can read and display all the tags i want in historical graphs.
On the Computer "customer", I imported network tags through the "Tag Configuration Editor".
Sometimes, when i want to read historical datas, Windows (XPSP2) kills my application on the customer. (I'm using the VI "read traces" ).
I saw errors in the "windows events viewer" : wrong execution of nicitmid.dll
I don't know how to solve this problem. Any help ?
(sorry for my poor english )
regards,
Alexis de La Fontaine

Bonjour,
Je constate que vous êtes de NI france donc je me permet de m'exprimer dans ma langue...
Oui, cette dll est installée avec Labview DSC.
Ce que j'ai pu constater :
J'ai un PC serveur qui tourne et qui centralise toutes les données reçues d'un fieldpoint. Ces données sont stockées dans la base de données gérée par citadel. Lorsque je demande des courbes d'historique de mes voies de mesures depuis le PC serveur, je n'ai aucun problème (j'utilise les Vis NI pour obtenir ces historiques).
Par contre j'ai un deuxième logiciel utilisé en tant que client sur des postes distants. Lorsque je fais des demandes d'historiques de données.... le client va chercher ces données sur le poste serveur... Dans la très grande majorité des cas, celà fonctionne très bien ! par contre, dans certains cas (aléatoires à mon sens), l'application cliente OU maitre plante avec une erreur windows. C'est alors que la dll nicitmid.dll est mise en cause par windows.
D'après moi, cette erreur est peut-être dûe au fait de demander simultanement des courbes d'historique à la fois depuis un poste client et depuis le poste maitre....
Avez-vous des idées, des suggestions ?
Cordialement,
Alexis de La Fontaine
ASSYSTEM FRANCE.

Similar Messages

Cp5611 card with Labview DSC

I want to use Labview 7 DSC with OPC servers and CP5611 card for communicating with Siemens AC drive. Do I need any other software or hardware for communicating on profibus DP?

You need to purchase the SIMATIC NET OPC server in order to communicate with your profibus based devices via a CP5611.
Please ask Siemens about order information and pricing.
Regards,
Jochen Klier
Applications Engineering Group Leader
National Instruments Germany GmbH

PC Crash with Labview 7 and windows 2000

Problem:
the PC does reboot without any prompt when a LV 7 vi is running; the reboot seems to occur randomly (no time dependent); sometimes instead of rebooting, the PC switches to the blue screen with the following message:
Stop: 0x0000001E (0xC0000002, 0x80419292, 0x00000000, 0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
Xxx Address 80419292 base at 80400000, date stamp 3EE6C002-ntoskrnl.exe
Starting memory download
Configuration:
Intel Pentium IV - 2.66 GHz - RAM 1 Gbyte - Video chipset Intel 82865G;
OS: Windows 2000
DAQ Board: PCI MIO 16 E1;
Labview 7 express - NIDAQ 7.1
Note:
The VI that causes the reboot uses the DAQMX to generate an Analog Output with analog trigger.

> The VI that causes the reboot uses the DAQMX to generate an Analog
> Output with analog trigger.
You probably want to post this problem to the DAQ message board as well
since LV itself really can't cause either of these problems on a
protected OS. Be sure to be very explicit about what HW boards and what
DaqMX calls you are making along with which version of the driver you have.
Greg McKaskle

LabVIEW DSC 8.0 examples that deal with events check for valid timestamp.Why?

Hi folks !
There are examples that come with LabVIEW DSC 8.0 that deal with alarm events, In these examples - DSC Alarms Event Structure Support.vi contained in DSC Alarms Demo.lvproj, for instance - when an alarm event occurs, the code checks for a valid time stamp - 17:00:00.000 31/12/1975. I´m confused, can anyone help me understanding why it´s done?
Thanks !

Hello marc8470,
Each Virtex 5 FPGA bank requires an external voltage reference. The FlexRIO FPGA module provides this reference in the form of Vccoa and Vccob. Because there are two voltage references available on the FlexRIO FPGA module, each Vcco reference is connected to 2 IO banks. The Adapter Module Interface and Protocol chapter of the FlexRIO MDK manual has a table that indicates which GPIO banks are referenced to which Vcco reference. The Vcco levels set in the general section of the adapter module configuration file are not used by the Xilinx compiler, but instead by the fixed FlexRIO logic to configure the external voltage references. The IO standard constraints section of the adapter module configuration file is used during compile to configure the output drivers in the Virtex 5. If the general VccoALevel and VccoBLevel values do not match the IO standard constraints, no error will occur during compile, but the hardware will not be configured correctly during runtime. The logic families used by each general purpose IO (GPIO) line must match that of the Vcco levels set in the general section of the adapter module configuration file. A mismatch in values could result to incorrect behavior or possible damage to the FlexRIO FPGA module or the adapter module.
In the future, please use the email address included in your NI FlexRIO Adapter Module Development Kit (MDK) User Manual to send your questions directly to the FlexRIO MDK support team. This group has experience with specific FlexRIO MDK questions such as this one.
The FlexRIO MDK manual is designed to provide all of the information a hardware designer will need to create a FlexRIO adapter module. National Instruments is always improving and working on new releases of the FlexRIO MDK. Please feel free to use the support email address in the FlexRIO MDK manual to send me any feedback you have on the contents of the manual.
Regards,
Browning G
FlexRIO R&D

LabVIEW DSC: Migration from 6.1 to 8.6 problems

Colleagues,
I need help from someone who experienced with LabVIEW DSC. I would like to recompile pretty old application written in LabVIEW 6.1/DSC 6.1 to LabVIEW 8.6, and got lot of troubles with this.
At the first I have tried to migrate my old scf file as described here: "Migrating from LabVIEW DSC 7.1 to 8.0".
Well, it seems to be OK, and LabVIEW.lvlib library with variables was created, but when I tried to double click on the some items, then exception occurred in LabVIEW (see dsc_exception.png in attachment).
Can you please open test project (attached to this post) and double-click on the Slave005_A0 Item? Is crash happened only by me or by someone else?
The second problem with understanding.
In LabVIEW DSC 6.1 I have used "Read Tag.vi" / "Write Tag.vi" vis for accessing the items. When my VI opened in LabVIEW/DSC 8.6, then these calls replaced with "legacy_Write_Tag_(analog)7x.vi" (see screenshot). I'm unable to found according VIs in DSC 8.6. How can I write/read my tags in the latest version? As far as I can understand, I can use Shared Variables directly. Is this correct? But then how can I read multiple tags? Through DataSocket VIs?
The same with "legacy_Get_Tag_List7x.vi". How can I get items list in DSC 8.6 programmatically?
Or should I leave all legacy* vis in my application?
thanks in advance and best regards,
Andrey.
Attachments:
dsc_exception.png ‏26 KB
dsc_legacy_Write_Tag.png ‏3 KB
TestProject.zip ‏4 KB

Hi Andrey,
Yes, my LabVIEW crashes as well. As you may have noticed, a lot has changed in LabVIEW 8.0 with regards to DSC, the most important being that tags are replaced with Shared Variables. I would recommend that you go through each variable and create them by yourself to ensure the most reliable performance.
If you are interested in reading 'tags', then you just need to drag the Shared Variable and place it on the block diagram (that's the direct way). If you are interested in doing this programatically, then have a look at the DSC Module -> Engine Control -> Variables & I/O Servers -> Get Shared Variable List palette on the block diagram. You can then use DataSocket to access the Shared Variables.
Don't leave the legacy VIs on your block diagram. Upgrade your whole project; shared variables are here to stay. Have a look at the following article to get a thorough understanding of them:
Using the LabVIEW Shared Variable
Let us know if you have more questions.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Interfacing PLC siemens S7_300 and LabVIEW DSC using siemens OPC server

Does anyone already interface Siemens PLC S7_315-2-DP with LabVIEW DSC using Siemens OPC server?
Is that a good solution? Are there any hidden problems?

The use of an OPC Server is the way to go when dealing with LV. If you already have Siemens OPC Server then use that. Otherwise, NI has a product called IA Severs/Lookout Protocol Drivers (LPD), which has a large selection of drivers for PLC's. After configuring the driver, LPD is the OPC Server for the device.

Labview DSC 8.6

Hi,
i am a new with Labview DSC 8.6, i have an application similar like SCADA development. want to read and store for 300 nos of channels over NI OPC server. but similar application i have done with out using DSC module by using Data socket with OPC server and same data i stored in SQL Data base using database tool kit.
could you send me the user manual for the DSC8.6?
also explain me how we can use to develope the application in best way.
1. The channels are to be configured as programatically
2. data logging with sql data base has to be done by programatically
3. allarms should be logged.
Regards,
Balaji DP

Thanks for the reply.
I figured that they may be different enough not to be compatible with each other, but I was hoping that they could coexist on the same computer, at least the tag monitors on my development computer that doesn't actually run the machines.
Do I have to remove 8.6 DSC to have 7.1 DSC tag monitor work again? 7.1 DSC tag configuration still works. I haven't actually tried to launch the 7.1 DSC engine. I have the 7.1 DSC CDs so I tried to repair it after renaming the shared Tag Monitor directory (so it would reinstall it) but although it installed the DSC 7.1 tag monitor, it didn't work, so there's something else. It didn't reinstall the Citadel database or Logos because it detected higher versions of them.
As far as upgrading the machine computers to 8.x, we will be doing that eventually but its going to take some time so I was hoping to still have a way of monitoring the tags.

Using Modbus TCP I/O Server with new DSC Shared Variables in LabVIEW 8.6

Hello,
I'm using LabVIEW 8.6 and want to communicate with a Beckhoff BK9000 Ethernet TCP/IP Bus Coupler via Modbus TCP. Instead of using the NI Modbus Library, I've tried the new LabVIEW 8.6 feature "DSC Shared Variables" as described at the bottom of this page: Latest NI LabVIEW DSC Module Features and Demos. Reading of analog input bus terminals works fine. However, I haven't figured out yet how to write on an anolog output bus terminal with these shared variables.
It's about a 16 bit analog output and I need to write to the registers 0x1121 and 0x0801. It works with the NI Modbus Library (just using function code 6 and choosing the registers), but on the other hand I don't know which shared variables I have to choose for these registers. I've tried several data items (e.g. 400001 upwards as well as 402049 for 0x0801) but none of them worked. I would be glad for a short explanation - thanks in advance for your support!
Regards
utechle

The Beckhoff documentation says, that holding registers start with 0x0800. I've checked this by using the NI Modbus Library. I used the "MB Ethernet Master Query.vi" togehter with the function code 6 for "Write Single Registers", changed the settings of the starting address to hexadecimal view and entered 801 (since it starts with a control byte in 0x0800 and the data out word follows in 0x0801). Furthermore, I had to address register 0x1121 in the same way for resetting the watchdog. As I've mentioned in my first post, this method works fine. However, I haven't found out yet which shared variables i have to use for accessing these registers.
On the other hand, it's no problem to read data from analog input bus terminals using shared variables. They start with 0x0000 (status byte) and 0x0001 (data in word) and I can read data with the shared variable and data item 300001, respectively.
Message Edited by utechle on 01-27-2009 11:12 PM

Application crashes when calling DLL built with LabVIEW 2011

Hello everybody,
Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
Thank you in advance.
#Date: Fr, 16. Sep 2011 16:25:25
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: PasTA
#Version: 11.0f2 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
16.09.2011 16:25:26.181
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
ExceptionCode: 0xC0000005
N
0x3072C804 - lvrt <unknown> + 0
0x3072CBB8 - lvrt <unknown> + 0
0x7C864191 - KERNEL32 <unknown> + 0
0x7C83AB50 - KERNEL32 <unknown> + 0
0x00000000 - PasTA <unknown> + 0
Attachments:
error.PNG ‏11 KB

On that note, you should be able to create DLLs in 2010 and run them with 2011, correct?? In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

Has somebody already used Applicom PCI2000ETH Card or Applicom SW1000ETH software to communicate with ETHERNET bewteen siemens s7-300 and LabVIEW DSC ?

I want to use ETHERNET and not PROFIBUS to communicate and I think you can do that with only the applicom software SW-1000ETH. You must just have an ethernet card on your PC. So, you could use a notebook with an
ethernet card. You can also use Applicom PCI2000ETH for better performance.

Hi,
You might be able to get the configuration listed above working as long as you can get from Siemens/Applicom or any other third party provider a OPC Server that communicates with the S7-300. Since LabVIEW DSC is a OPC client, you would be able to establish connection.
The National Instruments driver for the S7-300 (Containnned in the product called "IA OPC Server CD") does not support communication through ethernet directly, you would either have to have a Profibus board or use a serial port with a Siemens HMI Adapter.
I hope it helps
Best Regards
Andre Oliveira

Labview crashes with Excel ActiveX

Dear all,
I have written a program to read and write the data in the
excel using ActiveX sheet but crashes the Labview drastically when
executed.
Please go through the attached files.
Actually the program has to sort the data in ascending order in a
column in a
Specified worksheet and it should write the sorted data in another
worksheet in the same excel file itself. But while writing it should
neglect the repeating data and should write the corresponding data in
the other column with respect to sorted one.
For example , In datafile.xls in sheet1 cells are like below. Let a,
b & g are columns
a1=0.02, b1=2.1 , g1=0.1
a2=0.04, b2=4.2 , g2=0.3
a3=0.05, b3=4.2 , g3=0.35
a4=0.06, b4=4.3 , g4=0.43
a5=0.0
7, b5=7.1 , g5=0.43
a6=0.08, b6=7.2 , g6=0.43
a7=0.09, b7=7.2 , g7=0.75
a8=0.11, b8=7.4 , g8=0.75

I am not sure what is causing the crash. Can you give us more information? For example what does the crash say, when you relaunch LabVIEW does it comment on an error log file?
The code you mentioned was not attached, so I was not able to try and reproduce it. I would be happy to try it here, if you can attach it.

Labview application crashes with a Dr Watson Access violation c0000005 in win2K service pack 2 and 3

The application was developed on a Dell Optiplex PIV 2GHz, 512 MB Ram using LabVIEW 6.1 Profesional Control Development Suite. The exe runs for between 10 minutes and 21 days before exiting with a Dr Watson Access Violation error 0xc0000005. The basic stack dump info is as follows:
Application exception occurred:
App: (pid=312)
When: 2/4/2003 @ 20:54:51.843
Exception number: c0000005 (access violation)
*----> System Information <----*
Computer Name: NO1
User Name: No1
Number of Processors: 1
Processor Type: x86 Family 15 Model 2 Stepping 4
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 2
Current Type: Uniprocessor Free
Registered Organization: xxxxxxxxxxxx
Registered Owner: xxxxxxxxxx
*----> Task List <----* edited for brevity
312 xxxxxxx.exe
1056 drwtsn32.exe
0 _Total.exe
State Dump for Thread Id 0x38c
eax=78e34ff8 ebx=79288ab8 ecx=00000001 edx=78e338cc esi=78e34ffd edi=78e338d1
eip=3027bf0d esp=0012fc70 ebp=0012fc7c iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000202
function: MoveBlock
3027bef7 fc cld
3027bef8 eb15 jmp CheckFPStat+0xe52 (3027ce0f)
3027befa 0fbae100 bt ecx,0x0
3027befe 7301 jnb CheckFPStat+0xa344 (30286301)
3027bf00 a4 movsb ds:78e34ffd=32 es:78e338d1=00
3027bf01 d1f9 sar ecx,1
3027bf03 0fbae100 bt ecx,0x0
3027bf07 7302 jnb CheckFPStat+0x654e (3028250b)
3027bf09 66a5 movsw ds:78e34ffd=3532 es:78e338d1=0000
3027bf0b d1f9 sar ecx,1
FAULT ->3027bf0d f3a5 rep movsd ds:78e34ffd=???????? es:78e338d1=00000000
3027bf0f 5e pop esi
3027bf10 5f pop edi
3027bf11 59 pop ecx
3027bf12 8be5 mov esp,ebp
3027bf14 5d pop ebp
3027bf15 c3 ret
The error is always "move block" and leads me to believe that it is a windows memory manager issue but I cannot resolve it. The application connects to an ethernet GPIB interface and to 10 Opto22 Ethernet brains via activeX. The processor runs about 25%, there are no apparent memory leaks, and there is at least 300Mb of free ram when the crashes occur. Any suggestions?
Thanks,
Ian

I am having the same issue with LabVIEW 7.1
From Dr. Watson:
Microsoft (R) Windows 2000 (TM) Version 5.00 DrWtsn32
Copyright (C) 1985-1999 Microsoft Corp. All rights reserved.
Application exception occurred:
App: (pid=2208)
When: 10/21/2005 @ 13:09:12.530
Exception number: c0000005 (access violation)
*----> System Information <----*
Computer Name: WEESUSCILPCWRM0
User Name: RDL
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 1
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free
Registered Organization:
Registered Owner: Administrator
*----> Task List <----*
0 Idle.exe
8 System.exe
168 SMSS.exe
192 CSRSS.exe
188 WINLOGON.exe
240 SERVICES.exe
252 LSASS.exe
396 scardsvr.exe
472 svchost.exe
500 spoolsv.exe
568 dklog.exe
592 svchost.exe
616 FrameworkServic.exe
688 mcshield.exe
708 vstskmgr.exe
728 naPrdMgr.exe
844 regsvc.exe
860 mstask.exe
900 Smc.exe
1020 WinMgmt.exe
1048 Wuser32.exe
1076 CcmExec.exe
1188 dkcktkn.exe
1876 svchost.exe
916 explorer.exe
2172 shstat.exe
1988 tbmon.exe
1200 UpdaterUI.exe
2012 dkAutoReg.exe
2072 ERClient7.exe
1916 LabVIEW.exe
2288 notepad.exe
2284 notepad.exe
2208 WINWORD.exe
2424 agentsvr.exe
1900 DRWTSN32.exe

Labview crashes with access violation(0xc00000050at EIP=0x7c8219a6

when i poen my project in labview ,it crashes with "access violation(0xc00000050at EIP=0x7c8219a6.why is this happening?how can i open my project?

Probably nothing to do with it but I had some dodgy memory, and windows would complain that there was an error to do with that exact memory location: c0000005

LabView / DSC / FieldPoint with Symantec Endpoint Encryption Device Control

I am developing a LabView DSC based control program to communicate with multiple FieldPoint modules (cFP2200/cFP1808) for a client. Their IT department has implemented Symantec Endpoint Encryption Device Control ( http://www.symantec.com/endpoint-encryption-device-control ) and I was wondering if anyone has had experience with this software?
From what I have read and had explained to me, it is much more than an antivirus program. It operates at a very low level within Windows and restricts reading/writing to external devices, USB sticks, network shares, etc. It can also monitor / restrict network traffic and WiFi access.
Thanks,
Steve

Hi MillerMech,
I believe it will cause some errors to be thrown due to its restrictive nature. Symantec has a discussion forum which will most likely be more helpful:
http://www.symantec.com/business/support/index?page=home
Sunaina K.
Product Manager
Embedded Systems

External clock LabView crash with Measurment Computing board.

Hi,
I'm using a Measurment Computing PCI-DAS6402-16 board with Labview (using Universal librarys VIs) in a 4-stroke engine DAQ application and amognst the signals obtain Internaly clocked, there is In-Cylinders Pressure signal which is timed with a Crank-angle deocoder sending analog pulse signal.
Although there seems to be no problem while the motor is running, it appears that when to external clocked signal is not getting any pulses (while the motor is not running) then Labview stops to respond and awaits for the external clock to start, and that doesnt happen within 10s then it crashes.
I dont know whether it is Software problem (because external and internal clocked signals are both in the same WHILE LOOP) or if it is a Hardware problem (because With a NI card there seem to be no problems).
THNX in Advance

Well it couldnt be a more typcal windows crash:
If a channel is externally timed with an analog pusle signal, If the VI starts running but the external clock isn't then:
-Labview stops to respond to any clicks (there is no .exe at this point) but it keeps working though (That i know cause if i start the ext. clock at this point it "un-stucks' and starts working)
-But, if for some secs no ext. pulse signal is generated then labnview app stops respondin and i get the typical 'send error report' window.
Could it be that the Universal library for Measurment Computing boards haw a bug? Cause the same thing happens with the "Analog input External Clock.vi" example given with the Library..so it can't be my mistake..or can it?!

Crash with labview DSC

Similar Messages

Maybe you are looking for