It s possible to run to sub programs at same time ?
I have a routine that have a waituntil to wait a a signal.
And the robot is stop, but i want to move the robot to make another task.
Its possible ?
It s possible to run to sub programs at same time ?
I have a routine that have a waituntil to wait a a signal.
And the robot is stop, but i want to move the robot to make another task.
Its possible ?
The Multitasking option enables this functionality. However, depending on the specifics of what you are wanting to do, it could also be achieved in a single task, I believe.
Instead of WaitUntil "Signal" = 1
could this work?
WHILE "Signal" = 0 DO
OtherStuff;
ENDWHILE
The multitasking is not from base ?
I have the menu MULTITASKING but its blank
Its possible to install multitasking without format the robot ?
What do you mean when you say you have the menu MULTITASKING?
It s possible to run to sub programs at same time ?I have a routine that have a waituntil to wait a a signal.
And the robot is stop, but i want to move the robot to make another task.Its possible ?
Interrupts would be another option - depending on what the robot is doing in the meantime.
In the IPL2 i have multitasking but is all blank.
what is FactoryWare interface ??
DISK
3HAB2396-1/21 System Key 3.1
Serial no 14-11037
Included options:
1400
No Ext Axes
512 BaseWare OS Plus
530 Advanced Functions
534 FactoryWare interface
575 English
FactoryWare is an option for communication with a "Server" for statistics / monitoring etc. it's the predecessor of "the cloud" if you will (see full description below).
Like others have mentioned earlier, multi-tasking is generally used when you want the robot to run a completely separate task (logic only, no motion in background tasks)
and act kinda like a PLC... TRAPS (interrupts) are useful when you want to trigger on events, e.g. generate errors on loss of vacuum etc.
What does teh signal do that you're waiting for and what would you like to do while the robot moves ?
//M
Quote from FactoryWare InterfaceDisplay More
[size=6pt]This option enables the robot system to communicate with a PC using RobComm 3.0
or later versions (see FactoryWare). The FactoryWare Interface 3.2 serves as a runtime
license for RobComm, i.e. the PC does not require any license protection when
executing a RobComm based application. However, when developing such an
application, a hardware lock and password are needed in the PC (design time license).
Older versions of RobComm will require RAP Communication in the robot and license
protection in the PC (hardware lock and password for design and run-time, or only
password for only run-time).
This option will also work with RobView 3.2/1 or DDE Server 2.3/1 (or later versions).
Older versions work only with RAP Communication. In all cases RobView and DDE
Server will require the hardware lock and password.
The Factory Ware Interface 3.2 includes the Robot Application Protocol (RAP), based
on MMS functionality. The Robot Application Protocol is used for computer
communication. The following functions are supported:
- Start and stop program execution
- Transfer programs to/from the robot
- Transfer system parameters to/from the robot
- Transfer files to/from the robot
- Read the robot status
- Read and write data
- Read and write output signals
- Read input signals
- Read error messages
- Change robot mode
- Read logs
RAP communication is available both for serial links and network, as illustrated by the
figure below.[/size]