Break Points during Contour Move

We are using PCI-7340 (Firmware Version 68331) for a 2 Axis laser cutting application. The contour points are generated and fed to the 2D Contoured move.vi which works great for most part.
In our application presently we can have 9 to 15 contours per sheet. The laser is turned ON before start of the contour move and turned OFF after finishing the move. And the cycle repeats until the sheet is processed.
We would like to increase the productivity by combining all the contour points into one big contour move but not loosing the control over laser (ON/OFF). So, Is it possible to have BreakPoints embedded in the Contour data? We can not have Breakpoints based on single axis position because for a particular contour move an axis may move through that position (X or Y) multiple times. We need to define the (X,Y) location where that I/O transition needs to happen. Alternatively we can identify the contour point (contour buffer array number) where the transition needs to happen.
Thanks.

Sorry, I just realized that I asked almost the same question a while back and it was answered by NI person.

Similar Messages

Problem chosing layer break point for multi-movie DL DVD

HI. If you're authoring a DL DVD containing several short movies which can be selected from a menu in any order, how are you supposed to know which order they're burnt to disc in so as to know where the layer break point needs to be? Is media burnt in the order it's added to the project or what? Does it actually matter about choosing a LBP manually so long as DVDSP provides a choice of automatically determined points?

You can use VTS view to see the order they are laid out in
http://dvdstepbystep.com/vts.php
As to manually selecting a layer break, you can if you want to, especially if you know a section is a fade to black (for instance) where it will be less noticeable.
Some background -
There has to be a break point where it crosses over from Layer 0 to Layer 1, if you have no Chapter Markers at all (or a limited number of Markers, none of which fall near the point which is a bit more than half the size of the assets you will get an error that a Layer is the wrong size.
What you do is
1.) Set up markers in the areas where your would guesstimate the Layer Break(s) should be
2.) Build the project (but not format)
3.) Format a Disc (in the dialog that comes up, click on advanced tab, then where it says break point, use the pulldown which will have all valid breakpoint markers dark/black, while non-valid Layer Break Markers will be faded) If no marker is black there is no marker in the right place, regardless of you use automatic or not.
4.) If the layer break(s) are not where you would like them (in other words a place where they may be more noticable) use VTS view to re-order then go back to step 1.
When you do enough DLs, you start getting a sense based on the size of tracks where things should land

Break points set in an included script during debugging sporadically jump to the last line of the included script

As I stated in the title, I use the ScriptInclude command quite extensively, because we have at our company a policy of maintaining one large-ish (roughly 7k lines) function library which is included by various individual evaluation scripts. Debugging this with break points is often the only (useful) way to see into the state of the script, so I depend on them.
My problem is that often when I debug a script calling the function library, setting a break point in that library and running into it during debug mode will not transport the cursor to the location of the current break point, but instead to the very end of the included script. I have noticed this with a separate pair of scripts, as well, which includes a similar size script to call functions from (roughly 2k lines).
Now I wonder if this has to do with the size of the scripts included, or if it is dependent on something else. It seems to not be affected by restarting DIAdem, and sometimes it works as intended, but I have not been able to reliably replicate indivdual occurrences one way or the other.
Has anyone else had this problem happen to them?
Leo Zschokke
Test Engineer C-EPS
ThyssenKrupp Presta AG

Leo
I also use scriptincludes extensively, Most of mine are in the range of 500 to 2000 lines. Usually I organize them in logical code topics, I like to use them to hold one class most of the time. When I debug these I can set a breakpoint, and it will stop at that location.
I also use custom log class as well, I find this quite helpful, in the applications that are unattended.
The only thing I can think of to try is to separate the 7k file into 2 2k line files and then script include them separately.
Paul
ps. I sometimes need to have intellisense work from a file that was scriptincluded, this requires copying the file into the end of the main script. (you most likely already know this )
One other note, Are you talking about debuging code in a SUD, that is whole different problem to deal with.

"Thread Being Stopped" during break points

Hello Everyone,
I read few threads about this topic but couldn't find a solution. So, if anyone has a solution please help me.
I am using Visual Basic .NET 2003 and SAP BO 2005 Patch 31.
I couldn't use breakpoints because I am getting this exception "Thread being Stopped". It is giving me a hard time programming.
I used to have patch 25 and earlier I could use the breakpoints without any problems. But recently I upgraded it to patch 31. After I upgraded it, I am not able to use the breakpoints because of this error.
Any advise regarding this problem is welcome.
Thanking you,
Yours,
CK.

