曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
EPICenter window, or use F9. EPICenter will review every (non-comment) line in
your EPL Project and identify any errors. Keep in mind, your error may not be on
the line identified, but may be in a preceding line or the last line in the file compiled
prior to the line that is being reported by EPICenter. If an error is identified, correct
the error and then recompile (F9). When you get a clean compile, you’ll get a pop24
up window with an “OK” to acknowledge, then you’re ready to download the code to
your EPIC USB.
4.2.6 Downloading EPL to EPIC
Once you get a clean compile, download the EPL code to your EPIC by using the
menu item on the top of the EPICenter window or by pressing F10. EPICenter will
now download your EPL to EPIC while giving you a progress window so you can
track the progress. You’ll also hear EPICenter disconnect and reconnect the EPIC
from/to Windows as part of this process. Once the download is complete, a special
procedure, called “INIT” in your <name>.epl file is executed. The “INIT” procedure
is where you can place code (i.e. setup routines) that you want executed whenever
your EPIC is first loaded. Now that code has been successfully loaded into your
EPIC, you’re ready to use it, so close the EPICenter since you won’t need it again
until you need to modify your EPL code.
4.3 EPL Software
4.3.1 EPL Program Syntax
4.3.1.1 All text between angle brackets “< >” is descriptive and should not be
taken literally. All options separated by vertical lines “|” are mutally exclusive. All
options within square brackets “[ ]” are optional, options not within square
brackets are required. All text following the double slashes “//” <comment> and
preceding the end-of-line is ignored. Comments may appear anywhere in your
program.
4.3.1.2 Identifiers (ie. string literals <label> <flag> <var>), are used to “name”
flags, variables, and procedure blocks. Identifiers are case sensitive (ie. “Flag1” is
not the same as “FLAG1”) and must be unique. Reserved words cannot be used as
identifiers. Also, identifiers can only start with an Alpha (A-Z) or underscore ( _ )
characters. If you reuse a label, flag or variable by defining it twice, you will get the
“Ambiguous use of <item name>” error since all labels, flags and variables must be
unique.
4.3.1.3 : <label> { <function(s)> } This is the syntax for a label and it’s
accompanying function statements. You can now use the syntax <return type>
<label>(<arg type> <arg>,....) in preparation for passing arguments and return
values in later versions of EPICenter. Currently however, the only supported form
is: void <label>(void){ ....} which has no arguments (leading void) and no return
values (trailing void). There is also a predefined label called “RETURN” that can be
used in place of any label reference. A “jump” or “call” to “RETURN” does nothing.
4.3.1.4 EPICenter allows the use of predefined shortcuts in some of the names of
the functions. These shortcuts are defined as follows: keypress|kpr(<key>); This
25
function definition means that this function can be KEYPRESS(<key>) or
KPR(<key>) where KPR(<key>) is the shortcut version of this function.
4.3.1.5 The preprocessor directive, “#define”, allows you to use a string to
represent a value (#define <string> <value>). In the example if Trigger is equal to
module 0, row 0, button 0 and if the Auto pilot switch is module1, row 5, bit 6, we
could use the following statements in our EPL file:
#define TRIGGER M0R0B0
#define APSWITCH M1R5B6
Once defined, we only need to refer to TRIGGER and APSWITCH for actions
involving these devices (mod, row, bits).
4.3.1.6 Numbers can be expressed in decimal, hexadecimal, or binary. If a
number is to be a hexadecimal number, the numerical value must be preceded by
”0x”. If a number is to be in binary , the numerical value must be preceded by “0b”.
Therefore 123 can be represented as follows:
decimal: 128 range 0-255(byte),0-65535(word)
hexidecimal: 0x80 range 0-0xFF(byte), 0-0xFFFF (word)
binary: 0b10000000 range 0-0b11111111(byte), 0-0b1111111111111111
4.3.2 EPL Program Structure
To write an effective EPL Project, you must define quite a number of items for EPIC
about your hardware and how you want EPIC to respond to hardware actions. I use
the following structure to organize my EPL code to ensure I tell EPIC everything it
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料18(6)
