March 23, 2019, 08:59:28 AM
Robotforum | Industrial Robots Community

 Syntax for command files (.CM)

Author Topic:  Syntax for command files (.CM)  (Read 27262 times)

0 Members and 1 Guest are viewing this topic.

November 17, 2016, 11:35:48 AM
Read 27262 times
Offline

bidzej


Hi!

I made this topic to show you a very nice feature that is not listed in any manual from Fanuc.

The following quote is my original post (from which this topic came), you can generally skip it and go straight to the description of the .CM files.

Please feel free to contribute and leave a Thank you :icon_wink:

Quote
I am working on some small Karel software solution, that is sold to our customers as a "software package". To make the installation easier for the customer, I have prepared a .CM file that loads all necessary files (.PC, .VR, .TP, .TX etc.) to the robot and it works great. The thing is, that I would also like the file to do some more advanced changes or be flexible (allowing it to react to some unpredicted situations). As far as I know, it is doable, but can't seem to find any help on the syntax.

The commands that I use in the current file are taken from some other Fanc .CM files. These are:
# PRINT
# PCLOAD
# VRLOAD
# TPLOAD
# KCL LOAD FORM (this one allows me to think, that it is possible to use the KCL commands in the .CM files, but that does not help a lot, as I would also like to check some values and use conditional instructions if possible)

EDIT:

Okay, so this topic became a sticky one :icon_mrgreen: I will gather all the syntax posted in this topic in the first post, so that it is easy to find. Also, I will try to explain as much on the .CM files as I can find.
Please feel free to post anything you find out on .CM files, your suggestions, corrections or anything else which can make this topic better :)

The list contains .CM instructions grouped according to their functionality. Instructions in each group are listed alphabetically (at least more-or-less :icon_wink:).

What is a .CM file?

I guess it's a tool dedicated for Fanuc software developers. Basically, it's a file that can be executed using the FILE menu of the robot. It can perform various operations on files, programs (including .PC), variables (in specific programs or the system), print out information etc. It's a perfect solution for changing the robot configuration or creating installation procedures for custom software. For example, it is possible to:
  • quickly change the robot configuration from delivery state to a specification that you use as standard, by operating on system variables
  • create a kind of "installation wizards" for your custom-made software: loading files, running programs, setting up desired system variables etc. Hint: what Fanuc does (and what I have also implemented) is creating various .PC programs which perform operations more advanced than the .CM syntax allows, but loading, running, then deleting them and their variables using the .CM file, according to the logic evaluated in the .CM file)
  • ...and many more, the possibilities here are really great!
.CM files can be executed in Cold/Hot- and Controlled-Start modes of the controller.


How do I create a .CM FILE?

.CM files are just text files that contain a set of instructions for the controller (they do not even have to be placed in separate lines). You can create a .CM file using any text editor (including a standard Windows Notepad). You just write the instructions, save the file with a .CM extension and that's it. Example (based on a software package's installation .CM-file that I have created):

Code: [Select]
PRINT "#############################"
PRINT "#   Installing a program    #"
PRINT "#############################"

PRINT "Loading frm.tx..."
kcl load form frm
PRINT " - frm.tx loaded!"

PRINT "Loading frm.vr..."
vrload ut1:frm.vr
PRINT " - frm.vr loaded!"

PRINT "Loading PROGRAM.pc..."
pcload PROGRAM
PRINT " - PROGRAM.pc loaded!"

PRINT "Loading PROGRAM.vr..."
vrload ut1:PROGRAM.vr
PRINT " - PROGRAM.vr loaded!"

PRINT "Loading TP_PROG.tp..."
tpload TP_PROG.tp
PRINT " - TP_PROG.tp loaded!"

PRINT "All files loaded OK!"

PRINT "Customizing MENU..."
PCLOAD UT1:\SETUP\SET_MENU.PC
RUNPC SET_MENU
DELPC SET_MENU
VRCLEAR SET_MENU
PRINT " - MENU customized!"