Hi Chanikya!
i use Microsoft Visual Studio .Net 2003 / SAP B1 2005 A PL 31
in this case i've made my experience that if you want to step during the break points, there will be problems if you want to access objects from SAPbobsCOM..but if you want to access objects from SAPbouiCOM, there are no problems.
I don't know how to solve this, but maybe this is your problem too...
hopeithelps
Matthias

Can't move Layer break point

Hi,
In desperate straits here. I've created a dual layer project and set a break point via the disc inspector drop down menu. Now I need to change the break point but DVDSP won't execute the change. I've deleted the VTS build folders as Apple recommended but that has no effect. This is the second project- after running into the same problem prior, the only solution that I could find was port all of my assets and start a new project. I was able to set the break point once but now I'm back to where I was the first time. Any help that anyone could give would be tremendously appreciated. Thanks in advance.

Thanks for the reply...unfortunately that isn't the problem. I haven't tested my theory yet, but I now have an idea what happened and if correct, I would consider it a bug. A big bug.
When setting my break point, I did so via the disc inspector drop down menu and went to the track of choice and selected "track" as my breakpoint rather than selecting a mark of any sort. Once formatted and built, it seemed to have locked the breakpoint in place and would not even let me delete the track in an effort to clear it. After porting all of the items (via item descriptions) into a new project I created the breakpoint using a marker in the track. Viola, it now behaves as it should.
I will be testing my theory as soon as I have a free moment...meanwhile, my layer breaks will come from a marker specifically created for it.
Thanks again.
G5 Mac OS X (10.4.3) FCP 5.0.3, DVDSP 4.0.2
G5 Mac OS X (10.4.3) FCP 5.0.3, DVDSP 4.0.2
G5 Mac OS X (10.4.3) FCP 5.0.3, DVDSP 4.0.2

Contoured move and move constraints

The NI-Motion User Manul tells' A contoured move moves an axis or a coordinate space of axes in a pattern that you define. The trajectory generator on the motion controller is not used during a contoured move. The controller takes position data in the form of an array, and splines the data before outputting it to the DACs or stepper outputs' and ' The move constraints commonly used to limit other types of moves, such as maximum velocity, maximum acceleration, maximum deceleration, and maximum jerk, have no effect on contoured moves. However, the NI Motion Assistant prototyping tool can remap a user-defined trajectory based on specified move constraints, preserving move characteristics and move geometry.'. How the move constraints works in NI motion Assistant prototyping tool in the contoured move?

Thanks. Can I get the output position data of Smart Contouring?
In the contoured move, the motion time between two continous points is the sampling period, is it correct? I am really confused with the stepper motor controll by 7344 using closed-loop control.
I developend an interpoaltor in which I set the time interval between two sequential interpolated point is 1ms and this value can be changed. To get the smaller chorderror, the time interval also should be small. When I do the experiment using contoured move (stepper motor +7344 +closed loop), the velocity is very slow. I think the reason is that time interval of the control loop is much bigger than the time interval used in the interpolator. This means the motion time between two sequential point is increased consequently decreases the velocity. Anyway I am not sure about this. Is anyone has any idea?
^_^

Break point in EXIT_SAPLV05I_002

Hi, I nead your help.
I've already put a break point in EXIT_SAPLV05I_002, INCLUDE ZXV05U05 but when I crete a delivery the debuging is not started.
Dou you know in what moment this exit should stop?
Thanks
Dora

Hi Venkat
Your user exit does get processed during the delivery save.
Your breakpoints are not stopping in it because all the indexes tables VKDFS, VEPVG etc
are handled in the update task, so you have to use update debugging.
The quick wat to get to your user exit to see what is is doing is as follows:
Create a delivery in VL01n
Before you hit the save button switch on the debugger
then press save
In the debugger oput a breakkpoint on the ABAP statement COMMIT WORK
The program will stop at this statement which is the end of the application processing.
In the debugger go to SETTINGS > UPDATE DEBUGGING
Then press F8 to contunue
A new screen will appear with the update task.
In the new screen put a breakpoint in function module RV_DELIVERY_INDEX_SAVE
( If this were from a sales order you would do the same but with function RV_SALES_DOCUMENT_INDEX_ADD)
Your user exit is called below marked :
RV_DELIVERY_INDEX_SAVE
Billing type appears in the index if there is at least one R/3
billing relevant item in the delivery
     if vbuk_wa-fkstk ca 'AB' or
        vbuk_wa-fkivk ca 'AB'.
perform lk_01.                   "Fakturaauslöser           >>>>>>>
    EXIT_SAPLV05I_002 is called in here....
I hope this helps explain the system behaviour
Kind regards
Brian

Can any one explain me about break point

Hi gurus
What is break point what is the use of it? please let me know what is the use of it?
Thanks in advance

