Home Screen
・ | PLC MasterRobo registers, executes, and manages program files and executable files developed with the RBF API as Job Commands. |
・ |
PLC MasterRobo's PC can manage program files developed in Low-Code (RBF API). As long as the file is executable, PLC MasterRobo can manage it. |
・ | Monitor the operating status of multiple IA Robots (RBF Hosts). |
・ |
Monitor the status of the Windows screen of the IA Robot(PC) on the grid network. The status of the Windows screen is to monitor - Windows logon screen - Lock screen - Desktop screen - Remote desktop screen changes. |
・ |
If the program you want to run requires screen display and Windows interaction (UI), you can run the program only when the desktop screen is visible. You can also specify that the executable wait to launch until the desktop screen appears. |
・ |
Up to five relay routes to the IA Robot (Final Destination [Terminal] Host) that you want to execute the program can be set on the screen. |
・ | You can check the end status of execution results in chronological order and number of times. |
・ |
E-mail notification can be sent when the program is executed or terminated, or when the Windows screen changes. |
Run the file on the IA Robot (PC)
Execute the executable file on the IA Robot (PC) from PLC MasterRobo.
・ |
File Existence check You can check in advance whether the file to be run by the IA Robot (PC) exists. |
・ |
File Transfer. You can transfer (upload) the file to be run by the IA Robot (PC) in advance. |
・ |
File Deletion. You can delete files to be executed by the IA Robot (PC) using screen operations. |
Transfer (Upload) files to IA Robot (PC) and Run
Transfer the execution file from PLC MasterRobo to IA Robot (PC) and execute it.
・ |
When it exits after execution, the transferred files are deleted. |
For example, Use when you want to use the IA robot during inactive spare time.
Run in sequence on multiple IA Robots
The same program file/executable file developed with RBF APIs can be executed in sequence to multiple designated IA Robots.
When processing multiple IA robots in parallel, use the RBF API's wait-for-signal function to wait for each IA robot to finish
(1) | Wait for all IA Robots to finish running. |
(2) | When the execution of even one IA Robot is completed, proceed to the next process. |
You can develop a waiting method for parallel processing.
Run of parallel processing from PLC MasterRobo
(1) | Stop processing (Block) until end signal is sent from all IA Robots. |
(2) | Stop processing (Block) until even one end signal is sent from the IA Robot. |
On the RBF Host Status Viewer screen, you can check the overall status of the RBF Host (PC) registered as a monitoring / control target by the color of the Robo icon.
You can instantly change the status of the entire RBF Host (PC).
Also, the names used in the description are used as follows.
Work dependent name : IA Robot
Communication name : RBF Host
Name from App : RBF Server
Robo Icon Color | Explain |
---|---|
Black | The status has not been obtained yet. |
Red | Failed to get the status. Also Windows UI is not a desktop screen, even if RBF mode is running in desktop mode. |
Green | RBF mode is running in service mode. Windows screen operations using the RBF API program are not possible in this mode. It can execute batch programs and so on. |
Blue | The RBF API program is running. |
White | RBF mode is running in desktop mode and Windows UI is the desktop screen. |
The status of the RBF Host (PC) registered in each Robo No. is displayed.
You can check whether a program developed with the Low-Code RBF API can be executed in the current state of Windows.
If your program requires a Windows operation (UI), you need to display the desktop screen.
The color of the Robo icon is the same as above.
[Display of the Top line]
"Robo Group number" + "RBF license number" + "RBF license expiration date"
It is displayed in the order of.
[Display in the second row]
The IP address (FQDN) of the RBF Host to be Final Destination (Terminal) is displayed.
[Display in the bottom row]
The name of the robo number set in "RBF Host Robo Number Setting". Screen is displayed.
[First stage red / green / blue Lamp]
The execution mode set for the RBF Host is displayed.
Display | Explain |
---|---|
Lit Blue Desktop Mode | RBF is set to Desktop mode. |
Lit Green Service Mode | RBF is set to Service mode. |
Lit Red Failed | Failed to get the RBF status. |
No Lighting Disabled | Pause | It is set to Disabled. or Pause. |
[2nd stage red / green / blue Lamp]
The run mode running on the RBF Host is displayed.
Display | Explain |
---|---|
Lit Blue Desktop Mode | RBF is set to Desktop mode. |
Lit Blue Admin Exec | RBF is running in desktop mode with Windows system privileges. |
Lit Green Service Mode | RBF is set to Service mode. |
Lit Red Failed | Failed to get the RBF status. |
No Lighting Disabled | Pause | It is set to Disabled. or Pause. |
[3nd stage red / green / blue Lamp]
The Windows UI status of the RBF Host (PC) is displayed.
Display | Explain |
---|---|
Lit Blue UI Desktop | Currently the Desktop screen. |
Lit Blue UI R Desktop | Currently the Remote Desktop screen. |
Lit Green UI Lock | Currently Windows Lock screen. |
Lit Red UI Logon | Currently the Windows Logon screen. |
Lit Red UI R Logon | Currently the Remote Desktop Logon screen. |
Lit Red Failed | Failed to get the RBF status. |
No Lighting Disabled | Pause | It is set to Disabled. or Pause. |
A program developed with the RBF API is registered as a Job Command, and the number of
Job Command executions (Exec), success (Success), error (Error), and failure (Failed) are displayed in a graph.
Number of executions (white)
The number of attempts to start the program.
Number of success (blue)
The number of times the program returned an exit code for success.
Number of errors (orange)
The number of times the program failed to start.
Number of failures (red)
The number of times the program returned an exit code other than success.
This graph is called a Fish Bone Stack Graph.
In this graph, the area above the centerline is normal and the area below the centerline is abnormal.
You can see at a glance the tendency (amount) of the time zone and date when the abnormality occurred.
The relay route settings to the Final Destination (Terminal) RBF Host can be set in the "Set Communication for RBF Host Robo No. Screen".
Please refer to [
IA Robot APIs Overview
] for Robots Grid Network.
From the above setting screen,
- You can check the existence of files on Robo No.(PC).
- File upload (transfer) to Robo No.(PC).
- File delete on Robo No.(PC).
The Job command registered as a programmed job command developed with the RBF API can be executed by specifying multiple Robo No.
The screen above is a screen to be registered as a job command programmed with the RBF API.
The program can be specified to be run by the specified Robo No.(PC).
- Run the program in MasterRobo PC.
- Transfer the program to Robo No. and Run.
- Run the program located in Robo No.
The program can be executed according to the state of Windows.
Set on the Run Job Command screen.
- Run right now.
- Run at specified date and time.
- Run in time cycle.
- Run in week cycle.
You can set it to restart if the program stops unexpectedly.
The above screen is a screen to register and manage program files and executable files developed by RBF API as job commands.
It is an extension version of the same functionality of RBF Manager.
You can operate it in almost the same way as File Explorer.
Very sorry... The manual is currently in Japanese only. There is no funding to translate that language.
We are looking for business partners to cooperate with us.
Currently Manual site is in Japanese. If you want to display in another language,
Please use the translation function of your browser.