Wait a minute. You are aware that the PNS inputs are binary. So to run PNS0005 you would have both the 1st and 3rd Input on.
In the PLC you should create a SINT tag and then copy those bits into the 8 Pns inputs.
Wait a minute. You are aware that the PNS inputs are binary. So to run PNS0005 you would have both the 1st and 3rd Input on.
In the PLC you should create a SINT tag and then copy those bits into the 8 Pns inputs.
Send a copy of the programs. Maybe send one that is working and the one that isn't and we can see what is different. Please send the .ls version.
That's cool, I haven't heard of the integrated laser yet.
Personally, I wish they would get rid of all the separate core Tool software versions. Just create 1 core software, FanucTool and create options for each of the different specialty applications. Maybe you get 1 free option package when you purchase a new robot.
Think about a PLC. It's not like you get different software when you do a different application. You just program it to do whatever you want and have a single common development environment.
ENET isn't a thing on Fanuc robots. EthernetIP is a thing.
Are you actually using the EthernetIP protocol with a PLC? Have you purchased the EthernetIP adapter or scanner option and installed it on the robot? If so please list what model of PLC you are using and what model of robot controller.
I think your only option is to run that Karel program at startup and have a continuous loop, just like a BG logic program, but with a time delay so it doesn't bog down the cpu.
Then in each loop check if the signal is on to decide if you run your logic. Use one shot logic to trigger it only once.
In psuedocode:
While true
If trigger = on and running = off then
Do stuff
End if
Running = trigger
Time delay
End while
I would be hesitant to do so. I do much the same thing as you describe (repo, ftp, setup program) for quick setup and payload is always manual unfortunately.
My guess is that it would be ok if the robots are identical in model, controller, software version, and options.
As always, take an image backup first before you try.
No, you have to have a copy of the original software media. On newer robots it is on a USB drive, on older compact flash, on even only floppy.
Call a TP program with an argument for the UALM number. The TP program would have 1 line of code.
:. UALM[AR[1]];
On the newer controllers, R30ib+, you can have multiple snap tools in 1 vision process. On older models you may have to setup multiple tools or processes to do that.
What is your grid size? Another option is to create several medium size windows and then sort the results.
You can increase the number found and then sort the results by x and Y value. Or you can change the search window.
I think you will have to get the correct software from Fanuc, which will cost some money.
Maybe you are some kind of controls wizard, I don't know, but I have a hard time believing that you will be successful converting the controls. Best bet is to get the correct software or buy a robot that is actually functional.
That is strange. I use Other mode with all UI/O signals configured and have no issues.
On LR Mate it is under Start mode in the function menu. It doesn't cycle power for you but sets the next start mode option.
Menu>Setup>Host Comm>TCP/IP
The look at the value under Board address.
Each port will have it's own mac address, so you can press the F-key for port toggle between them and find the one you need.
You are right that it requires a power cycle to change the program select method. But when I do that it stays with whatever selection I have made.
So I assume you are setting select method = other and start method = UOP. Then if you highlight the select method and press 'F3' detail you have to select your main program.
Are you then rebooting with a cold start? If you are doing a hot start, I'm not sure it will take effect. Make sure you press function>cycle power>Option> cold start first, then cycle power.
Do you know how to use the Search tool on the web browser? Basically go to that robots IP address, select search tool at the bottom, then search for that variable name in all the programs.
That variable normally can be changed anytime and would stay put unless someone or a program changes it. Does it work right away after you change it?
Maybe a background program is setting it through the system variable.
$SHELL_CFG.$SEL_TYPE
See if you can find that variable being set in any programs or BG logic and if so take it out.
So if I understand correctly, you want to rotate around the tool Z axis, but have that axis offset from the center of the faceplate.
It should be as simple as setting an X or Y value for the tool frame. If it drifts in x or Y while rotating only the R angle then you must use trial and error to adjust the tool frame until it is correct.
The only way to determine if it is a mastering issue is to mount a solid, sharp pointer, teach a 3 point method, and see if you can rotate on point.
Sounds like You're getting closer. You need to use the 3 point method to teach your tcp using a pointer. Don't expect it to be accurate just using direct entry.
Send me 1 of the programs and I will try to compile it.