Shared Folder Between KRC4 and PC

check the following things:

-C and D partitions on robot are shared.
-you are able to ping the robot from the pc. "edit: didn't see you could already ping the robot "

kind regards,
NoMad

Sharing folder is a windows functionality and it has nothing to do with KSS version

It requires not just functional network connection but also security credentials (user name and password)

That means same user account must exist on both machines (KRC and PC), or you need to use different credentials (username and password of accepted by machine that shares folder).

When you attempt to access the robot shared folder from the PC, do you get a request for Username and Password?

Sharing the C drive with Write access is a bad idea. Also, attempting to write KRL modules directly to /KRC/R1/Programs is generally a bad idea -- you'll run into conflicts between the HDD and the RAM drive. Best method is to share a unique folder (I usually create one on the D drive, with read/write access, specifically for this) to the network, then on the SmartPad, manually copy&paste the KRL modules from the shared folder into /R1/Programs. This forces a compile/link cycle, and avoids HDD/RAMdrive issues.

are you sure you are on a same subnet?
are you sure you have needed rights and services?

here is the basics:

1. on a controller log in as Expert
2. while logged in, minimize HMI
3. open Computer and right-click on D:\ and check properties - if drive is shared, with who and what access rights are given. if needed adjust them. this window will give you EXACT info to type into your PC to connect to shared folder
4. bring back HMI and note down Network settings for Windows interface. default is 172.31.1.147, 255.255.0.0
5. on your laptop make sure network settings match those of KRC, for example set your network interface to 172.31.1.148, 255.255.0.0. ping KRC to verify connection
6. open windows explorer and click on Computer, that will show all drives and in menu make Map network drive visible
7. pick unused drive letter such as W: and as folder enter shared link from KRC (see step 3) or enter path using format "\\machine\folder_name", for example \\172.31.1.147\d (it is acceptable to use either machine name or IP address) BUT make sure here to place checkmark on "Connect using different credentials" or you may not see prompt to enter user name and password. depending on windows and KSS version, user name and password may differ. on KRC4 usualy user name is KukaUser and password is 68kuka1secpw59

hello, did you you fix the problem?

Quote from panic mode

are you sure you are on a same subnet?
are you sure you have needed rights and services?

here is the basics:

1. on a controller log in as Expert
2. while logged in, minimize HMI
3. open Computer and right-click on D:\ and check properties - if drive is shared, with who and what access rights are given. if needed adjust them. this window will give you EXACT info to type into your PC to connect to shared folder
4. bring back HMI and note down Network settings for Windows interface. default is 172.31.1.147, 255.255.0.0
5. on your laptop make sure network settings match those of KRC, for example set your network interface to 172.31.1.148, 255.255.0.0. ping KRC to verify connection
6. open windows explorer and click on Computer, that will show all drives and in menu make Map network drive visible
7. pick unused drive letter such as W: and as folder enter shared link from KRC (see step 3) or enter path using format "\\machine\folder_name", for example \\172.31.1.147\d (it is acceptable to use either machine name or IP address) BUT make sure here to place checkmark on "Connect using different credentials" or you may not see prompt to enter user name and password. depending on windows and KSS version, user name and password may differ. on KRC4 usualy user name is KukaUser and password is 68kuka1secpw59

Display More

Hey panic mode,

is it possible to put some characters (%d) in the path to obtain a folder containing the current date in its name, for example 220528 or 20220528, tomorrow 220529, and so on?

Quote from panic mode

are you sure you are on a same subnet?
are you sure you have needed rights and services?

here is the basics:

1. on a controller log in as Expert
2. while logged in, minimize HMI
3. open Computer and right-click on D:\ and check properties - if drive is shared, with who and what access rights are given. if needed adjust them. this window will give you EXACT info to type into your PC to connect to shared folder
4. bring back HMI and note down Network settings for Windows interface. default is 172.31.1.147, 255.255.0.0
5. on your laptop make sure network settings match those of KRC, for example set your network interface to 172.31.1.148, 255.255.0.0. ping KRC to verify connection
6. open windows explorer and click on Computer, that will show all drives and in menu make Map network drive visible
7. pick unused drive letter such as W: and as folder enter shared link from KRC (see step 3) or enter path using format "\\machine\folder_name", for example \\172.31.1.147\d (it is acceptable to use either machine name or IP address) BUT make sure here to place checkmark on "Connect using different credentials" or you may not see prompt to enter user name and password. depending on windows and KSS version, user name and password may differ. on KRC4 usualy user name is KukaUser and password is 68kuka1secpw59

Display More

Can we do it other way around? Have a folder from my laptop mapped inside kuka environment?

what do you think?

Quote from asharma7

Can we do it other way around? Have a folder from my laptop mapped inside kuka environment?

