Call Fanuc tell them what you need and they will set you up with a bracketed harness that has the proper I/o cables and a tech to install it. That's your best option.
You run cables thru the harness yourself you're asking for trouble.
Call Fanuc tell them what you need and they will set you up with a bracketed harness that has the proper I/o cables and a tech to install it. That's your best option.
You run cables thru the harness yourself you're asking for trouble.
If you're trying to access the homepage thru the same i.p. address your plc is using it's likely not going to work well or not at all.
You should be on a separate network using different port.
Why not just open the .ls files with notepad++
Never had any luck with virtual machine. However dosbox works or a 32 bit OS. None of this will work in roboguide.
Did you actually teach a tool frame and what did you teach it too?
Normally ( depends on what you're doing) the approach position is the same position as a pick position whatever PR[30] is. You apply another offset such as tool offset or offset pr to it in addition to the VR offset.
They work in windows 7 32bit in command prompt
You are probably getting a pulse mismatch error because a brake is slipping. This error does not require calibration just a reset from the mastering screen.
TP files are compatible across platforms as long as what's in the program (options) is actually installed.
Does this robot have interference zones or space function?
I believe what you want is done through IRprogrammer
Your search program needs to taught in a user to your liking. If it's active it will search accordingly to active frame.
You'll need the DOS programs and a 32 bit os type the command ktrans filename.kl
Compile the source code with version 3
From a maintenance perspective it's not a good idea. I've done repairs and restored controllers after replacing a CPU. This is where the problem comes. How am I supposed to know it was mastered 90 degrees off? Most of the time end user doesn't have their software or backups. It's frustrating and depending on who does the repair will depend on how long it takes to figure out someone decided to master 90 degrees off. It's happened to me many times. The end user throws a fit at the repair guy and it's not even his fault. Like he has some crystal ball in his tool box.
I forgot to add why I did the mastering on the fly. It was to prevent unwinding. So for example if I start at zero degree the motor would have to return to zero(unwind). The threading operation wasn't consistent and never knew how much the motor would have to turn. So the easiest thing to do was just remaster it. This saved cycle time because there was unthreading done first.Completed part removed new part added.
This was interesting, please do tell how you did to accomplish this.
/PROG MST_AUX1
/ATTR
OWNER = MNEDITOR;
COMMENT = "MASTERS G2 A1";
PROG_SIZE = 418;
CREATE = DATE 08-04-24 TIME 05:24:24;
MODIFIED = DATE 08-04-30 TIME 03:29:32;
FILE_NAME = ;
VERSION = 0;
LINE_COUNT = 7;
MEMORY_SIZE = 798;
PROTECT = READ_WRITE;
TCD: STACK_SIZE = 0,
TASK_PRIORITY = 50,
TIME_SLICE = 0,
BUSY_LAMP_OFF = 0,
ABORT_REQUEST = 0,
PAUSE_REQUEST = 0;
DEFAULT_GROUP = *,1,*,*,*,*,*;
CONTROL_CODE = 00000000 00000000;
/MN
1: WAIT $MOR_GRP[2].$FILTER_EMPT=1 AND $MOR_GRP[2].$CARTFLTREMP=1 ;
2: R[3:FINGER NUMBER]=($MOR_GRP[2].$MACHINE_PLS[1]) ;
3: $MCR_GRP[2].$CALIBRATE=1 ;
4: $DMR_GRP[2].$MASTER_COUN[1]=R[3:FINGER NUMBER] ;
5: ;
6: !WAIT FOR COMPLETION ;
7: WAIT ($MCR_GRP[2].$CALIBRATE=1) ;
/POS
/END
depending on the group the number in the bracket will change.
This example is group 2 axis 1
/PROG MST_AUX2
/ATTR
OWNER = MNEDITOR;
COMMENT = "MASTERS AUX G3A1";
PROG_SIZE = 460;
CREATE = DATE 08-05-02 TIME 04:30:38;
MODIFIED = DATE 08-05-02 TIME 04:31:28;
FILE_NAME = MST_AUX1;
VERSION = 0;
LINE_COUNT = 7;
MEMORY_SIZE = 840;
PROTECT = READ_WRITE;
TCD: STACK_SIZE = 0,
TASK_PRIORITY = 50,
TIME_SLICE = 0,
BUSY_LAMP_OFF = 0,
ABORT_REQUEST = 0,
PAUSE_REQUEST = 0;
DEFAULT_GROUP = *,*,*,*,*,*,*;
CONTROL_CODE = 00000000 00000000;
/APPL
/MN
1: WAIT $MOR_GRP[3].$FILTER_EMPT=1 AND $MOR_GRP[3].$CARTFLTREMP=1 ;
2: R[7:MST AUX1 COUNT]=($MOR_GRP[3].$MACHINE_PLS[1]) ;
3: $MCR_GRP[3].$CALIBRATE=1 ;
4: $DMR_GRP[3].$MASTER_COUN[1]=R[7:MST AUX1 COUNT] ;
5: ;
6: !WAIT FOR COMPLETION ;
7: WAIT ($MCR_GRP[3].$CALIBRATE=1) ;
/POS
/END
group 3 axis 1
Brake power is coming from main amplifier. You are correct that if axis 7 is moving all brakes are disengaged or released. Motor power is holding position.
If you mean master on the fly yes it can be done. I've actually done that with some aux motors that did a threading operation.
That is dual arm option