Stopping a program in debug mode
Hi all,
i have am having a intermitent issue with a program. first let me give you the issue and then the specs.
This is an inconsistant program lockup. when the program runs in an, .exe format it runs fine for an hour to a couple of days and then goes to a white screen and freezes. the program is basically just continiously reading a DAQ card and comparing readings to set values.
if i have the program running in Debug mode thru CVI and it freezes, CVI sees it as running (in top left hand corner of CVI interface), if i push the stop button (break execution) the break execution dims but the program never stops and the Running indication is still active.
question--- is there another way to stop the program while it is in this frozen state to see where the issue is hanging up. like a hard stop command ????
I can only stop the program by using task manager and ending CVI there. which does me no good in finding the freezing point.
CVI 2012 sp1
with a PCI 6071E DAQ
There isn't an easy way to debug this kind of events.
The behaviour you are seeing (stop button dimmed after click but program that soesn't stop) normally happens when the program is stuck in a operation waiting for it to finish before breaking into the IDE. It may be a popup message waiting for user input, a I/O operation with a long or infinite timeout...
To deal with such a kind of thing you can for example write operations to a log file -one line before each critical call and one after that- so that you can at least see where it hanged. Alternatively you can use DebugPrintf to write messages to the debug output window: if in the IDE you have this window listed in Windows menu, if an .exe you can use utilities like DebugView to receive those messages. Another alternative can be to use Remote Debugging.
However, this is only a list of possible instruments and techniques: solving these problems usually ends up in a boring task of trial and error to narrow down to the critical situation and trying to overcome it.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?
Similar Messages
-
Can't Run program in Debug Mode
To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about 50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business Model we
are wondering if Forte is timing out during the partition phase or if the
server partition is running out of memory . The following error messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor", (partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada
-----------------------------------------------Hi,
We have had the same problem in a non-express application
with a heavy server partition. In our case, the error was not
systematic, depending on the server workload at the time we
tried to partition and run.
The work-around we're using is to put the -fm flags (increasing the x
parameter to say 30000) in the 'server arguments' of your server
partition
properties in the partition workshop. Note that if your server is a Unix
platform,
you need to put double-quotes before and after the parenthesis in the -fm
syntax.
Hope this helps,
Vincent Figari
BTW, what Forte version are you using ?
On Tue, 2 Dec 1997 13:44:24 -0500 "David Wilbur"<[email protected]>
writes:
>
>
>
>
>
To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a
non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about
50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business
Model we
are wondering if Forte is timing out during the partition phase or if
the
server partition is running out of memory . The following error
messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition
testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of
the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more
information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called:
qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor",
(partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means
the
process at the other end of the wire failed. Please go look there
and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition
testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition
testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition
testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition
testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode:
SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada -
How to run labview program in debugging mode in windows 95 version
Respected all,
I am facing probelm while running probe.vi.
I received this command "connection to acquisition board was not found" when i run labview program.
I am using labview 5.1, fieldpoint FP 1000, NI-DAQ 6.5, Field point explorer version 1.6, Measurement and Automation Explorer 1.0.1.
I would kindly request you please help me how to run my program probe.vi in debugging mode in windows 95 version, so that i can locate where error occurs.
Thanking You
Yours faithfully
M.VijayRespected Norbert,
Thank you very much to for your help.
Norbert : Possible reasons are e.g. wrong IDs for measurement devices. If the error is connect to the FieldPoint, it is possible that it isn't configured correctly.
I am using Field point explorer 1.6, The Field point instrument FP 1000 and RS-232 port is using. It is confirmed that the field point instrument is working properly by LED light indication test.
Norbert: It sound like you are using DAQ devices (like PCI MIO 6952E) in the application. Are you sure that you select the correct device ID for this?
I am asking you to know, If i using Labview and Fieldpoint instrument FP 1000 to monitor my parameter interms of All, Channel 0, Channel 1, Channel 2, Channel 3, Channel 4, Channel 5, Channel 6, Channel 7 for my measurement.
But now i need to solve the command connection to acquisition board was not found, The expert say this command is due to there was no AT-AO-10 Analog Output board was present in CPU.
I do not find AT-AO-10 Analog Output board in my CPU, Previously the instrument was worked perfectly by other person who assembled everthing to measure temperature.
The only aswer know send by previous person is if my task does not imply the use of a DAQ you probably have to locate where the DAQ driver is called and exclude it from the program. try to run the program in debugging mode so that you can locate where the error occurs.
I do not know how to proceed his instruction. So i would kindly request you to please help me to solve my probelm.
I also removed AT-AO-10 software from device manager >> Data Acquisition system >> AT-AO-10 just now.
I also find GPIB version 1.30, when i remove in add or remove program, it say that Error removing the GPIB.
I am eagerly waiting for your help.
Thanking You
Yours faithfully
M.vijay -
Start/stop user programs with laptop-mode
Hi,
i am trying to place some scripts in /etc/laptop-mode/*start[stop] to kill and start some programs when on battery or ac.
I tried with the following script, but the process is just a zombie and dropbox will not appear: any ideas?
#!/bin/bash
case "$1" in
start)
su pschw -c
/opt/dropbox/dropbox &
stop)
killall dropbox
echo failed!
esacHi,
i am trying to place some scripts in /etc/laptop-mode/*start[stop] to kill and start some programs when on battery or ac.
I tried with the following script, but the process is just a zombie and dropbox will not appear: any ideas?
#!/bin/bash
case "$1" in
start)
su pschw -c
/opt/dropbox/dropbox &
stop)
killall dropbox
echo failed!
esac -
Help debug mode: Stops at breakpoint, but line is not highligted, no actions selectable
I just reinstalled Pydev and now debug mode no longer works.
I run a program in debug mode. Without a breakpoint, the program runs through. When I set a breakpoint, the program pauses, as it should, but the code line is not highlighted. This also means that none of the debug actions are selectable (step into, etc.), although they are visible. I only have one breakpoint.
The 'debug' option (next to pydev and java options) is selected.On 08/09/2015 02:31 PM, ttt bbb wrote:
> I just reinstalled Pydev and now debug mode no longer works.
>
> I run a program in debug mode. Without a breakpoint, the program runs
> through. When I set a breakpoint, the program pauses, as it should, but
> the code line is not highlighted. This also means that none of the debug
> actions are selectable (step into, etc.), although they are visible. I
> only have one breakpoint.
>
> The 'debug' option (next to pydev and java options) is selected.
Unfortunately, PyDev isn't Eclipse. It's a set of third-party plug-ins
you'll have to get support for in another forum. -
Problem connecting to Realtime system to download or run in debug mode
I have updated my LabWindows\CVI to 2013. I have a PXI system with a PXIe-8101 controller. The PXIe-controller has a real-time OS installed. I have been programming this system for a while now so I am not exactly a novice anymore. The first time I tried to install the program to my real-time target I got a message which said "LabWindows/CVI cannot connect to the real-time target." It also said " .... The version of the LabWindows/CVI Run-Time Engine for RT must be compatible with the version of the LabWindows/CVI development environment."
So I figured that was the problem. My next step was to go into MAX and sure enough was getting all sorts of flags and errors when I used the real-time software Wizard in MAX by right clicking on the Remote software and clicking on Add/Remove Software. And like I suspected there were several flags indicating a software differences. My next step was to update the software in my real-time target to resolve the problem. After I did that I compiled the code and installed it on my remote system. Everything seemed OK.
The following Monday I restarted LabWindows/CVI and made a couple of changes and tried to build and install to my real-time target. I get that same message as in the first paragraph. So I thought I might not have real-time system booted up correctly or something like that so I checked all of that and it looked OK. Next I opened up MAX and it could see my real-time target just fine.
When I had my LabWindows/CVI 2012 I did not have this problem. I think maybe there is some incompatibliity issues with my LabWindows 2013; has anyone had a similar problem? I am able to get around the problem by building the release version and copying it to the PXI with CuteFTP V9.0 but I cannot do run my program in debug mode with my LabWindows/CVI and if you may have noticed I have other problems which is in another post I put in next week. I am hoping the problems are connected and I can kill two birds with one stone LOL.
I appreciate any suggestions.
Thanks,
Don PearceHello,
I want to make sure I'm understanding what you are doing in the LabVIEW project. According to the Getting Started with the LabWindows /CVI Real-Time Module manual, these are the steps to install software on the RT target:
1. Launch MAX.
2. Find and expand your RT target under the Remote Systems item in the MAX configuration tree, right-click Software, and select Add/Remove Software. When you select Add/Remove Software, MAX launches the LabVIEW Real-Time Software Wizard. This displays all the National Instruments software and drivers installed on the host computer that you can install on a selected RT target.
3. Select the software you want to install on the RT target, click the icon next to the software, and select Install the feature.
You need to install LabWindows/CVI Run-Time Engine for RT to add support for LabWindows/CVI RT applications on the RT target. This component is required for all LabWindows/CVI RT applications.
The forum post here solved this same issue by installing missing drivers based on this KnowledgeBase article.
Also, LabWindows/CVI 2013 SP1 has been released. Service Pack 1 (SP1) has many useful bug fixes (listed here), so I recommend upgrading to LabWindows/CVI 2013 SP1 if possible.
Taylor B.
National Instruments -
Reset Preference for Launch in Debug Mode
I accidently clicked "Don't ask me again" when queried whether I want to always launch in debug mode when I debug. How can I reset that. The obvious place under Run/Debug in preferences didn't work for me.
Hi Jeff,
I'm assuming that you are using JDev 9.0.3.
Make sure that your project has the "Oracle JDBC" library selected. This can be done on the Libraries panel of the Project Settings dialog box.
Are you saying that you get the ClassNotFoundException when you step through your program in debug mode, but when you run you program it works fine?
-Liz -
Hi all,
i need to stop the program flow control without entering into the start-of-selection.
i am using some manual conditions for validating some parameter fields...
i used Leave list-processing--->but it dosint works
call selection-screen 1000--->it works but when i click the back button the control goes inside the start-of-selection can any one help me with this....If you want to stop the program flow in case one condition is satisfied, you can use STOP or EXIT command. Else, if you want to stop the program and debug it just but BREAK command where ever you want to stop the program. Also, if you want to validate the program selection at the time of entering the selection before the start of selection, you need to add AT SELECTION-SCREEN event block before the start of selection.
-
Problem when trying to run in "Debug Mode" in JDeveloper9i
Hello All ,
i have a problem to debug my application using
JDeveloper9i .
i get an error: "fdebug.exe could not be read "
and Application error box appears .
i did the following steps in the instalation:
1) i installed the JDK 1.3
2) installed the Jdev9i from base installation zip
3) In <jdeveloper_root>\jdev\bin\ i executed the command
InstallOJVM.bat c:\jdk1.3
and get message:
"InstallOJVM successfully"
4) i wrote simple program and put a breakpoint ,
when i'm trying to run the program in "Debug mode" i get an error box message
"fdebug.exe Application Error"
The memory instruction could not be read
please help ,me to fix the problem i need the debuger option .
thanks in advance.Do you have the file c:\jdk1.3\jre\bin\fdebug.exe, if you don't, you
need it. Look for the file in the base install directory, it should be
there and then copy it to the location above.
Michel -
Hi there,
I'm coding a program in SE38 in a BW environment and there is a function call made (RSDRI_INFOPROV_READ). It seems that the table returned by this function won't accept double entries (which should be the case for standard tables), however, when I execute my program in debug mode, it does everything like it should. Anyone knows why it doesn't work when i choose execute as background job? It's hard to find what's wrong since in debug all goes well...
thank you,
TomWhy not debug the program in background running？You can add a endless loop before the code you are interested in, and then enter debug mode to jump to the focus code at background job console.
-
The program is automatically launching into the debug mode.
Hi,
I have written a small servlet program. When I try to run the program it automatically launches itself into the debug mode. I have tried all things but I am not able to prevent this from happening. Can anyone help me with this.
Regards,
PrashantMy guess is you have one or more breakpoints set in the application. When it its that breakpoint, it goes into debug mode. Run the application and not what file and what line it stops on. In Eclipse IDE, you will see a blue dot next to the line that the breakpoint is on. Click on the blue dot to remove it. If your code is not too large, look through all *.java files for that blue dot and remove them.
-
CVI under W2K crashes when using stop in debug mode and AOGenerateWaveforms
When using AOGenerateWaveforms to generate a sine wave. If you hit stop in debug the PC restarts. If you're using the same channel to generate a DC signal, it's fine. Seems to be the card accessing the dynamic memory I've set the waveform up in after you hit stop and the memory has been free'd.
This is sometimes the nature of the beast. When your program is running you are doing DMA transfers to locations in memory that have been setup by your operating system. Now if you stop your program, with out killing or stopping the DAQ device it will cause you problems in some cases. You need to call AOClearWaveforms before you stop your program.
If you do not stop the DAQ device, before stopping your program it will cause the DAQ device to write to memory that is no longer allocated for that process. In most cases windows detects this as an error and reboots the system, because it thinks a program has crashed and is now writing to memory locations out of its designated space.
I hope this helps.
Joshua -
My program works only in debugging mode
Dear All,
I am just starting to use LabVIEW and developing a instumental driver.
The program is rather sequentially designed because I am only used to work with text-based program.
The current program is working in debugging mode without any error message.
To give an idea of how it is composed:
1. Set up the serial port setting (machine address, baud rate, parity, etc)
2. Send to the instument the name of a short program to be run.
3. Send mutiple string commands to the instruments. Those string commands construct a short program to control the instrument.
4. Send another string command to run the short program
The issue is that it does not work in excution mode. It looks to me that the communication between the instrument and computer seems to be too fast.
Since the program is designed in a sequential manner, it does not have any while-loop or for-loop so I cannot add any timing function.
Could anyone give me a hint or a right direction to fix this issue? It would be really appreciated. Thank you.
Solved!
Go to Solution.You could do something like the attached modification.Note how I modified the connector pane for the subVI to use the conventional 4-2-2-4 pattern and notice where I connected the terminals.
NOTE: I am assuming the VI is supposed to run just once, and that you're not using the Run Continuously button in the toolbar. You're not, right?
Attachments:
NE-100_StairFlow_w_RUN00 MOD.vi 27 KB
NE-100_RAT_00_XX MOD.vi 18 KB -
Program running fine in Debug mode but failing in direct execution
Hi All,
I am facing a peculiar problem, I have created a report that create STO then Delivery and then Shipment one after one. I have used BAPI to do so. If STO creation is successful then Create Delivery and if delivery creation is also successfull then create Shipment.
When I run this program by pressing execute button it is only creating STO and coming out ,but if I run it in Debug mode I get all the three( STO, Delivey,Shipment). Since it run fine in debug so I can't found where the problem is.
Can any one help???
Regards
HemantHi guys,
A learning for me .... how important WAIt parmeter is in commit work .. Initially i have not set WAIT paramater in commit BAPI to X due to this further processing.. Delivery and Shipment creation was failing in direct execution ... as after STO creation I was reding EKPO and that was failing in direct execution , but in backgroung everything was ok.
Thanks for your time.
Cheers
Hemant -
Debugging mode stopped automatically when using xml file load
Dear Sir,
I am trying to develop a new add-on using xml files for creating new forms. In fact I was using the sample code delivered with the SDK ( WorkingWithXml - under VB.NET). The Problem is that when I am in the debuging mode and after the form load. the application goes out of the debugging mode and stop action.
In fact what i was trying to do first is to create a new menu and then when i click on this menu a new form appear but once the menu is loaded the application stop the debugging mode automatically.
Can somebody clarify to me what I am doing wrong and why the debugging mode is stopped automatically, noting that i am still in the add-on developpement phase.
As i mentioned above i used the WorkingWithXml sample code (VB.NET) and i have adjusted in a way to load menu and then on the menu click i load my form.
Please advice
Best RegardsHi Mary,
Put your code between in a Try Catch block. In the Catch part use the following:
oApplication.MessageBox("CompError: " & oCompany.GetLastErrorCode.ToString & ", " & oCompany.GetLastErrorDescription & vbCrLf & "Message: " & ex.Message)
This should give you a clearer idea of what the error is all about.
The most likely reason is that there is something wrong with your XML file.
Regards,
Vítor Vieira
Maybe you are looking for
-
Not scheduling on manual creation of planned order
Creating planned order through MD11 and noticed there scheduling not done and capacity planning not done and on doing scheduling manually dates altered and capacity planned which are appearing in CM01 for the respective week Planned order created thr
-
Hello QM masters, Iu2019m trying to use the QM-IDI, but Iu2019m having some difficulties with the function modules to update the characteristic results. I tried to use the function module QIRF_GET_ORIGINAL_VALUES2 and QIRF_GET_FEATURE_VALUES2 and I g
-
Reg: Automating Miscellaneous Issue
Hello Everybody, I have one query, i am presently working on interface. i have a requirement of automating the Miscellaneous Issues periodically. i want some of my items to be issued out of oracle automatically at regular intervals. Is there any Poss
-
Java.sql.SQLException: Io exception: A remote host did not respond within t
Hi All, I am using SUN ONE Webserver 6 on AIX with Oracle 8i. Every now and then I get this error java.sql.SQLException: Io exception: A remote host did not respond within the timeout period. I am not able to unterstand this. Some one please help...
-
Entourage: iPhoto 9.4.1 not working!
I've found both 9.4 and 9.4.1 to be unstable. They are slower than previous versions, do not recognize or load my SD cards (it takes several insertions/ejections) and the worst part I can't email from Entourage. That feature was working in 9.4 for a