Yes, it's possible. But the mapping must be done using the CWRITE KRL_MOUNT command, and have the password hash generated with the khash.exe program in the robot's UTIL directory. The details are in the CREAD/CWRITE manual.

using CWRITE KRL_MOUNT is only needed if files in shared folder are accessed by CWRITE.

for other uses that is not needed (archiving, accessing files using windows or smartHMI etc.).

Quote from gol.one

is it possible to put some characters (%d) in the path to obtain a folder containing the current date in its name, for example 220528 or 20220528, tomorrow 220529, and so on?

i am sure there is a way and if not one can make it that way using suitable tool or simple script.

perhaps something like

MKDIR %date:~-4,4%%date:~-10,2%%date:~-7,2%
SUBST V: /D
SUBST V: %date:~-4,4%%date:~-10,2%%date:~-7,2%

first line creates folder with that name

third line makes that folder appear as drive V:

second line removes previous substitution for V:

so if one puts this into a script (CMD or BAT) and run it ever day, then new folder would be created every day and current day folder would be always appearing as V: and thus giving you fixed path

and if you prefer YYYY-MM-DD instead of YYYYMMDD try

MKDIR %date:~-4,4%"-"%date:~-10,2%"-"%date:~-7,2%
SUBST V: /D
SUBST V: %date:~-4,4%"-"%date:~-10,2%"-"%date:~-7,2%

Quote from SkyeFire

Yes, it's possible. But the mapping must be done using the CWRITE KRL_MOUNT command, and have the password hash generated with the khash.exe program in the robot's UTIL directory. The details are in the CREAD/CWRITE manual.

I was able to map a folder from my local pc to the controller and did a "Map to Drive". I was able to see my Z drive (the folder was in z drive) on my Teach Pendant. It works but is it the right way?

Quote from asharma7

I was able to map a folder from my local pc to the controller and did a "Map to Drive". I was able to see my Z drive (the folder was in z drive) on my Teach Pendant. It works but is it the right way?

Yes, if you're only working in the Windows side of the robot -- say, for pushing backups to a remote network share, or importing program modules from the remote share.

However, as far as I know, this does not make the Z drive available to the VxWorks/KSS side of the robot. That is, you will not be able to access the Z drive from inside a robot program. That still requires the KRL_MOUNT command.

So it depends on what you're trying to do.

Quote from SkyeFire

When you attempt to access the robot shared folder from the PC, do you get a request for Username and Password?

Sharing the C drive with Write access is a bad idea. Also, attempting to write KRL modules directly to /KRC/R1/Programs is generally a bad idea -- you'll run into conflicts between the HDD and the RAM drive. Best method is to share a unique folder (I usually create one on the D drive, with read/write access, specifically for this) to the network, then on the SmartPad, manually copy&paste the KRL modules from the shared folder into /R1/Programs. This forces a compile/link cycle, and avoids HDD/RAMdrive issues.

Hi all,
I come to the same conclusion, but I want customers, easily run the program from HMI (industrial PC).
Any solution to transfer directly /KRC/R1/Programs without conflict. Or another solution?

Src and Dat are transferred, but not accepted as modules without restarting the robot.

Tnx

Thats because they need to be downloaded into VxWorks to be able to use them with the robot.. Putting them on your harddisk only makes them visible for Windows side of your controller. At startup files get downloaded from Windows into VxWorks.

Another option is copying them onto a shared folder and then using the KUKA HMI to copy them into the R1 directory you see on the HMI. This HMI folder basically shows the file system inside VxWorks. Using the KUKA HMI the copy copies from Windows to VxWorks.

A third option is to buy sofware like directory loader from KUKA. It essentially does the same (copy from Windows to VxWorks) but can be used without end user interaction.

Fubini

Quote from robot_programmer

Any solution to transfer directly /KRC/R1/Programs without conflict. Or another solution?

No. Only the DirLoader option from KUKA can do this.

Quote from robot_programmer

Src and Dat are transferred, but not accepted as modules without restarting the robot.

That's because the robot does not run from the hard drive.

During boot, all the operating files are loaded from the HDD into a RAM drive. Compiling and liking takes place at this time (it's why the boot time is rather long). After boot is complete, the KSS side of the robot's brain runs only off the RAM drive. This is a deliberate decision by KUKA both for speed, and to insulate the running code from any potential issues on the HDD. KSS periodically saves the contents of the RAM drive back to the HDD.

This leads to a situation where someone could tamper with programs on the HDD (if the C drive was made remotely writeable, for example) while the robot is running, and have no effect -- in fact, the next auto-save would "fix" any tampering.

Ironically, the Windows side of the KRC is not so protected, so an intruder with write access to C: could potentially BSOD the robot by tampering with Windows files. But it's not possible to make alterations to robot program code, and have those changes take effect, without either using the DirLoader option, or rebooting the robot. And due to the periodic save from the RAM drive to the HDD, using the reboot method is unreliable.