PRINT "Read the README file, check setup"
PRINT "& restart the system!"


How do I run a .CM FILE?

Create a .CM file, load it to a memory device (like an USB-stick), connect it to the robot, find the file using the FILE menu and then just select it, press ENTER and confirm with F4 - YES. The .CM files are not loadable, you just execute them from where they are.
Just remember to run your .CMs in the main window of the Teach Pendant (the left one when the screen is split). The file will be executed, with an appropriate information after the successful completion (that you should confirm with F4 - OK). That's all!

====================================================================================================

General remarks:

  • Be careful when trying to make your file clearer by implementing spaces and/or tabulators in the layout.  SOME INSTRUCTIONS DO NOT WORK WITH TABs (e.g. PCVLOAD), AND OTHERS WITH SPACES (e.g. KCL) BEFORE THE ACTUAL INSTRUCTION. Either do not use tabs/spaces before instructions, or test the file for proper function when using them.

====================================================================================================

KCL (Karel Command Language):

KCL anyKCLcommand - this allows you to use KCL commands, listed in the Karel Reference Manual. You can use it for operations on variables, files etc, for example:
Code: [Select]
KCL SET VARIABLE [ProgramName] variable=value
Code: [Select]
KCL ABORT ALL
Code: [Select]
KCL DELETE FILE MD:\PROGRAM.VRThis is definitely the most powerful tool for .CM files, as the KCL commands (described in the Karel manual) allow you a better control over the performed operations, and the command palette is much wider than the one of standard .CM instructions.

PROGRAM FLOW CONTROL:

IF statement - note: arguments listed one after another seem to be interpreted as OR - see the 2nd example of ORDER evaluation with IF.

  • IF VAR VarName "VarValue" ... ELSE ... ENDIF - evaluates the value of the specified variable. Be sure to compare the variable with a correct data type. This function seems to have problems when working with variable arrays, like the $CUSTOMMENU variable...
Code: [Select]
IF VAR $APPLICATION[2] "V7.30P/*"
  SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
ELSE
  IF VAR $APPLICATION[2] "V7.40P/*"
    SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
  ELSE
    IF VAR $APPLICATION[2] "V7.50P/*"
      SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
    ELSE
      IF VAR $APPLICATION[2] "V7.60P/*"
        SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
      ENDIF
    ENDIF
  ENDIF
ENDIF

  • IF ORDER xxxx ... ELSE ... ENDIF - evaluates the robot specification.
Code: [Select]
IF ORDER J737 J738 !this syntax I assume means "OR"
...
ENDIF
Code: [Select]
IF ORDER J654 J655 J656
   PRINT "Load"
   PRINT "SHELLSTART"
     runpc inst
ENDIF


OPERATIONS ON VARIABLES:

SETVAR $VarName VarValue - sets the specified system variable to the specified value. Be sure to use same data types.
Code: [Select]
SETVAR $UALRM_MSG[1] "Invalid Argument"

OPERATIONS ON IOs:

This instruction comes from this reply by lexx905. I've done some interpretation of the instruction's parameters and I hope it's ok. Multiple examples provided below should help. I haven't tested this instruction yet, but I assume, that standard limitations to IOs apply here (so setting unsimulated inputs may be impossible).
SETIOVAL type index sim_mask unsim_val sim_val - sets an IO point of selected type to a selected value in a selected mode, where:
  • type:
    1 = DI
    2 = DO
    8 = RI
    9 = RO
    35=Flag
  • index is just an index number of the IO point
  • sim_mask:
    0 = signal unsimulated
    1 = signal simulated
  • unsim_val is the value in UNSIMULATED mode
  • sim_val is the value in SIMULATED mode
Code: [Select]
!***************
!DI 33 SET Sim Mode and True
SETIOVAL 1 33 1 0 1

