1. Password Mode for PLC integration. - We would benefit a lot from having a pre-made mode for the password option wherein an identification signal and a login signal could be configured such that a thumbprint scanner could be used, run through the PLC and specific users be logged in to the robot at specific levels. Right now, the existing implementation makes it difficult if not impossible to log in via PLC with different levels.

2. Limit jogging to Cartesian coordinates with no w/p/r component without forcing the user into JGFRM. Would like to be able to force operator to work in TOOL frame but only use x/y/z, no w/p/r. Better granularity on jogging options.

3. Easier setup duplication, simple file to transfer between robots that can immediately set up User Names and Passwords. Include in the XML for level definition?

ASCII upload should be free. This used to be a free option in the RJ3iB days, but now Fanuc charges for it. Same with Karel.

A zero percent speed. Abb's have this and it is very useful to stop the program without abort it, or having to reissue start commands.

Customizable jog step increments. I know I can change the fine move step, but that is buried in the system variables.

Ability to return a value from a TP program. Also the ability to check if an argument passed to a TP program exists.

Ability to set a string register directly. There is a way to do it via arguments into a subprogram, but it is janky. More modern string manipulation in general.

Ability to write to the TP error line without Karel.

Ability to pass a string register to the MESSAGE comment.

Advanced math without an option.

Some form of IDE for working on a robot on the floor. Ability to see where the robot is, what line it is on, what it is waiting for, set breakpoints (including logic driven break points (i.e. break on this line when DI[4]=ON)), set step mode, set variable watches, etc. See Abb's robot studio for a very well done example.

Get rid of archaic registers and implement user named variables, arrays, and data structures. All user created variables should be able to be monitored on the data screen in alphabetic order, or a filtered view.

Something like ABB's Robot Studio would indeed be nice. To be able to plug into a robot and see everything it is doing, control it from the software, pull backups, and write and revise programs is a powerful tool. Not to mention that the limited free version has no time limit.

I have tested it. It is a good step in the right direction but needs further development. Currently it is only available for Scara robots.

Fun little trick with this one; you can create an empty SCARA cell, log into the iRProgrammer via your browser, build the programs, save them using a file back up, then copy the .TP files to another controller/workcell (as long as there are no SCARA specific commands or commands relying on software packages not present on both controllers).

I've found this to be useful when I'm in the psuedocode stage of programming as it's a bit cumbersome to go through the whole process for just one or two programs; I also agree that the iRProgrammer is a huge step up but also very, very wonky at times. If they stopped iRProgrammer from compiling, throwing errors, and locking down any keyboard progress after every line entry, I'd be much, much happier with it.

If the robot is in Teach and the Fence Circuit is closed, T2 is active, if the robot is in Teach and the Fence Circuit is open, T1 is active. Allows a person to safely operate the robot at full speed from the teach pendant if and only if the cell is closed and in a safe production state. Otherwise, speed is limited. We have entirely switched to two mode switches to prevent any risk of injury caused by T2 speeds, this would be a big improvement for us.

If the robot is in Teach and the Fence Circuit is closed, T2 is active, if the robot is in Teach and the Fence Circuit is open, T1 is active. Allows a person to safely operate the robot at full speed from the teach pendant if and only if the cell is closed and in a safe production state. Otherwise, speed is limited. We have entirely switched to two mode switches to prevent any risk of injury caused by T2 speeds, this would be a big improvement for us.

We use DCS to control what I believe you're requesting. Is this what you're looking for?

2. Dynamic memory allocation and pointers in KAREL. Actually, I'd probably be okay with just support for data structures other than statically sized arrays and structs (Vectors/ArrayLists, maps, etc).

3. More ways to transform position datatypes, particularly relating to orientation.

4. Termination type to move through point without stopping slowing down. I know they are working on a package that might do this, but from what I've heard it'll be pretty restrictive and prone to throwing errors.

5. Ability to read safety IO directly, instead of having to map safety IO to regular IO and then reading that.

I got used to Fanuc robot, however they are like from 90's with their software (for example UR are more modern to use) but I wish to have new thing in Roboguide which makes me angry. In roboguide you can't zoom objects in other ways, there's just magnifier but the moving with camera (f.e. between objects!) is missing. WHY? That thing is in every 3D program like Blender, Catia, Pro engineer etc.. So if you have some big object before the other, you can't see the other because you can't move with camera between them.

As a newcomer to Fanuc, I think Fanuc should up their game regarding customer support as I have found most answers and assistance has been more proactive here at Robot Forum than Fanuc's responses.

Maybe Fanuc could apply some affiliation towards Robot Forum in the future perhaps?

A big shout out to all those here at Robot Forum in the Fanuc boards, as a newbie and after going through the STPP and DCS training at Fanuc, you guys/gals are providing the 'missing gear' the makes the whole thing turn.

Keep up the good work...………

If you find members information useful don't forget to provide a reaction to show your appreciation

Get rid of archaic registers and implement user named variables, arrays, and data structures. All user created variables should be able to be monitored on the data screen in alphabetic order, or a filtered view.

Not get rid of it but add alternative. This is one of the best things that the people I train praise by comparison to ABB or MOTOMAN.