How do you program Fanuc robots?

None of the above. I program in a text editor then just touch up points on the pendant.

I use a text editor with a built in ftp and roboguide to compile/test programs.

Depending on situation/task I use nearly every method mentioned above, additionally a self programmed tool to manipulate position coordinates.

Quote from HawkME

None of the above. I program in a text editor then just touch up points on the pendant.

please tell us more about it. how can you write a program in a text editor and then load the robot?

Starting out I used the TP, the more confidence I build up now, the more I steer towards:

- text editor.

- load into roboguide for checking/verification and debugging.

I do similar with Kawasaki too, although Fanuc has a better TP teaching facility.

Notepad++, then Roboguide, then real robot.

Notepad++ (or any other text editor) is used to start the project and do the heavy lifting. Scratch, copy, paste, etc. I know Roboguide has an internal (and somewhat hidden) text editor, but I prefer N++ because it is faster.

With the raw program(s) written, is time to upload it to Roboguide and debug. Maybe teach some basic positions, etc.

With these more "mature" programs, is time to upload in the robot itself, touch up the rest of the path and make tests.

But this happens mostly on small projects with single/few robots. Big deployments normally have virtually commissioned OLP programs that in theory are plug and play.

Emphasis on "In theory"...

The best way to start programming with a text editor is to copy some .LS files from an existing robot. .LS files are the text versions of the programs. Then you can see how it is constructed and practice making changes.

Then you need a way to compile/convert the .LS files to .TP files. This can be done with Roboguide, OLPCPro, MakeTp, or Ascii upload.

Quote from HawkME

Then you need a way to compile/convert the .LS files to .TP files. This can be done with Roboguide, OLPCPro, MakeTp, or Ascii upload.

Thanks. INTERESTED EXACTLY THIS

I tried a few times to write my own LS files, but got frustrated with programs not importing, and offering no debug info.

I now usually:

1. create a cell in roboguide with all machine models to verify reachability
2. create a roboguide 'simulation' program that quickly does the 'pick' and 'place' routines. No fancy logic... just checking paths are clear and cycle times, reducer life-expectancy, and overheating.
3. draft my programs with pseudo-code in a text editor (Visual Studio Code). this allows me to make bird's-eye representation of my logic flow
4. rewrite the programs on the virtual TP in roboguide
5. teach all points in roboguide
6. transfer programs and PRs or Ps to the physical robot
7. touch up points

Quote from schnautz

I tried a few times to write my own LS files, but got frustrated with programs not importing, and offering no debug info.

If a program fails to import, there is usually an explanation in the alarm history, along with a line number. Some stuff, particularity involving UFRAME names usually, just craps out and don't give a line number.

Quote from Nation

If a program fails to import, there is usually an explanation in the alarm history, along with a line number. Some stuff, particularity involving UFRAME names usually, just craps out and don't give a line number.

Yeah... I would export an LS file, perform no modifications, and it would fail when re-importing. I can't explain it.

Quote from schnautz

Yeah... I would export an LS file, perform no modifications, and it would fail when re-importing. I can't explain it.

That happens if you don't have a blank line after the /END statement:

pasted-from-clipboard.png

Yes, this is frustrating!

I've never had much issue with MakeTP. Once you get used to typing correct syntax then I rarely have a file that doesn't compile.

fanuc

Quote from massula

Notepad++, then Roboguide, then real robot.

Notepad++ (or any other text editor) is used to start the project and do the heavy lifting. Scratch, copy, paste, etc. I know Roboguide has an internal (and somewhat hidden) text editor, but I prefer N++ because it is faster.

With the raw program(s) written, is time to upload it to Roboguide and debug. Maybe teach some basic positions, etc.

With these more "mature" programs, is time to upload in the robot itself, touch up the rest of the path and make tests.

But this happens mostly on small projects with single/few robots. Big deployments normally have virtually commissioned OLP programs that in theory are plug and play.

Emphasis on "In theory"...

Display More

When using N++ what language coding do you use in order to get the best TP code visibility?

And second issue: which encoding do you use?

Quote from neighbour1

When using N++ what language coding do you use in order to get the best TP code visibility?

And second issue: which encoding do you use?

I use my own syntax highlighting set. With N++ is pretty easy create a new one.

Some years ago I uploaded my .xml file here on the forum.

Re: Off line editor

The current one is different. Simpler, I think. Follows attached.

Regarding the syntax highlight, my biggest concerns are: what is a instruction, what is a comment, and, in FANUC case, what is a commented instruction.

And, about encoding, N++ can handle this very well.

But if You are creating a program from scratch, what You must observer isn't encoding, but line endings. Newer robots normally handle this well, but older robots wants UNIX (LF) line endings.

Programming in text is way faster, but you have to have a good setup. Create templates and common code snippets that you can paste in.

When you reuse templates/snippets then you save a lot of time and also reduce typos.