!DI 34 SET Sim Mode and False
SETIOVAL 1 34 1 0 0

!DI 35 SET UnSim Mode
SETIOVAL 1 35 0 0 0

!***************
!DO 33 SET Sim Mode and True
SETIOVAL 2 33 1 0 1

!DO 34 SET Sim Mode and False
SETIOVAL 2 34 1 0 0

!DO 35 SET False
SETIOVAL 2 35 0 0 0

!DO 36 SET TRUE
SETIOVAL 2 36 0 1 0

!************
!RI 1 SET Sim Mode and True
SETIOVAL 8 1 1 0 1

!RO 1 SET Sim Mode and True
SETIOVAL 9 1 1 0 1

!************
!Flag[10] = true
SETIOVAL 35 10 0 1 0

!Flag[11] = false
SETIOVAL 35 11 0 0 0


PROGRAMS, FILES:

Note, that:
  • instructions which are type-specific (designed to work with a particular filetype, like PCLOAD for PC-files only, VRCLEAR for .VR, etc.)  should all work as described for PCLOAD - with full path, or just a filename (with the extension ommited in this case). However, there are some exceptions (like VRLOAD or TPLOAD) - as this is not an official feature, the syntax is a bit messy sometimes...
  • generally, adressing goes as follows: you can use dev:filename when the addressed file is in the root folder of the selected device, but you have to use dev:\folder\...\filename.filetype if it is located deeper in the structure.

ASLOAD filename - loads namefile.AS (assembly files - used internally)

COPY device:\(path\)sourcefile.filetype device:\(path\)targetfile.filetype - copies sourcefile to targetfile.
Code: [Select]
COPY MD:\MEMORY.DG MED:\00\TEMP\TEMP_MEMORY_STAT.DG
DEL filepath:\filename.filetype\ - deletes filename.filetype located in filepath

DELFR FR:\filename.filetype - deletes filename.filetype from FROM (can also be used to delete files from FRS - internal system memory, not accessible via TP):
Code: [Select]
DELFR FRS:\CTRLRSTR.DAT
DELPC ProgramName - deletes the specified .PC program from the robot memory

DELTP ProgramName - deletes the specified .TP program from the robot memory. Important: this instruction will simply ignore a non-existing .TP program. This means it can be used before TP loading instructions to make sure they do not hit an existing file (which leads to .CM file execution being aborted). More in THIS post.

FRCOPY fr_:\targetfile.filetype dev:\sourcefile.filetype - copies a source file to specified location on FROM. fr_ is for FR, FRS, FRSU, FRB - however, have no idea what the last two mean). Can be used to copy any type of files, including .SV and .IO:
Code: [Select]
FRCOPY frs:diocfgsv.io MD:diocfgsv.io
MKDIR device:folder - creates a folder under a specified address
Code: [Select]
! create a folder "test" on USB stick in the controller's USB port
MKDIR UD1:test


PCCLEAR filename - clears namefile.PC (removes from program stack)

PCLOAD Device:\PathToProgram\ProgName.PC - loads the specified .PC program
Code: [Select]
PCLOAD UT1:\SETUP\PROGRAM.PCCan be also used just with a program name (without the path) - the program will be loaded from the currently selected device:
Code: [Select]
PCLOAD ProgName   ! notice, that the .PC extension is omitted in this case!
PCVLOAD filename - loads filename.SV (no .SV-extension in the instruction!)

RUNPC ProgramName - runs the specified .PC program that is loaded to the robot (no .PC-extension in the instruction!)

TPLOAD programname.tp or TPLOAD device:program.tp - loads the specified .TP program to the robot memory (.TP-extension required!), for example:
Code: [Select]
TPLOAD my_tpprogram.tp
TXPLOAD filename - loads filename.TX (no .TX-extension in the instruction!)

VRCLEAR ProgramName - deletes the .VR file of the specified program from the robot's memory (no .PC- or .VR-extension in the instruction!)