Hi
Hi,
A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.Max 30 breakpoints we can use.
Session Breakpoints exist only until you are logged in or until ur session is active. Even if u forget to remove the session break points, they are automatically removed once ur session becomes invalid or u logged out.
Debugger
This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
Functional Overview
Use
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Direct Processing
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator
Select a report or transaction and choose Program ® Test ® Debugging.
From the ABAP Editor
Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
From any screen
Choose System ® Utilities ® Debug ABAP.
From any screen
Enter /h in the command field.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields
The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table
Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints
A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints
You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls
This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview
This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings
This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto ® Display data object.
Single field
Displays the contents and technical attributes of a field.
Structured
field
Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings
Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table
Displays the type, line numbers and contents of an internal table.
Object
Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
Displaying Program Attributes
You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
Restarting the Debugger
If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
Breakpoints
Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statement
The Debugger stops the program directly before the specified statement is executed.
Breakpoints
at subroutine
The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module
The Debugger stops the program directly before the specified function module is called.
Breakpoint at method
The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions
The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter that only activates the breakpoint after it has been reached
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1.Choose Breakpoint ® Breakpoint at ® Statement...
The following dialog box appears:
2.Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3.Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
The following dialog box then appears:
Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
Choose Breakpoint ® Breakpoint at ® Function module...
The following dialog box appears:
Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at Methods
You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
Prerequisites
You must be already running the program in the debugger.
Procedure
To set a breakpoint for methods:
1. Choose Breakpoint ® Breakpoint at ® Method...
The following dialog box then appears:
2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the list in the display.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint ® Breakpoint at ® System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
Position the cursor on the line of the source code at which you want to set the breakpoint.
Choose Utilities ® Breakpoints ® Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities ® Breakpoints ® Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
Position the cursor on the line in which you want to set the breakpoint.
Select the line by double-clicking it or choosing Breakpoint ® Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint ® Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint ® Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto ® Control debugging ® Breakpoints.
Example
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
Regards
karthik

ZCL_IM_COM_PARTNER_BADI - not breaking on break point.

I have implementated a BADI but the methods
IF_EX_COM_PARTNER_BADI~DETERMINATION_ADD_IN_1,
and
IF_EX_COM_PARTNER_BADI~DETERMINATION_ADD_IN_2,
and
IF_EX_COM_PARTNER_BADI~DETERMINATION_ADD_IN_3
are not been called and when I but a break point inside IF_EX_COM_PARTNER_BADI~DETERMINATION_ADD_IN_3 it doesnt break during the creation of service oder.
Kindly assist.

fill in your batch sequence=10, dialog seq.=10 if it's the first access.
If your source is COM_PARTNER_X, then go to se18, enter badi=COM_PARTNER_BADI.
If you already created implementation, should find it under implementation menu -> overview and select your implementation. Otherwise, create a new one.
Then go to interface tab and click on DETERMINATION_ADD_IN_1 method. Implement your source codes here. Put an external breakpoint for testing.
Dont forget to assign your access sequence in the 'Partner function in proceudure' in partner determination procedure.
Lastly, assign the partner determnation procedure to your service order trx.

Suitable marker break point error for dual layer DVD!

I'm a new FCP user of a few months and DVDSP of one week.
I have read the manual again and again and I am still not sure how to add a suitable break point. I added a chapter marker and set it as a dual layer break point, not sure if that is correct. Quicktime Movie is 5.9 GB, it does everything except burn to DVD in SP. I can burn this movie in IDVD though. Please help me!
Thank you in advance for your help, I appreciate the assistance everyone so willingly gives. Thank you!

Will compressor or Mpeg cause degeneration of picture quality?
If you put it on DVD-Video, you have to convert it to MPEG2 (with either Compressor or by letting DVDSP convert it). It will lose quality as a result. The only way to minimize this is to use as high a bitrate for your MPEG2 file as possible. Compressor has some presets labeled 60 min, 90 min, and 120 min, that will allow movies of that length to fit onto a single-layer DVD.
You should probably re-read the opening chapters of the DVDSP manual; they cover this important and fundamental information relatively well.

How to start a contour move from a non-zero position

Hi,
I am using a PXI 7344 motion controller under LabVIEW 8 to do a vector contour move. How can I start the contour from a non zero position ? I want to use absolute position mode. The test requires the x axis to move to a known distance and wait for a known time (more than a 1 hour) before the contour starts.

Hi Milinda,
Unfortunately the zero position is inserted at the beginning of the
array points by the firmware. As far as I know there is no way to stop
this happening. The only way to get round this is to use reletive
positioning and keep track of the current position.
Regards
Jon B
Applications Engineer
NIUK

