This will export .eds
Posts by Five Taco
-
-
$MOR.$safety_stat from other linked thread should work.
IF $MOR.$safety_stat <> 512 THEN
!safety OR other fault detected
ENDIF
But this will trigger all of the faults listed there. DEADMAN for example...
Or you can try:
512 +
1 MFS_EMGOP
2 MFS_EMGTP
8 MFS_FENCE
64 MFS_EMGEX
IF $MOR.$safety_stat = 513 OR $MOR.$safety_stat = 514 OR $MOR.$safety_stat = 520 OR $MOR.$safety_stat = 576 THEN
!Emergency stop
ENDIF
I'm not sure, if TP E-STOP will trigger EMGEX as it does with DO. Maybe $MOR.$safety_stat = 576 is enough? Need some testing to do
-
Hi,
$E_STOP_DO
$CR_AUTO_DO
$CR_T1_DO
$CR_T2_DO
Those variables are to assign DO to the specific function. Same as SYSTEM > CONFIG.
For mode you can use:
$MSKKEY
1 - T12 - T2
3 - AUTO
It's not clear if you want E-STOP in general or specific button status.
$MOR.$SAFETY_STAT will show different status
robot-forum.com/robotforum/thread/20222-safety-status-variables/ -
Mitsubishi calls it a buzzer. Set TBBZR or BZR parameter to 0
-
Check $LOGBOOK variable group, inside there are specific items that can be enabled/disabled.
In your situation should be $LOG_PRGEXE 0, I think?
Check "Software Reference Manual" or could guess some by the names.
There are variables to set how much space should be left in controller memory after logbook buffer(otherwise buffer is deleted).
$DRAM_MARGIN, $SRAM_MARGIN - kilobytes. But didn't have any need to change it, filtering works fine.
I don't think it resets after power off.
-
Also forgot that alarm history can show you time.
Click on F5 (Detail) on selected alarm. -
There is an alarm "SRVO-012 Power failure recovery", it comes up after hot start.
You could check MENU>ALARM>F3 (HIST) or Motion Log. But keep in mind that this alarm can be out flooded with other alarms during production.
Or you could check LOGBOOK.LS in MD: directory (or make AOA and open with notepad). It would include robot time as well like this.
========================================
Power failure recovery
25-MAR-23 19:58 :36
========================================
It again can be out flooded by other stuff (for example "ENTER is pressed"), but those can be disabled in $LOGBOOK variable group. There is are a lot, but some could be guest like $LOG_UF means UserFrame. Or check the "Software Reference Manual".