VRLOAD device:filename.vr - loads a specified .VR file to the robot's memory (.VR-extension required!), for example:
Code: [Select]
VRLOAD UT1:my_vrfile.vr
WR_FILE device:filename.filetype "text" - attaches a given text to the contents of the given file. I guess this instruction can only modify files in the root folder of a selected device.
Code: [Select]
WR_FILE MED:AUKEPDCS.DAT "Don't init DCS safety parameter"

OTHER INSTRUCTIONS:

@path:\file.cm - executes another .CM file from within the current .CM file. Can be used without path - in this case, the current device and path will be used. If the .CM file is located in the root folder of the memory device, backslash can be ommited in path. Examples:

Code: [Select]
@md:setup.cm    ! executes setup.cm from MD:
@ud1:\program\setup.cm    ! executes setup.cm from UD1:\program
@setup.cm    ! executes setup.cm from the currently selected location (device/path)

CLRALMH - clears alarm history

DELAY # - delays execution of the .cm file by # milliseconds. DELAY 1000 will wait 1 second.

EXIT - finishes the .CM file execution. Can be used in IFs, to finish the execution before the whole program is completed (on errors for example).

IGALBKUP device:\folder - stores an AoA backup in a specified folder
Code: [Select]
! store an AoA in a folder "test" on USB stick in the controller's USB port
IGALBKUP UD1:\test


PRINT "string" - displays the specified string. If you do not use quotation marks, only the string up to the first space will be displayed. If you use quotation marks, the whole string between them will be displayed, BUT including the marks.
Code: [Select]
PRINT "Hello user"
SPEP_ON / SPEP_OFF - not sure what these instructions do, but Fanuc uses SPEP_OFF right before operations like MKDIR, DEL, COPY or other istructions which operate on the structure of files or folders, and SPEP_ON right after these instructions, like in the example below (taken straight from a .CM file made by Fanuc)
EDIT: these instructions allow you to ignore errors from some instructions and avoid breaking the whole sequence because of one instruction returning an error. SPEP_OFF makes the .CM execution ignore the errors, SPEP_ON makes it vulnerable to faults again.
In the example below, if file TEMP_MEMORY_STAT.DG doesn't exist or any other fault is encountered by the COPY... instructions, the execution of the .CM file will not be aborted:
Code: [Select]
SPEP_OFF
COPY MD:\MEMORY.DG MED:\00\TEMP\TEMP_MEMORY_STAT.DG
SPEP_ON
SPEP_OFF
DEL MED:AUKEPDCS.DAT
WR_FILE MED:AUKEPDCS.DAT "Don't init DCS safety parameter"
SPEP_ON
There are also instructions like COLDSPEP_ON and COLDSPEP_OFF, but found them only in 1 file and ofc have no idea what they do...

RE_POWER - cycles power on the controller. Be careful with this instruction - I have only tested it in Roboguide so far and it works OK when the .CM file is executed in Cold-Start, but causes a VARS-204 Power-off incomplete fault when in Controlled-Start!
« Last Edit: November 16, 2018, 12:47:17 PM by bidzej »

Today at 08:59:28 AM
Reply #1

Advertisement

Guest

November 28, 2016, 04:13:37 PM
Reply #1
Offline

Nation


It is unfortunate that this is not documented anywhere, but I found the IF statement synax in one of Fanuc's .cm files.

Here it is:
Code: [Select]
IF VAR $APPLICATION[2] "V7.30P/*"
  SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
ELSE
  IF VAR $APPLICATION[2] "V7.40P/*"
    SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
  ELSE
    IF VAR $APPLICATION[2] "V7.50P/*"
      SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
    ELSE
      IF VAR $APPLICATION[2] "V7.60P/*"
        SETVAR $CCSCB2_GRP[1].$FS_TYP2 1
      ENDIF
    ENDIF
  ENDIF
ENDIF
Check out the position converter I wrote here!