Formatting Failed Error - Break Point Error

I have a large project I'm trying to burn on a dual layer dvd. I keep getting the following error:
Formatting was not successful. A suitable marker could not be found in the required layer break range. See the DVD Studio Pro User's Manual for more info.
Well I did that and tried to move the break point marker to where I thought the break may occur according to the VTS outline view. I usually use automatic for this but it's not working this time.
Any suggestion would be greatly appreciated. Thanks for your time.

When you prepare to Format the disk: Look at the Disc/Volume tab: Dual-Layer Break Point drop down menu.
Are any of the chapter markers in the middle tracks visible in black (ie not greyed out)? If so select a suitable one of these and you should be OK. If they are all greyed out then you need to create a chapter marker in an area of the movie that should be at about the mid point of the movie. Try to select a point where a slight pause would not be distracting.

How many break points and watchpoints are allowed in ECC 6.0

Hi,
Can any one say how many break points and watchpoints are allowed in ECC 6.0

Hi ,
A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.Max 30 breakpoints we can use.
There is a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change ie...Watchpoints allow you the option of monitoring the content of individual variables.The Debugger stops as soon as the value of the monitored variable changes.You can use max of 5 watchpoints.
Difference
1. Break Point.
At particular LINE of SOURCE CODE,
the system will STOP there.
2. Watch Point.
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
(For this, we have to give some
VARIABLE NAME & VARIABLE VALUE - with relational operator)
When this CONDITION gets satisfied,
(anywhere during the execution of the program),
the system will AUTOMATICALLY STOP THERE.
(EG when the value of matnr reaches the specified value)
That is the purpose of WATCHPOINT
(the system will WATCH it, like a dog)
Please go through this link:
Watchpoint Vs breakpoint
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger. Watchpoints allow you the option of monitoring the content of individual variables.
The Debugger stops as soon as the value of the monitored variable changes.
In addition, conditions can be specified. The Debugger also checks whether such a condition is fulfilled.
For more details...
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cd9e68c11d2b2ab080009b43351/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/f1/792442db42e22ce10000000a1550b0/frameset.htm
If satisfied, rewards me..
Kind Regards
Yogesh

DL Break Point error.. please help!

Hi All,
I have a really big DSP4 projects with a 78 min feature, and about 15 more 2-5min clips. For some reason, I am having a really hard time setting a break point.
If I choose automatic break, I get:
"Formatting was not successful. A suitable marker could not be found in the required layer break range. See the DVD Studio Pro User's Manual for more information."
...and if I set the breakpoint myself, I get:
"Formatting was not successful. Layer 0 exceeds the maximum layer size allowed. Please choose a suitable marker location that will support this condition."
Please help me out!

Hi, I definitely understand what you are going trough, I spent a whole week trying to find the brake point, after reviewing my tutorial I realized wherre the problem was. Devide the total lenght of the movie by 2 and then add about 5 to 10% to the 50%, than start adding markers on the timeline close together, you are allowed 99 markers, hilight each marker after being used so that you can keep track, if you are reaching the disc limit, than you may be limited to a few choises.I hope this works for you.
G5 Dual 2.0 Mac OS X (10.4.4) ATI 9800 Pro Display Card
G5 Dual 2.0 Mac OS X (10.4.4) ATI 9800 Pro Display Card

Time interval for contoured move

I have a interpolator and it output the interpolated data with time interval 1ms. When I do the experiment using stepper motor controlled by 7344 (contoured move). the time interval is much bigger the 1ms, resulting in very low velocity. How to solve this problem? Increasing the time interval of interpolator? Is there anyone has any ideas? Thanks a lot!

In contouring mode you can set the time interval for the position buffer in the Configure Buffer function. Here is the parameter description:
Requested Interval (10 ms) is additional data for the Position
buffer type. The Position buffer type requires a Requested Interval parameter,
and indicates the time between contouring data points in milliseconds. For all
other buffer types, the Requested Interval parameter is ignored.
The controller uses the closest value it can that is greater than
or equal to the interval value you requested. Your time interval must be an even
multiple of the PID rate. Refer to the description for the Actual
Interval parameter for more information.
When used with Breakpoint or High-Speed
Capture, Requested Interval indicates how often, in
milliseconds, the onboard data is updated from the hardware, and the value is a
whole number.Please note that 10 ms is the fastest interval that you can set. If your data is sampled with a 1 ms time interval and you want to use the 10 ms time interval with your 7344 you simply should decimate your contouring data array by copying every 10th value to your contouring position array.
Best regards,
Jochen Klier
National Instruments Germany

Break Points during Contour Move

Similar Messages

Maybe you are looking for