# MoveLSync without stopping **URL:** \ **Category:** RAPID Programming\ **Created:** [December 18, 2020, 6:37pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882 "2020-12-18T18:37:08Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![xerim](https://avatars.discourse-cdn.com/v4/letter/x/2bfe46/32.png) [@xerim](https://tech-community.robotics.abb.com/u/xerim)\ **Post date:** [December 18, 2020, 6:37pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/1 "2020-12-18T18:37:08Z")
Hello, I am trying to use MoveLSync without the robot stopping, however when the robot reaches the robtarget specified in my MoveLSync instruction, the motion stops as the program pointer has jumped to the other proc. How can I execute this without the robot stopping once it reaches the target? Thanks ---
**Author:** ![davidmalott](https://avatars.discourse-cdn.com/v4/letter/d/58956e/32.png) [@davidmalott](https://tech-community.robotics.abb.com/u/davidmalott)\ **Post date:** [December 21, 2020, 8:37am UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/2 "2020-12-21T08:37:54Z")
The procedure called within MoveLSync needs to complete itself first before the PP return to the the next instruction line, so it depends what you are trying to do. ---
**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\ **Post date:** [December 21, 2020, 1:00pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/3 "2020-12-21T13:00:06Z")
How big a zone have you defined? Is there a whole lot of code in the routine? Especially, any waiting for a DI or condition? ---
**Author:** ![xerim](https://avatars.discourse-cdn.com/v4/letter/x/2bfe46/32.png) [@xerim](https://tech-community.robotics.abb.com/u/xerim)\ **Post date:** [December 21, 2020, 1:22pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/4 "2020-12-21T13:22:51Z")
> [@lemster68](#): > > How big a zone have you defined? Is there a whole lot of code in the routine? Especially, any waiting for a DI or condition? The zone is relatively big (100mm), but the proc the MoveLSync calls does contain many WaitUntil instructions. Essentially I have a routine that prepares a tool for work, and a turn table that runs on a stepper motor and uses limit switches to get positional information. What I am trying to do is trigger the table turning to the correct limit switch while the tool is being prepared simultaneously. ---
**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\ **Post date:** [December 21, 2020, 2:32pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/5 "2020-12-21T14:32:17Z")
So I suppose in your motion event log you will see a corner path failure warning identifying this line number. ---
**Author:** ![xerim](https://avatars.discourse-cdn.com/v4/letter/x/2bfe46/32.png) [@xerim](https://tech-community.robotics.abb.com/u/xerim)\ **Post date:** [December 21, 2020, 2:41pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/6 "2020-12-21T14:41:46Z")
No corner path failure present in the motion event log ---
**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\ **Post date:** [December 21, 2020, 3:26pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/7 "2020-12-21T15:26:12Z")
None, whatsoever? There is a parameter to turn that off, though. ---
**Author:** ![xerim](https://avatars.discourse-cdn.com/v4/letter/x/2bfe46/32.png) [@xerim](https://tech-community.robotics.abb.com/u/xerim)\ **Post date:** [December 21, 2020, 3:30pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/8 "2020-12-21T15:30:29Z")
I mean there is one, but not for my MoveLSync instruction, but for when the robot returns to the home position at the end of the procedure. ---
**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\ **Post date:** [December 21, 2020, 3:45pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/9 "2020-12-21T15:45:53Z")
Hmmmm, I would expect that it would flag the warning if it is stopping. Do you have multitasking? Or, can you get things prepared sooner, like when robot completes one task and is moving away? Perhaps break it up into smaller procs. ---
**Author:** ![xerim](https://avatars.discourse-cdn.com/v4/letter/x/2bfe46/32.png) [@xerim](https://tech-community.robotics.abb.com/u/xerim)\ **Post date:** [December 21, 2020, 6:12pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/10 "2020-12-21T18:12:26Z")
Breaking up into smaller procs isn’t a bad idea, I don’t have multitasking but it would be ideal for an application like this. The biggest obstacle I am facing right now is the procs for turning the table all depend on WaitUntil commands that are fulfilled by limit switches triggering at certain positions. Is there a way to have a proc running in the background without multitasking? ---
**Author:** ![lemster68](https://dub1.discourse-cdn.com/flex005/user_avatar/tech-community.robotics.abb.com/lemster68/32/1945_2.png) [@lemster68](https://tech-community.robotics.abb.com/u/lemster68)\ **Post date:** [December 21, 2020, 6:26pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/11 "2020-12-21T18:26:43Z")
No, not really. ---
**Author:** ![MattB](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@MattB](https://tech-community.robotics.abb.com/u/MattB)\ **Post date:** [December 29, 2020, 1:10pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/12 "2020-12-29T13:10:04Z")
You can try to use \Conc parameter to execute some code in background while robot is moving. To be able to use it you have to use MoveL/MoveJ command. ---
**Author:** ![xerim](https://avatars.discourse-cdn.com/v4/letter/x/2bfe46/32.png) [@xerim](https://tech-community.robotics.abb.com/u/xerim)\ **Post date:** [January 4, 2021, 1:22pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/13 "2021-01-04T13:22:38Z")
> [@MattB](#): > > You can try to use \Conc parameter to execute some code in background while robot is moving. To be able to use it you have to use MoveL/MoveJ command. Does \Conc take a proc as an argument though? I need to trigger an entirely different proc while another one is already executing. ---
**Author:** ![MattB](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@MattB](https://tech-community.robotics.abb.com/u/MattB)\ **Post date:** [January 4, 2021, 11:42pm UTC](https://tech-community.robotics.abb.com/t/movelsync-without-stopping/9882/14 "2021-01-04T23:42:16Z")
No, it’s not possible to use an argument. If you use \Conc in move instruction program pointer will jump to the next line and start command or proc instantly without waiting for robot to reach a corner zone.