November 29, 2016, 07:43:15 AM
Reply #2
Offline

bidzej


Thanks. I guess Fanuc keeps that syntax to themselves... I have found exactly the same function in some .CM file. I guess that there are some limits with using array variables in that IF function which I am not aware of (I have tried changing some items in CUSTOMMENU variable array, but no luck), but that is a start.

Maybe we could make a topic like the one with BG-Logic for these .CM files? What would moderators say to that? I could just add things posted in this topic to the first post and make a nice list this way... So, for example:

PROGRAM CONTROL:

.PC Programs:

DELPC programname - deletes the specified .PC program from the robot memory

PCLOAD programname - loads the specified .PC program from a current device

RUNPC programname - runs the specified .PC program

VRCLEAR programname - deletes the .VR file of the specified program
« Last Edit: November 29, 2016, 07:50:15 AM by bidzej »

February 15, 2017, 04:24:30 PM
Reply #3
Offline

skalactik


More commands found in various .CM files :

# PCVLOAD namefile - to load namefile.SV
# TXPLOAD namefile - to load namefile.TX
# ASLOAD namefile - to load namefile.AS (assembly files - used internally)


#PCCLEAR namefile - to clear namefile.PC
#DELFR FR:namefile.filetype - to delete namefile.filetype from FROM
#DEL filepath:\filename.filetype\ - to delete filename.filetype located in filepath

February 22, 2017, 10:34:16 AM
Reply #4
Offline

bidzej


Added these new instructions, thx for your commitment skalactik!

April 05, 2017, 11:51:09 AM
Reply #5
Offline

Chander_hxj


You are a very great guy, nobody can learn these great info. from any FANUC manual.
I have a question about '*.as file' which seems that you are good at it, I got a as-file, however, I can not understand the code inside.
by the way,can you share more about karel software development, I am also interested in it.

April 05, 2017, 12:49:31 PM
Reply #6
Offline

bidzej


Honestly, don't remember what exactly is in the .AS files and don't have an appropriate manual at the moment. Maybe someone else can help here?

When it comes to Karel... Well, there is a separate manual for that, but to really be able to do some sensible programming, you need experience. Mainly because not everything works as described in the manual, especially things that have anything to do with motion. As far as I know, these motion instructions are somewhat old and not always compatible with the newest controllers, as Fanuc gave up the development of KAREL motion some time ago.

Today at 08:59:28 AM
Reply #7

Advertisement

Guest

April 06, 2017, 03:43:32 PM
Reply #7
Offline

skalactik


Quote
I have a question about '*.as file' which seems that you are good at it, I got a as-file, however, I can not understand the code inside.
.as files are Assembly files, basically they are used to perform direct manipulation of internal memory (or registry) of the Operating system

April 08, 2017, 03:58:05 AM
Reply #8
Offline

Chander_hxj


thanks for your advice
I'm totally agree with you, the info., in the karel manual, sometimes makes me waste much time to understand, because some incorrect info. will mislead me and i have to do many experiments to get one point from it.
as you said, the motion part in J3iB Karel manual can not be found in the new manual. however, as a software developer, it's important.
I am learning from your *.CM FILE, and I'll work hard on karel programming, there's so much fun in it.
if you have any info, about karel, i will be your first fan to follow it.

April 08, 2017, 04:08:44 AM
Reply #9
Offline

Chander_hxj


I have a question about '*.as file' which seems that you are good at it, I got a as-file, however, I can not understand the code inside..as files are Assembly files, basically they are used to perform direct manipulation of internal memory (or registry) of the Operating system
[/quote]


i got two *as file, however, I really dont understand about it's rules in it.
e.g.
1:% ASM #2 EMCD #2#1
2:$0a000000 #31 $F4 !Online shift use$CUSTOMMENU[4]

i can understand the first line, but, I cant transfer the second line's code one by one
i can guess the function about the second line.

