About to receive my first KUKA robot... setup preparations.

Quote from Koppel

https://amzn.to/2ZOHD4N

Not entirely sure why you bought a manual that you can download for free from KUKA.Xpert...

Quote from Koppel

What do I need to do when I take the robot out of the box it arrives in?

Bolt it down and ensure that all the cables are connected properly. Follow the installation guide, which you will also receive.

Quote from Koppel

Do I absolutely need to perform the Mastering? I do not own the Electronic Mastering Device or a microEMD device

No. The robot will come mastered from the factory, and the Agilus bots have absolute axis encoders, so unless you do something stupid like crashing the robot hard or manually wiping the factory mastering, they should be accurate and not require additional mastering.

Quote from Koppel

I will command the robot externally with a Siemens S7-1500 PLC. At least call out a specific program.
There is a KUKA.PLC mxAutomation function package:
https://support.industry.siemens.com/cs/document/10…?dti=0&lc=en-WW

I am unsure what is the difference between just calling out a KUKA program with a PLC versus doing everything inside the PLC.
What is the recommended way to go for a total beginner

Unless you're prepared to do an extreme amount of work writing a PLC interface program, your best option is to write all the code on the controller and have the PLC select and run programs.
You can either do this with the PLC software options(which will cost you a lot of extra money, since you already bought the robot without them), or you could run the robot in Automatic External mode, in which the digital IO(some of which the robot will have by default) can be used to start/stop the robot and select programs.
This is all described in the programming and system integrator manuals, and all of them are freely available.

Ideally, since you're going head-first into KUKA with a new robot rather than tinkering with restoring an older one, you should take an official KUKA training class, which will teach you all the basics of industrial automation and deploying the robots. It costs money, but it might be worth it.

[size=small]On first power on, software installation is completed (just like when you buy new laptop). This may require one or more reboots.[/size]

[size=small]Device Description Files are usually small files (text or binary) that are created by manufacturer of device (guess where you need to go to get these files). [/size]

[size=2]Type, structure, format and extension for Device Description Files depends on supported fieldbus. Some common file extensions for these files are:[/size]

[size=small]ESI - EtherCat[/size]
[size=2]EDS - DeviceNet, EthernetIP[/size]
[size=2]GSD - ProfiBus (generic)[/size]
[size=2]GSE - ProfiBus (like GSD but only in English language)[/size]
[size=2]GSG - ProfiBus (like GSD but only in German language)[/size]
[size=2]GSDML - ProfiNet[/size]
[size=small]etc.[/size]

[size=2]The main function of Device Description File is to provide information about particular device:[/size]
[size=2] > name, model, manufacturer of device[/size]
[size=2] > file version[/size]
[size=2] > supported capabilities (such as communication modes, communication speeds)[/size]
[size=2] > supported interfaces (type, IO size, addressing options, etc.)[/size]
[size=2] > etc.[/size]

[size=2]This allows various configuration software to integrate and use these devices as building blocks when creating larger, more complex systems. Before Device Description Files can be used by some software, they first need to be integrated into database that is part of that software [/size][size=small]("catalog" or "library" or DTM)[/size][size=small] [/size]

[size=2]WorkVisual is an example of such configuration software. It is meant to configure Kuka controllers (KRC4 and Sunrise).[/size]
[font=verdana, arial, helvetica, sans-serif][size=2]When WorkVisual is installed, bunch of Device Description Files are installed as well. Those devices are grouped into not one but several catalogs (Robot models, Controller parts, Positioners, MGUs, program templates etc.). Another catalog (DTM) is also added to store Device Description Files for everything else (all non-Kuka products) in one place.[/size][/font]

The "Operator Safety" error message means exactly what it says. One of the contact pairs for Operator Safety on the X11 is open.

In T1 mode (and T2, depending on configuration), the robot ignores Operator Safety, but AUT and EXT require it. Losing the E-Stop X11 inputs kills the robot in any mode.

In this case, the "emergency stop" the message refers to is a behavior, not a signal. Op-Safe and E-Stop have the same effect on the robot, it's just that Op-Safe is mode-specific and E-Stop is not.

Op-Safe is intended to be connected to safety gates, area scanners, etc -- devices that keep the contacts closed until someone enters the hazard area. A "button" will not suffice, unless you have someone holding it down all the time.

forum is not a substitute for formal education. take the training before you kill someone.

great, just what the world needed... training cell put together by someone not familiar with what they are doing. do you at least know what standards are applicable in your country?

smartPad will have messages indicating what is going on. The most recent message is on the top of the screen but this is usually not the only one. click on it to switch screen to messages view and find all messages that have red or yellow icon... specially the oldest one.

Startup mode does not work in all scenarios. It allow bypassing safety interface... if one is defined. If you have already attempted to enable safety interface over Ethernet but PLC is not yet configured, make sure to unplug cable going to PLC and make sure to have external enabling switch wired (or equivalent jumper connected to CCU).

On larger controllers, that jumper connector is X311 (00-177-608). On KRC4 compact that would be X403 (jumper plug 00-231-963).