When trying to use PSPD with SE[x], the controller faults with CPMO-136 "No PSPD allowed in this region / application block"
When it gets to pre-processing Line 14, it throws the CPMO-136 fault.
If the SS/SE options are removed, it works, but then it won't glue, will it? (/s)
I'm fairly certain that SS/SE and PSPD should be able to work together, right?
Does anyone have any tips or ideas for correcting or debugging this?
Test program:
Code
/PROG A_GLUE_SEAM_1 Process
/ATTR
OWNER = MNEDITOR;
COMMENT = "1st Dispense";
PROG_SIZE = 877;
CREATE = DATE 40-05-25 TIME 18:37:36;
MODIFIED = DATE 40-05-29 TIME 17:22:42;
FILE_NAME = MOV_SEAM;
VERSION = 0;
LINE_COUNT = 35;
MEMORY_SIZE = 1245;
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;
/APPL
DISPENSE : TRUE ;
DISPENSE_PROCESS;
CYCLE_TIME : UNINIT;
LAST_CYCLE_TIME : UNINIT;
GUN_ON_TIME : UNINIT;
LAST_GUN_ON_TIME : UNINIT;
DEFAULT_USER_FRAME : 9;
DEFAULT_TOOL_FRAME : 3;
EQUIPMENT_NUMBER : 1;
/MN
1: UTOOL_NUM=3 ;
2: UFRAME_NUM=9 ;
3: PAYLOAD[3] ;
4: UNLOCK PREG ;
5: CALL A_MAKE_PATH(1) ;
6: LOCK PREG ;
7: ;
8:J PR[41:Jnt_App_Disp1] 25% CNT100 ;
9: ;
10: !Approach starting point ;
11:L PR[199:~Disp_Approach] 250mm/sec CNT100 RTCP ;
12:L PR[121:~Disp_01] 250mm/sec FINE RTCP ;
13: !Start sealing ;
14:L PR[122:~Disp_02] 250mm/sec CNT100 RTCP PSPD25 SE[1] (edit: SS[1], actually!) ;
15:C PR[123:~Disp_03]
: PR[125:~Disp_05] 250mm/sec CNT100 RTCP PSPD25 ;
16:L PR[124:~Disp_04] 250mm/sec CNT100 RTCP PSPD25 ;
17:L PR[125:~Disp_05] 250mm/sec CNT100 RTCP PSPD25 ;
18:C PR[126:~Disp_06]
: PR[128:~Disp_08] 250mm/sec CNT100 RTCP PSPD25 ;
19:L PR[127:~Disp_07] 250mm/sec CNT100 RTCP PSPD25 ;
20:L PR[126:~Disp_06] 250mm/sec CNT100 RTCP PSPD25 SE ;
21: ;
Display More
- Jay
P.S. Robot-Forum hasn't let me post or reply since the big adpocalypse. I can log in and edit old replies, or DM, but can't post, so I made this new account, and it works fine.
This indicates that there is a bug in the site code. I'd love to have my old account back in working order, though.