the other prog.
1:% ASM #2 TOPK #2#3#1
2:07000000#31 $F5 !F7:CAN/STR(CANCEL/Start line)
3:08000000#31 $F6 !F8:LOG/END(Log/End line)
4:09000000#31 $F7 !F9:CAN/STR(Start/Convert)

if you have any advance to share, feel free. thanks.







April 12, 2017, 12:58:19 PM
Reply #10
Offline

Fabian Munoz

Administrator
Hi Chander_hxj

I don't know much about these AS files,
I just want to ask you if this last post is related to Fanuc As. files ?
Also, Should that post start a new thread ?

Fabian
somar

April 22, 2017, 04:22:48 AM
Reply #11
Offline

Chander_hxj



Hi Fabian,
I'm sorry to make this mistake.
 Chandler_HXJ

April 22, 2017, 04:29:42 AM
Reply #12
Offline

Chander_hxj


PCVLOAD[/b] namefile - to load namefile.SV
# TXPLOAD namefile - to load namefile.TX
# ASLOAD namefile - to load namefile.AS (assembly files - used internally)


#PCCLEAR namefile - to clear namefile.PC
#DELFR FR:namefile.filetype - to delete namefile.filetype from FROM
#DEL filepath:\filename.filetype\ - to delete filename.filetype located in filepath


I've been learning cm.file for two weeks, and I found [PCVLOAD] also used in the *.vr and *.pc files.
when used in *pc.file load, it's also same to PCLOAD.
if anything is incorrect, thanks for your suggestion.

April 22, 2017, 04:46:52 AM
Reply #13
Offline

Chander_hxj


PROGRAM CONTROL:[/b]

.PC Programs:

DELPC programname - deletes the specified .PC program from the robot memory

PCLOAD programname - loads the specified .PC program from a current device

RUNPC programname - runs the specified .PC program

VRCLEAR programname - deletes the .VR file of the specified program
 
Hi,master bidzej
I'll add some syntax about CM-file, which I also don't know about its function.However, I wish master bidzej or someone will fix it out oneday. :nanananana:
the structure is
1.#SPEP_ON.........#SPEP_OFF
2.#FRCLRPR.........#FRSETPR

another question is about [How to Start the CM.file]
if there's no KCL command in the cm.file,I can start the CM.file.
However, if the cm.file contains the KCL command, I need to set the varaible [$RMT_MASTER] to '1', disable the teach pedant, and switch to AUTO mode. In the case, I can start the CM.file finally



Today at 08:59:28 AM
Reply #14

Advertisement

Guest

April 22, 2017, 08:23:56 AM
Reply #14
Offline

bidzej


I have also seen these SPEP instructions in some .CM files, but have no idea what they do...
« Last Edit: April 24, 2017, 11:52:37 AM by bidzej »

May 01, 2017, 01:08:51 PM
Reply #15
Offline

lexx905


Ciao

CLRALMH - Clear alarm history
RE_POWER - Restart system

May 01, 2017, 01:38:53 PM
Reply #16
Offline

lexx905


And still, using such a construction -> SETVAR $ CCSCB2_GRP [1]. $ FS_TYP2 1, you do not ever refer to a variable of type STRING.
It is better to refer to the variables like this:
    KCL SET VAR $ ATCELLSETUP. $ HOME_MACRO = 'BLA_BLA'
    KCL SET VAR $ ACC_MAXLMT = 15
    KCL SET VAR $ AP_AUTOMODE = TRUE

May 02, 2017, 05:43:01 AM
Reply #17
Offline

bidzej


that SETVAR... comes from some Fanuc .CM, that's why I mentioned it. The KCL SET VAR instructions are listed already. Thx for your input! :merci:

May 25, 2017, 05:45:45 PM
Reply #18
Offline

lexx905


Ciao


MKDIR UD1:test
IGALBKUP UD1:\test
EXIT


This code will automatically create a TEST folder on the USB and put AOA and IMAGE on it :)


