You could map the UOP signals to rack 34, slot 1. That will map the UIs and UOs to flags. You can then connect these flags in your logic. Should even work with RIs (when I remember correctly).
Posts by DS186
-
-
Depending on your controller, I would suggest using the available DI/DO instead of hijacking the EE signals. Check the maintenace manual of the controller for detailed information.
-
Unfortunately I cannot say for certain. Do you have the chance to test with another TP?
In our case we changed the cable with no success and after that, we tried with another TP. The other TP worked without problems.
-
Yes and no. I get where you're coming from and weighed a few things before posting.
Any safety device can be bypassed if you know what you are doing. A couple jumper wires can bypass an entire safety system and a gate switch key can be left in a door. Someone can write the DCS Code on the side of the teach pendant or controller and render it useless.
Fanuc can unlock your forgotten DCS Code, but it's going to cost you time and money. A machine builder might chose to not give you the code despite being paid for the job.
Lost DCS Codes have been a problem and folks have been downloading .PC files from unknown sources to solve their problem. I appreciate those that made those .PC files, it's good stuff. In this age of digital ransoms, I wanted to give an option that just about anyone could implement without fear of damaging their robot.
Later,
00Red
I totally agree with you and I really appreciate that you shared this helpful information.
With my post I just wanted to say that I am really surprised about it. Because my expectation was that the code is a bit more hidden or rather protected.
-
Welcome to the forum. I cannot believe that works!
How did you ever figure that out? And more importantly, what other mystical secrets do you know?
This is indeed unbelievable. This easy and obvious way to get the DCS code makes it a bit useless.
-
Hello droth,
S/WORLD, S/USER and S/TOOL allows you to jog the robot linear through singularity points.
-
-
-
You can change it under Controller > Tasks > Main Entry. Search for "main entry" in the system parameters manual for more information.
-
We had the same problem with the TP of a brand new R-30iB Mate Plus controller. We got some advice from Fanuc tech support. In the end, Fanuc have sent us a new TP to fix it.
-
In my opinion the only way to reliably control the force and to get precise values is a force sensor.
Fanuc offers different force sensors, depending on the robot model.
-
-
From version 8.6 and newer you need the option KUKA.RemoteSupportView for a proper RDP connection. This is what KUKA Germany told me and I can confirm that I was never able to connect via RDP with a KSS 8.6 (or newer) controller without having the above option.
For versions older than 8.6 it was always possible to connect with adapting the KLIConfig.xml.
-
No problem. Tomorrow when I have time I will also check one of my backups trying to find out where to find the data and how I managed to get the stuff working.
-
Hey guys,
I have a general question about how you would do the following. Some information in advance:
I am using PROFINET on a R-30iB Plus controller. I normally directly connect the Ethernet port 1 (CD38A) to the physical PROFINET network to be able to remote access the controller over the machine network, e.g.:
IP address PROFINET 172.169.1.10
IP address Ethernet port 1 172.169.1.11
Now I have a Cognex camera communicating over Telnet via Ethernet with the controller.
Would you completely separate the camera network and use another subnet and connect the camera equipment to Ethernet port 2 (CD38B)?
Or would you connect the camera to port 1. In this case, remote access via a PC and communication with the camera would both be managed over port 1 (CD38A), if possible?
How do you normally do such a setup? What is the preferred setup (from your experience)?
Appreciate your help!
-
Hey jrfall,
I had the exact same issue with my last ABB robot (in 2019). When I remember correctly, the solution for me was exporting the IO config (or the SafeMove config?), searched the F-source and F-destination address and changed the values. After that, importing and transferring the config to the controller worked.
-
I normally prefer STYLE instead of PNS due to the possibility of a more descriptive naming convention for the programs.
-
There are many different ways to do that. I normally use the SELECT instruction within my main loop. See here for some ideas on how to do it. This guy creates awesome content on his website.
-
In case of OTHER it will always start the main program set under $SHELL_WRK.$CUST_NAME. You can then create some kind of a job handler inside that main routine to call different programs. To select these subroutines you can e.g. send a number to a GI via the PLC.
-
No problem. And don't forget to make a cold start once you have finished your changes in controlled start mode.