« Last Edit: May 27, 2017, 07:39:43 AM by lexx905 »

May 25, 2017, 06:41:10 PM
Reply #19
Offline

lexx905


Change Status - Di\Do\Ri\Ro\Flag

!***************
!DI 33 SET Sim Mode and True
SETIOVAL 1 33 1 0 1

!DI 34 SET Sim Mode and False
SETIOVAL 1 34 1 0 0

!DI 35 SET UnSim Mode
SETIOVAL 1 35 0 0 0

!***************
!DO 33 SET Sim Mode and True
SETIOVAL 2 33 1 0 1

!DO 34 SET Sim Mode and False
SETIOVAL 2 34 1 0 0

!DO 35 SET False
SETIOVAL 2 35 0 0 0

!DO 36 SET TRUE
SETIOVAL 2 36 0 1 0

!************
!RI 1 SET Sim Mode and True
SETIOVAL 8 1 1 0 1

!RO 1 SET Sim Mode and True
SETIOVAL 9 1 1 0 1

!************
!Flag[10] = true
SETIOVAL 35 10 0 1 0

!Flag[11] = false
SETIOVAL 35 11 0 0 0

May 29, 2017, 06:18:54 AM
Reply #20
Offline

bidzej



Today at 08:59:28 AM
Reply #21

Advertisement

Guest

June 01, 2017, 09:45:02 AM
Reply #21
Offline

bidzej


I have just added a few more instructions to the list (WR_FILE, SPEP_ON/SPEP_OFF, COPY) and updated descriptions of a few others.

Pls let me know if this is still readable for you. Should I change the format of the list or divide it into more detailed sections?

July 27, 2017, 03:41:42 PM
Reply #22
Offline

robotomation


I recently used a Command File to populate UALRMs on several(16) robots. It took minutes, instead of hours to do.
I was quickly and easily able to implement 200+ User Alarms  :top:

Sample of syntax:
SETVAR $UALRM_MSG[1] "Invalid Argument"
SETVAR $UALRM_MSG[3] "BG Logic 1 not running"
SETVAR $UALRM_MSG[4] "BG Logic 2 not running"
SETVAR $UALRM_MSG[5] "BG Logic 3 not running"
SETVAR $UALRM_MSG[6] "BG Logic 4 not running"
SETVAR $UALRM_MSG[7] "BG Logic 5 not running"
SETVAR $UALRM_MSG[8] "BG Logic 6 not running"
SETVAR $UALRM_MSG[9] "BG Logic 7 not running"
- - - MH - - -

August 30, 2017, 02:48:33 PM
Reply #23
Offline

bencor21


DELTP program - deletes the specified .TP program from the Robot memory

Use this before TPLOAD device:program.tp (like loading from USB).  It won't alarm if the file exists in Robot memory where the TPLOAD will if the file exists & it ends the execution of the .cm file.

September 01, 2017, 12:06:38 PM
Reply #24
Offline

bidzej


Hi bencor21, I've added these to the OP, thanks for your input. Could you be more specific about that overwriting?


Share via facebook Share via linkedin Share via pinterest Share via reddit Share via twitter

xx
S controller command syntax

Started by tdevine77 on Kawasaki Robot Support Forum

4 Replies
2758 Views
Last post September 09, 2015, 10:15:33 AM
by kwakisaki
xx
Syntax Help using LPOS

Started by ovoyevoda on Fanuc Robot Forum

14 Replies
12673 Views
Last post January 23, 2015, 05:58:55 PM
by ovoyevoda
xx
Syntax problem

Started by zicki_88 on KUKA Robot Forum

3 Replies
360 Views
Last post July 11, 2018, 10:15:21 AM
by Fubini
xx
Syntax of INTERRUPT

Started by rmacumber on KUKA Robot Forum

5 Replies
358 Views
Last post October 22, 2018, 04:04:30 PM
by panic mode