Other Tools Manual
Other Tools Manual
匯出日期:2025-03-06
修改日期:2020-09-16
机床产品/Machine Tool Products
–
Other Tool.
–2
机床产品/Machine Tool Products
–
Other Tool.
1.1.1 Purpose
The operation log reader can record the user's keystrokes when operating the machine, which can help the
Machinery electrical control staff or customer service staff for troubleshooting.
Controller
• New version: 10.118.24B, 10.118.25B, 10.118.28O, 10.118.38 and above.
• Old version: Versions other than the new versions.
OKLogReader
• New version: Version 3.0.0 and above.
• Old version: versions other than the new versions.
1.1.3
How to Use
Directory
5 Key
• ARM - F10 Next → F2 Diag. → F4 Operation Log
• X86 - F10 Next → F2 Diag. → F10 Next → F4 About → F2 Operation Log
8 Key
• ARM - F10 Next → F2 Diag. → F4 Operation Log
• X86 - F7 Diag. → F8 System manager → F6 About → F2 Operation Log
Screen Description
1. Each record shows the [Number] and [record data]. Order number 1 is the latest record.
2. Each page displays 80 records, and you can use PageUp/PageDown to see later or earlier records.
3. DOS displays up to 12 pages, while CE has no page limit.
4. Whenever you re-enter the history page, it will be updated to the latest record when you "entering the
history page".
Basic Operations
Find Alarm
• Input format: alarm ID + alarm number.
• If entering MOT11, it will jump to where the first alarm MOT11 record is.
• If the input format is incorrect, a messagebox "format wrong!" will pop up.
Find I-Bit
• Input format: I + number.
• If entering I88, it will jump to where the first I88 ON record is.
PC - Log Reader
Download
To download the log reader, please go to SYNTEC official website → Customer Support → Software Download →
04. Application Tool → OKLogReader.
We recommend downloading version 3.0.0 and above. Please refer to" Version Matching and Display Specifications"
for compatibility notes.
Basic Operations
• Note: OKLogReader displays the old record first and then the new record, in the opposite order of the
controller.
This operation is for OKLogReader to display operation logs and data logs in a consistent manner.
• Filtering: "Full Log" displays all operation logs, while "Alarm", "I-Bit" (second panel), "First Panel Key
Log" (first panel), and "Action" can be filtered by multiple criteria.
• Jump to the previous/next identical value: After selecting a row in the list, pressing F3 can jump to the next
row with the same RawData value, and Shift + F3 to the previous one.
• Searching: Press "Search Log" to bring up the search window. Fill in the criteria, then press "FindNext" to
start searching from the highlighted row. It will highlight and jump to the latest record that meets the
criteria. If you want to search for the previous one, you can check the "Upwards" box on the right before
searching.
• Search DateTime: The input format is yyyymmdd or yyyymmddhm. E.g. 20150213 or 201502130900
• Search Alarm: The input format is Alarm ID+Alarm Number. E.g. MOT18
• Search I-Bit: The input format is Alarm ID+Alarm Number. E.g. I66
• Search Action: Refer to Appendix I for detailed human-machine action input format. E.g. S_MMach
• Search RawData: Refer to Appendix II for detailed RawData input format. E.g. 0x100500BC
• Search Index: The input format is Index number. E.g. 123
• Search OPLog: The input format is OPLog string name, and it can be searched with part of the string
(case as different strings). E.g. StartUp
• New version means that the controller version is 10.118.24B, 10.118.25B, 10.118.28O, 10.118.38 or above.
• In the new versions, an additional timestamp will be recorded for all operations.
1 17:07:58
2 11/04/15
3 17:07:58
4 StartUp
1 17:07:58
2 COR21
ClassID:
ClassID:
• OKLogReader
[ClassID]/ [ClassID]/[AlarmID] +
[AlarmID] + [ObjectID] [alarm
[ObjectID] string]
(start from SI and
has multilingual files
in MB/SB)
1 17:07:58
2 CycleStart On
N Data
o
1 17:07:58
2 Param3205Modified
2 MillLengthGeometry
Modified
Workpiece Input
No Data
1 17:07:58
2 G54Modified
1 17:07:58
2 Escape
S_MProg: Program
S_MRun: Execute
S_MAlarm: Alarm
S_MParam: Parameter Setting
S_MDiag: Diagnostics
2 AbsHome 1
User Change There are two records for one login or logout:
• One records the authority of login or
No Data
logout. (corresponds R5997)
• SyntecLogIn
• MakerLogIn 1 14:48:15
• AdminLogIn
• OtherLogIn
• LogOut 2 AdminLogIn
• The other one records the user name.
• Format: "User[CRC value of the 3 14:48:15
user name]".
4 User16320
2 EnterForceIO
EnterF Enter
orceIO ForceIO
mode 3 14:48:15
{ I bit Using
name ForceIO 6 I123ForceOff
} function to
Force force the I 7 14:48:15
Off bit Off
8 I123ForceOn
{ I bit Using
name ForceIO
} function to 9 14:48:15
Force force the I
On bit On 10 O123ForceOff
16 ReleasO123
OPLo Trigger
g recording
conditions
Releas Releasi
e{ I bit ng the
name ForceIO
} state
of I
bit
Releas Releasi
e{ O ng the
bit ForceIO
name state
} of O
bit
• OKLogReader
• 3.6.0~ 4.8.0~
4.8.0
{ Ibit refer
name } to PLC
Force related
Off records
display
{ Ibit
name }
Force
On
{ Obit
name }
Force
Off
{ Obit
name }
Force
On
3.6.0~ 4.8.0~
4.8.0
Releas
e{ Ibit
name }
Releas
e{ Obit
name }
ClassID:
• OKLogReader
[ClassID]/ [ClassID]/[AlarmID] +
[AlarmID] + [ObjectID] [alarm
[ObjectID] string]
(start from SI and
has multilingual files
in MB/SB)
Action Record
1.1.5 Notes
1. PC simulator: Operation Log is currently not supported.
2. CE controller: Available in versions 10.115.29, 114.23 and above.
3. DOS controller: Available in versions 10.115.42, 114.37 and above.
4. The operation log reader can only be enabled on models supporting FRAM (models without FRAM: SUPER
with PIO3/PIO4 or versions before PIO5 v5.5).
5. Please refer to the "Parameter Setting Instruction Manual" to set parameter 5 correctly. If it is set incorrectly,
the operation log function will not be enabled properly.
OKLogReader
New Version
(3.0.0 and above)
OKLogReader
Old Version
The action names and menu names need standard environment data to be
displayed.
You need to load MB/SB through SI and download the standard environment
data, then open OKLogReader to see the information above.
For more details: Syntec IDE Operation Manual. > SI Operation steps
3. ForceIO On/Off/Release
• The short comments will only be displayed in the OKLogReader under the following scenarios:
1. Opening MB, and the target MB contains a backup ladder (cnc.lad).
2. Opening SB.
3. Using SI to read MB/SB and then opening.
• Before 4.8.0 After 4.8.0
CNCPosition Home 0
CNCProgram End 1
CNCGraphTea BackSpace 2
ch
CNCMonitor Insert 3
CNCAlarm Delete 4
CNCGraphTea PageUp 5
ch
CNCHelp PageDown 6
CNCReset Space 7
Add / + Enter 8
Substract / - Up 9
\ Down .
; Left Divde or /
下表为目前会显示支援的OPLog键盘Key值
Below table is the current supported OPLog keyboard Key value
6 XButto Seco 7 G G 1 2
n2 nd X 1 3 0
click 6 1
of
mous
e(five
-butt
on
mous
e)
7 7 H H 1 2
2 3 0
7 2
8 BackSp BACK 7 I I 1 2
ace SPAC 3 3 0
E 8 3
9 Tab TAB 7 J J 1 2
4 3 0
9 4
1 LineFe LINEF 7 K K 1 2
0 ed EED 5 4 0
0 5
1 7 L L 1 2
1 6 4 0
1 6
1 Clear CLEA 7 M M 1 2
2 R 7 4 0
2 7
1 Enter ENTE 7 N N 1 2
3 R 8 4 0
3 8
Return RETU
RN
1 8 P P 1 Scroll SCROLL 2
5 0 4 LOCK 1
5 0
1 ShiftKe SHIFT 8 Q Q 1 2
6 y 1 4 1
6 1
1 Control CTRL 8 R R 1 2
7 Key 2 4 1
7 2
1 Menu ALT 8 S S 1 2
8 3 4 1
8 3
1 Pause PAUS 8 T T 1 2
9 E 4 4 1
9 4
2 CapsLo CAPS 8 U U 1 2
0 ck LOCK 5 5 1
0 5
Capital
2 KanaM IME 8 V V 1 2
1 ode Kana 6 5 1
mode 1 6
key
Hangu IME
elMode Hang
uel
mode
key
Hangul IME
Mode Hang
ul
mode
key
2 8 W W 1 2
2 7 5 1
2 7
2 JunjaM IME 8 X X 1 2
3 ode Junja 8 5 1
mode 3 8
key
OemOp OEM
enBrack open
ets bracket
key on
a US
standar
d
keyboar
d
OemQu OEM
otes singled/
double
quote
key on
a US
standar
d
keyboar
d
2 IMENo IME 9 1 2
9 nconve nonc 4 5 2
rt onver 9 4
t key
4 D1 1 1 F3 F3 1 MediaPl media 2
9 1 7 ayPause play pause 4
4 9 key 4
5 D2 2 1 F4 F4 1 Launch launch 2
0 1 8 Mail mail key 4
5 0 5
5 D6 6 1 F8 F8 1 2 EraseEo ERASR
4 1 8 4 f EOF
9 4 9
5 D7 7 1 F9 F9 1 2 Play PLAY
5 2 8 5
0 5 0
6 1 F18 F18 1
4 2 9
9 4
The purpose of the data log reader is to complement the operation log reader (OPLOG) in the interpretation of
abnormality detection.
For example, when the program starts to process, the data log reader will automatically record the current
machine coordinate and start line no. etc. This allows analysts to have a better grasp of the abnormal
situation.
1.2.2 Notes
1. The data is constantly captured, but the frequency of writing into DataLog.dat is every 10 minutes or as
soon as a MOT alarm is triggered.
2. The current data log reader is optimized for storage capacity for 3 days.
a. OKLogReader, which is window edition, can interpret the new format (corresponding to
controller versions 10.116.16 and above).
b. TransferDataRecords v1.x, which is console edition, can interpret the old format (corresponding
to the controller version below 10.116.16).
3. The events defined by the data log reader are not always issued when the state has changed, some are
detected every once in a while. The main categories are as follows.
a. Fixed time (before ID6): For example, ID6 (1sec in CS) will record the coordinate every 1000 ms.
b. PLC signal (ID7~18): For example, ID17 (Specified R On) is issued when PLC scan time (or
FastPLC scan time) detects that R value changes.
c. Processing status (ID21~25): For example, ID21 (ReadyToCS) is issued when the controller status
has changed from ready to processing during OpScan (executed every 100ms).
d. Real-time events (after ID26): For example, ID27 (Home) is issued when the controller is ready
for home searching.
To export the records, you need to use the data backup function (only Machine Backup (MB) provides this
record). After decompressing the backup data exported from the controller, the DataLog0.dat or DataLog1.dat
in the DataLog folder will be the records of the data log reader.
The data backup path for each controller model is as follows.
1. ARM system (6/11/21)
• 8 key: F5 Maintain > F6 Backup Sys.
• 5 key: F5 Maintain> F10 Next > F1 Backup Sys.
2. x86 system (SUPER/10/20)
• 8 key: F7 Diag. > F8 System manager > F2 Backup Sys.
• 5 key: F10 next > F2 Diag. > F10 next > F5 System manager > F2 Backup Sys.
Controller Software Version after 10.116.16 Controller Software Version before 10.116.16
Download
• Please go to SYNTEC official website → Downloads → Application Tool, and download
"OKLogReader_[V].zip".
Examples
• KLog-Find Event
• An Event will usually contain multiple Arguments. If you want to sort by event, follow these
steps:
1. Select "1st item of the EVENT" in the filter criteria, then the first information of each event
will be listed.
2. Click on the row in the right list, the left list will switch to the same row as well.
Since the left list shows all the information, you can see all the information of that event.
b. Click on the row in the right list, the left list will switch to the same row as well.
Since the left list shows all the information, you can see all the information of that event.
Controller Software Version after 10.116.16 Controller Software Version before 10.116.16
Download
File Interpretation
• Put the record and the converter into the same folder (please download the converter from the
"Development File Download" section), and execute the converter. Then type in that folder path,
and press enter to start the conversion. You can see the text file DataRecord.txt in the folder after it
is finished.
Content Descriptions
• There are five kinds of retrieved data separated by commas. And each line represents a separate
piece of information. The format is shown below. And the following section will explain the content
of each category.
• Event time: The event time obtained by OKLogReader, which is the same as the time
reported by the client regardless of the time zone where the OKLogReader and the
controller is located.
• Event ID: The status of the controller at that moment, from which you can understand what
the machine is doing at that time.
• Data Type: The type of data, so that you can determine what kind of data it is.
• Data content: The recorded data.
Event List
7 Axis ID Motor
Feedback
0 Axis ID Machine
Coordinat
e
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
93 System Boot 6
94 System Running 6
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
7 Axis ID Motor
Feedback
Notes:
1. Axis group ID will display the data of the corresponding number and ID according to the "number
of enabled axis group".
2. Axis ID will display the data of the corresponding number and ID according to the "number of
enabled axis".
3. The unit of coordinates is "BLU".
Examples
Here are several examples to explain the meaning of the data. For detailed definition of the data, please
refer to the table "Time and Data Recorded by the Data Log Reader".
• 2014/2/5/20:0:29.479;21,0,2,-15804
Red: 8:00 p.m. 29.479 seconds, February 5, 2014.
Blue: the event ID is 21, which means to start processing.
Green : the data type is 0, which means the following data are "Axis ID, Coordinate".
• 2014/2/5/20:0:29.479;21,0,2,-15804
Red: the data type is 0, which means the following data are "Axis ID, Machine Coordinate".
Blue: the axis name 2 represents Y-axis, and the machine coordinate is -15.804.
• 2014/2/5/20:0:29.479;21,1,1,1,1,0
Red: the data type is 1, which means the following data are "Axis Group, Workpiece Coordinate, Axis
ID, G54 Setting Value".
Blue: they are the 1st axis group, the 1st Workpiece coordinate, X-Axis, and setting value is 0.
• 2014/2/5/20:0:29.479;21,2,1,1,50000
Red: the data type is 2, which means the following data are "Axis Group, Axis ID, External Offset".
Blue: they are the 1st axis group, X-Axis, and external offset is 50.
• 2014/2/5/20:0:29.479;21,1,1,1,1,0
Red: the data type is 1, which means the following data are "Axis Group, Workpiece Coordinate, Axis
ID, G54 Setting Value".
Blue: they are the 1st axis group, the 1st Workpiece coordinate, X-Axis, and setting value is 0.
• 2014/2/5/20:0:29.479;21,7 ,2,-15804
Red: the data type is 7, which means the following data are "Axis ID, Motor Feedback".
Blue: the axis name 2 represents Y-axis, and motor feedback is -15.80.
• 2014/2/5/20:0:29.479; 30,3,1,1,50
Red: the event ID is 30, which means G92 Setting.
Blue: the data type is 3, which means the following data are "Axis Group, Axis ID, G92 Offset".
Green: they are the 1st axis group, X-Axis, and offset is 0.05.
1.2.5 QA
Q1. Why does the time displayed differ from the one in controller alarm history or operation log when reading
DataLog*.dat with a data log reader (hereinafter called Reader), such as "TransferDataRecords v2.1" or
"OKLogReader_2.0.2"?
A1: There is a time zone difference between each controller software version and Reader. The following table
shows the relationship between each version.
A 10.116.6D ~
10.116.10A ~
10.116.16A ~
10.116.24A ~ 10.116.24L
B 10.116.24M ~
10.116.38A ~ 10.116.38F
10.116.54A ~ 10.116.54D
10.118.0A ~10.118.0B
C 10.116.38G ~
10.116.54E ~
10.118.0C ~
Time zone When the controller is rolled out, it is set to Suppose the computer using Reader is in
Taiwan time zone UTC+8 which users cannot Taiwan, the time zone is UTC+8.
change.
A When the time zone of Reader's computer is UTC+N, the When the time zone of Reader's
display time will be "N hours ahead" of the time computer is UTC+N, the display time
recorded by the machine. will be identical to the time recorded
by the machine.
E.g. The same DataLog0~2.dat is 8 hours ahead of the
machine recorded time in Taiwan and 5 hours behind in E.g. The DataLog0~2.dat will display the
New York. Because the time zone of Taiwan is UTC+8, and same time with the machine recorded
New York is UTC-5. time regardless of the time zone.
Related issue ISSUE-1493 Related issue MMI-3310
B When the time zone of Reader's computer is UTC+N, the When the time zone of Reader's
display time will be "8+N hours ahead" of the time computer is UTC+N, the display time
recorded by the machine. will be "N hours ahead" of the time
recorded by the machine.
E.g. The same DataLog0~2.dat is 16 hours ahead of the
machine recorded time in Taiwan and 3 hours ahead in E.g. The same DataLog0~2.dat is 8
New York. Because the time zone of Taiwan is UTC+8, and hours ahead of the machine recorded
New York is UTC-5. time in Taiwan and 5 hours behind in
New York. Because the time zone of
Related issue ISSUE-7228
Taiwan is UTC+8, and New York is
UTC-5.
Related issue MMI-3310
C When the time zone of Reader's computer is UTC+N, the When the time zone of Reader's
display time will be "N hours ahead" of the time computer is UTC+N, the display time
recorded by the machine. will be identical to the time recorded
by the machine.
E.g. The same DataLog0~2.dat is 8 hours ahead of the
machine recorded time in Taiwan and 5 hours behind in E.g. The DataLog0~2.dat will display the
New York. Because the time zone of Taiwan is UTC+8, and same time with the machine recorded
New York is UTC-5. time regardless of the time zone.
Related issue ISSUE-11215 Related issue MMI-3310
Q2. Why is the DataLog*.dat which is backed up with the latest controller software version 10.116.24 not
updated or empty?
A2:
• The data log reader function is disabled in versions 10.116.16K (inclusive) ~ 10.116.24/10.116.26.
• It is re-enabled after 10.116.36, and the specification of machine coordinate record in processing is
changed from writing every second to writing once every 10 minutes. And if an MOT alarm is triggered
during the 10-minute period, it will compulsorily write the data to ensure that important information is
recorded.
1.3.1 Purpuse
IOLog can record the change of input/output signal 8 second before the alarm occurs. It can be used to determine
the cause of the problem.
Supported version: 10.118.44C, 10.118.46C, 10.118.48N, 10.118.52H, 10.118.56B, 10.118.57 and after.
Note: The IOLog will record data when below alarm happend.
The alarm trigger recording
1. MOT-008 Loss Pulse
2. MOT-087 Inaccurate stop position. Please check if there are any mechanisms are stuck
3. MOT-019 Following error exceed
4. MOT-023 Fatal following error exceed
5. AL-120 Driver Over Current
6. AL-121 Power Module Failure
7. AL-202 Overload
8. AL-203 Over Torque 1
9. AL-521 Excessive Following Error
10. OP-005 I/O transmission error (Note)
11. SYS-041 RIO1 communication error (Note)
12. SYS-042 RIO2 communication error (Note)
Note: Supported version - 10.118.72I, 10.118.82T, 10.118.86M, 10.120.4V, 10.120.12T, 10.120.16M,
10.120.24C, 10.120.28 and after
Remark: If the IOLog is opened via "Open file", the IOLogForm will open directly. If you open IOLog via "Open
MB/SB", please click "View>IOLog" to open IOLogForm.
4. The IOLog display window is as follows, the upper left is the drop-down menu, which will display the IOLog
files that can be opened. If the IOLog is opened via "Open file", only one file will appear.
After selecting the IOLog file you want to open from the drop-down menu, click "Display Settings", the
DisplaySettingsForm will pop up, and the basic information of selected IOLog will be shown on the upper
right panel.
Among them, the Input and Output are the number of I/O points recorded in the IOLog data. This number is
not always equal to the number actually used, but will be greater than or equal to the number actually used;
The Interval is the scanning time of the IO point; the Num. of Rec. is the total number of data recorded at the
same point;
The Start Rec. Time is the time when all data are started to be recorded, and the Elapsed time at the bottom
of the graph is based on the Start Rec. Time.
2.1 Preface
With the development of industrial evolution, cloud intelligent network, remote monitoring becomes one of the
essential functions of the controller, to meet the diverse customer demand, this manual will introduce the remote
monitoring applications in SYNTEC's controller and related information.
(Fig.1)
Description
1. Each controller has individually physical IP
2. Server can connect directly to controllers via IP
2.3.1 Specifications
1. SYNTEC controller using WinCE system
2. Software version 10.114.30 (or later)
S098 OCAPI Server is Running S098 is true when OCAPIServer is enabled, S098 is false
when OCAPIServer is disabled.
S099 Dipole connection in use Whether Dipole connection is used, S099 displays 1 if
there is monitoring program connecting to Kernel. If not,
S099 displays 0.
Before using this software, please setup SYNTEC CNC monitor first(Ladder Editor, MarcoDev, Cncmon32, it is
suggested to use version 10.114.56,10.116.0 or later)
Fig.6: List
Optional display contents
Monitor Mode
User can open monitor mode when cncView has more than two pages, it shows each page.
Notice:If remoteAP always shows " connecting..", you can close firewall or open 5568 and 5570 port in order to let
PC connect to CNC
Feature Overview
Machine Infor
File transfer
Work record
Alarm Infor
Notify Alarm
Can send Prompts/Alarm to manager when alarm appears via Pipeline notification set on the alarm setting screen.
Pipeline notification-Mobile
Pipeline notification-Email
Pipeline notification-Skype
Method:
1. Install SKYPE in the PC Remote Monitoring Application installed, and login account A
2. Allow account A enable other process access in SKYPE advanced setting
Pipeline notification-QQ
Report table
Report table will synchronously display all machining information of each controller. Display information can be
defined by user (refer to "display content of report table"),
Authority Management
Admin can manage all of users' right of view page
New specifications:
• Support for user records( permission management, version 10.118.12G and later )
• Record generation time point
There are unrecorded cumulative workpieces that satisfy the following conditions
a. Profile change
b. The number of required workpieces reaches
c. Operator change
Figure 4 Template
Group STD_MACHINE_GROUP_MONITOR
• Customized content: Beginning with R (if value R is a string format, it is required to add ",
STR", otherwise it will be considered a digital display. ).
• String display on remote monitoring software: shown as right hand side (not support multi
language)
P.S. The display order on remote monitoring soft is according to the order of SETTING.INI.
Group STD_MACHINE_GROUP_MONITOR
IP STD_MACHINE_IP_FIELD
Customized method
2. Do one function key (OK). Once function key is activated, the value of R3510 will be filled into R4010(self-
defined action "CUSTOMDEVSTR")。
3. Fill the value of R4010 into work record of employee. Copy the Schema
file(StdMMIRes\Common\Schema\Schema_WorkRecord.xml) to the OCRES path (OCRes\Common\Schema)
to customize. Add the below content:
<Field>
<Name>Col_User</Name>
<InputFormat>String</InputFormat>
<Length>20</Length>
<Storage>R4010</Storage>
</Field>
4. Do one function key (LOG OUT). Once activated can do following action
• action "DoAddWorkRecord",
• Clear R4010.
Above function can be used to do the log out key that can write current part count into the work record table
(including employee ID).
=============================================================
However, there are two cases have not yet considered.
1. Syntec's controller will automatically update the work record table when one of below condition is satisfied:
• Condition 1: Total required part is completed (system updates automatically)
• Condition 2: Part count is unequal to zero and change machining program (system updates
automatically)
It is needed to avoid system update automatically and rewrite problem when employee selects logout
button
2. Previous employee forgets to log out, so when the next one logs in, it can update the work record table.
According to 2 above case, it is needed to use prediction as below (in this case, using PLC with HMI button and
R5998)
HMI HIM
PLC
R3800 = 1(Log in) R6800 = 0(Required part is not reached R5998 Corresponding action of R5998
R3800 = 2(Log out) R6800 = 1(required part is reached)
refer to note 1”Require Part Count Reached”
1 0 1 1. DoAddWorkRecord
2. Set R5998= 0
3. Set Part count 0
1 1 3 1. Set R5998=0
2. Set Part count 0
2 0 2 1. DoAddWorkRecord
2. Set R5998= 0
3. Set Part count 0
4. Set R4010= 0
2 1 4 1. Set R5998= 0
2. Set Part count 0
3. Set R4010= 0
S034 Require Part Count Reached When required part is reached, this S FLAG is ON.
Once Cycle Start or Reset, this FLOG is OFF
To meet the demand of remote monitoring application from customer, SYNTEC provides open library, development
files and examples. User can visit SYNTEC website to download related data.
Path: DOWNLOADS -> CNC Software -> Open CNC Tools -> SYNTEC Remote CNC monitor.
New specifications:
• Support for user records( permission management, version 10.118.12G and later )
• Record generation time point
There are unrecorded cumulative workpieces that satisfy the following conditions
a. Profile change
b. The number of required workpieces reaches
c. Operator change
Figure 4 Template
3.1 Preface
3.2 Requirement
3.3 Caution
3.4 Contents
1. Bin folder:The executable and DLL files are stored in the folder.
2. SBBackup folder:The output backup file will be stored in the folder. The backup file is named
"Backup_SB_CRC code.zip", e.g. Backup_SB_3a6b72b7.zip.
3. SBRestore folder:The input restore file needs to be stored in this folder.
4. SBBackup.bat:You can double-click the file to perform SB backup.
5. SBRestore.bat:You can double-click the file to perform SB restore.
6. IP.txt:It's a file for setting the IP address.
1. Result.txt:
The file is generated after SB backup or restore is completed.
If performed successfully, the content of this file will be "SB Backup (Restore) Successful".
Otherwise the content will be "SB backup(Restore) Fail".
2. Error.txt:
This file is generated only when SB backup or restore fails, and error messages will be recorded.
3.5 Procedure
Here is an illustration of the path of the SBtool. Place the SBtool folder in the same directory as the
DiskC folder.
Execute SB backup:
1. Double-click SBBackup.bat, and wait for the percentage finish.
Then the screen will display "SB Backup complete!", indicating that the execution is complete.
Execute SB restore:
1. Put the SB backup file under the SBTool\SBRestore folder.
2. Double-click SBBackup.bat, and wait for the percentage finish.
Then the screen will display "SB Restore complete! Please restart CNC".
3.6 Troubleshooting
If the screen displays red error messages and Error.txt is generated, please refer to the following
troubleshooting methods:
• 「Fail to get IP」:
This means that the IP address in DipoleSettings.xml or IP.txt cannot be read. Please refer to the "
Set IP address " above to reset IP and also check whether the IP format is correct.
If you re-enter the IP directly on the screen, SBTool will automatically reconnect and save the new
IP to IP.txt.
• 「Fail to connect to CNC」:
Please check the CNC network status or check whether the IP is correct.
If you re-enter the IP directly on the screen, SBTool will automatically reconnect and save the new
IP to IP.txt.
• 「SB Backup Fail」:
This means that the CNC rejected the backup request, which may be caused by the busy CNC, or
SBTool was mistakenly closed during the last execution (Please restart the CNC).
• 「SB Restore Fail」:
This means that the CNC rejected the restore request, which may be caused by the busy CNC,
or SBTool was mistakenly closed during the last execution (Please restart the CNC).
• 「SB Restore Fail: Please check Restore folder.」:
Please make sure that only one file exists in the SBRestore folder.
• 「SB Restore Fail: CRC check error」:
Please make sure the CRC code of the file name is correct.
4.1 Catalog:
Catalog:
Introduction:
Specifications:
User guide:
Constraints:
Notifications:
4.2 Introduction:
Currently, the Data Logs and Operation Logs play great roles in providing information on system status and
user operations by routine recording. When it comes to issues about troubleshooting, behavior tracking, or
long term reliability analysis, it seems nothing to do with these two recorders. It's also infuriating that analysts
have to tell the key information from massive amounts of the data files by files.
The brand new Data Aggregators make great improvement of the disadvantages above and aim for the
following three subjects.
Under specific critical alarms, such as the loss pulse alarm(MOT-8) and motor overload alarm(AL-202), the
CNC machine would execute an emergency stop, and break the machining process instantly. It might be
helpful to analyze the history of data like machine position, loading factor of motors, following errors, etc.
This information can help our erecognize machine behavior and furtherly solve the problem.
4.3 Specifications:
• These data aggregators would persist in acquiring the monitoring data as long as the controller is running
and keep the data histories for a period of time.
• For different purposes, the data aggregators have a variety of settings with each other. The following
paragraph will show you the configurations of the three different data aggregators.
• The following table contains the monitoring data of an alarm data aggregator(4~6Axis):
No. Target Channel Target Data Source Interpretation
5 1st Spindle Power Stage Main Drive Status Monitoring The drive must
Capacitance Variable No.DB0 support an MCU of the
Temperature Power Stage
Capacitance.
7 1st Spindle Encoder External_1 Drive Status Monitoring Syntec Encoder only.
Temperature Variable No.D62
8 1st Spindle The 5V Detection of Drive Status Monitoring Syntec Encoder only.
1st Encoder Variable No.D70
• The data of the same date would get exported to the same record, by appending the data to the end of
previous data.
And a new record will be created when there is no file of the same date.
Both of the situations will the aggregator edits the time stamp on the file name by the recording time of
the last data.
• The error record includes no data info but the error message. It might overwrite the previous record of
the same date.
Monitoring Data:
• The following table contains the monitoring data of a daily data aggregator.(V1.1)
Software version: from 10.118.32I, 10.118.40M, 10.118.41M
No Target Target Data Source Interpretation Limitation
. Channel
7 1st Axis Power Stage Main Drive Status The drive must
Capacitance Monitoring support an MCU of
Temperature Variable No.DB0 the Power Stage
Capacitance.
8 1st Axis Power Stage Main Drive Status The drive must
Capacitance Monitoring support an MCU of
Temperature Variable No.DB0 the Power Stage
Capacitance.
Directory FileName
MB\BackupOnly\Syntec FileName_MMDDhhmm.csv
MM: Month DD: Day
• \Alarm: alarm
hh: hour mm: minute
record(1~3Axis)
• \Alarm456: alarm for example:
record(4~6Axis) 。Alarm_0510093029.csv ( the time in the alarm(1~3Axis) file name
• \Service: will be recorded down to second )
service record
。Alarm456_0328164633.csv ( the time in the alarm(4~6Axis) file
• \Daily: daily
name will be recorded down to second )
record
。Service_05101730.csv
。Daily_05102359.csv
• Keep up to 10 files for each directory. Overwrite when the file name is the same.
• A guide to retrieve records from the controller and analyze by the tool: Syntec Analytics.
Steps Interpretation
Step 1. a. Run the Syntec Back-up System function to retrieve the records.
Path:【System Admin.】 → 【Backup Sys.】
Retrieve Machine Backup
b. The entrance page of the Syntec Back-Up System is
(MB)
shown below.
You can select the Syntec standard backup or a customized one
for different purposes.
It should be noticed that the records of data aggregators are
categorized as Auto-Backup Information,. That is to say, no
matter which option is chosen, the records would get backed up
as long as the backup process starts.
c. For quick back-up progress, you can choose only a few options.
Such as the History Alarms, OP Log, Diagnosis Log, or Maker Info
would be good choices.
Steps Interpretation
Step 2. a. Unzip the backup file, and you would get an overview of the
directory as shown below.
Find the records in the
The BackupOnly folder contains the records of data aggregators.
Backup.
Steps Interpretation
c. For example, try to find a daily record by the date in which we are
interested.
The records have the timestamp of recording on its name, so it's
Step 3. With the Syntec Analytics - oscilloscope tool, we can import the record
directly into the oscilloscope and make the line chart easily.
Analyze the record.
For more oscilloscope operating details, you can visit Syntec Analytics
- Oscilloscope.
※ Syntec Analytics does support the data aggregators records
interpretation from the version 2.1.16.
The version should be checked first before performing data analysis
by Syntec Analytics.
4.5 Constraints:
• Supported Controller Version: 10.118.23X, 10.118.28L, 10.118.36, and later.
• Supported Alarm record(4~6Axis) with Controller Version: 10.118.48P, 10.118.52J, 10.118.56D, 10.118.58 and
later.
• Drive Status Monitoring Variables are ONLY supported for Syntec M3 Drives.
That is to say, these variables cannot be retrieved with non-Syntec M3 Drives, and WILL always be 0 on
record.
4.6 Notifications:
• Due to limited communication bandwidth, Drive Status Monitoring Variables may not be retrieved
correctly under certain circumstances, as listed below. In such cases, data loss is recorded.
• Display Page - Fast Diag.-Axes Data -Drive comm.
• Drive Firmware update: The controller will disconnect with the drive after updating the drive
firmware, causing the Drive Status Monitoring Variables to be unavailable. A reboot is required to
regain access to Drive Status Monitoring Variables.
• Encoder Firmware update
• Encoder-related Tuning Function
• Error condition:
Up to this time, data aggregators neither have a diagnosis page nor notify runtime errors intuitively. But
there are still two fatal errors that might put the control system at risk.
Therefore, when these errors show up, data aggregators would write the error message and temporarily
inhibit themselves from exporting.
• Insufficient disk space( less than 1MB )
Before aggregators export data recorded to files, they will check the free space of the target disk first.
The aggregators will overwrite the record with an error message and inhibit the following record
exportation on the same date only if they meet the low disk space problem.
Error message: "Export Record Fail: Insufficient disk space. ( less than 1 MB )"
• Insufficient physical memories ( less than 30 MB )
At the startup of the controller, a memory protection process would be executed first before building
the data aggregators in case of running out of memories.
Once the memory lackage happened, the data aggregators will export an error message individually
and stop running until the system reboots.
Error message: "Register Kernel Scope Fail: Insufficient memory. ( less than 30 MB )"
Steps Interpretation
Step 1. 1. Run the Syntec Back-up System function to retrieve the records.
Path:【System Admin.】 → 【Backup Sys.】
Retrieve Machine Backup
2. The entrance page of the Syntec Back-Up System is shown below.
(MB)
You can select the Syntec standard backup or a customized one for different
purposes.
It should be noticed that the records of data aggregators are
categorized as Auto-Backup Information,. That is to say, no matter which
option is chosen, the records would get backed up as long as the backup
process starts.
3. For quick back-up progress, you can choose only a few options. Such as the
History Alarms, OP Log, Diagnosis Log, or Maker Info would be good choices.
Steps Interpretation
Step 2. 1. Unzip the backup file, and you would get an overview of the directory as
shown below.
Find the records in the
The BackupOnly folder contains the records of data aggregators.
Backup.
2. Push to the directory: BackupOnly\Syntec, and you would find four folders,
named ( 1 ) Alarm ( 2 ) Service ( 3 ) Daily ( 4 ) Alarm456. Each of them
contains the records of the four data aggregators with the same name.
Steps Interpretation
3. For example, try to find a daily record by the date in which we are interested.
The records have the timestamp of recording on its name, so it's easy to find
Steps Interpretation
Step 3. With the Syntec Analytics - oscilloscope tool, we can import the record directly
into the oscilloscope and make the line chart easily.
Analyze the record.
For more oscilloscope operating details, you can visit Syntec Analytics -
Oscilloscope.
※ Syntec Analytics does support the data aggregators records
interpretation from the version 2.1.16.
The version should be checked first before performing data analysis by
Syntec Analytics.
1. Title Bar
Show the software name and whether it has been saved after modification (indicates by star sign)
2. Function Bar
Currently provide saving function only
3. Edit Area
The alarm no. and its corresponding string can be edited here
4. Status Bar
Display the current status of the data, such as "Pencil: Line being edited", "Star sign: Newline", "Arrow:
Selected line"
5.1.2 Function
Modification
Method 1: After clicking any field, input the string directly (it's more convenient to click once only)
Method 2: After double-clicking any field, enter the string (the edit cursor will appear, which is more intuitive)
Click the status bar, the line will be highlighted, and it will be removed after pressing "Delete"
Save File
If there is a blank field, a prompt window will pop up and the file will not be saved
5.1.3 Suggestion
The standard/customized Macro alarm no. range has not yet been specified.
In order to avoid the conflict between the customized no. and the standard no., it is recommended that the
user set the number to "10001~20000" while setting.
5.2.2 Environment
No restrictions
When using the customized command set (Macro) function through SI for the first time, this software will be
installed through SI, no need to do that by yourself.
This software must be operated with SI and is not valid when using alone (meaning double-click
MacroEditor.exe by yourself).
If used alone, there will be no file loading function.
• Introduction
• Notes
• Execution Environment Requirements
• Operation
• Step 1. Download
• Step 2. Insert the software installation pack
• Step 3. Plug the USB into the controller and power on
• Initialize file content
• Log file
• Troubleshooting
6.1 Introduction
• This tool can automatically execute by plugging in the USB. It can initialize the controller and reset
related settings.
• This tool will format DISKC/DISKA, initialize Windows Registry, and remove all customized developing
files (PLC/Parameters...).
• This tool does not have built-in software installation package. The package of the corresponding
controller must be installed before use, and the recommended software version is 10.116.24Z.
6.2 Notes
• Please do not remove the USB while the tool is running, this action will cause serious damage to the
system.
• If an unexpectedly power failure occurs, user can first try to plug in the USB to reboot. The system will
try to continue the initialization operation. However, if an abnormal things occurs and the tool
cannot operate, please send the controller back to Syntec and attach the Log file of the AutoInit folder
in the USB.
• The software installation pack is to provide tools to automatically determine the version during
execution and to install automatically.
• Please make sure that there is only one installation pack in the AutoInit folder before plugging in
the USB to avoid system exceptions.
• AutoInitializer is a disposable tool, please download and use it again after use; otherwise, it will cause
problems such as the failure of the panel shortcut keys.
6.4 Operation
Unzip the installation pack to the USB, and the files in your USB are as shown in the figure below:
Please go to the official website to download the installation pack of the corresponding model
• Link: http://www.syntecclub.com/Download.aspx
6.4.3 Step 3. Plug the USB into the controller and power on
Please plug the USB into the controller before power off, this tool will execute automatically.
Initialize (automatically)
• After the controller is initialized, the files in DiskA / DiskC will be removed and put into the files needed
for system operation.
The following is the description of some of the inserted files.
• Ladder
• Site: AutoInit\Data\DiskC\OpenCNC\Ladder\Cnc.lad
• Source: Ladder of the company's products before shipment
• Parameter file
• Site: AutoInit\Data\DiskC\OpenCNC\Data\param.dat
• Source: 21MA product parameter default, and set "axis board no. corresponding to X
axis" to 1 (Pr21=1)
• The number of function key is restored to five keys
• If user wants to restore the customized parameter file/ladder after initialization, you can change the file
according to the above site.
• Notes:
• Replace the ladder/parameter file for initialization by yourself, please strictly confirm the
correctness of the source file, otherwise it will cause serious problems such as unable to turn on
the controller.
(If the above problem occurs after the operation, user can use the initialization tool without any
replacement to try to initialize the system again)
• Valid version: AutoInitializer_1.0.2
• When this tool is executed, the Log file will be generated in the AutoInit folder in the USB
• Log file name: serial number_Log.txt
• Content:
• Execution time
• Execution details
• Record of execution mistakes
• Record of controller related information
Title Chinese
OS 作业系统
CPU 处理器
platform 平台
Serial number 序号
Maker ID 机械厂代码
NK Version 映像档版本
• Example:
Click to expand
6.7 Troubleshooting
• If the following screen appear during installation, please refer to the table below for possible
troubleshooting methods
CPU type not support Please confirm whether the CPU of the
controller is the supported type (am35x,
am335x, am3354)
Note: For more information, please open the
AutoInit folder in the USB and refer to the internal
Log file.
The CNC model of the Please check whether the installation pack in
the USB matches the CNC model
installation pack does
Note: For more information, please open the
not match
AutoInit folder in the USB and refer to the internal
Log file.
The machine type of the Please check whether the installation pack in
the USB matches the machine type
installation pack does
Note: For more information, please open the
not match
AutoInit folder in the USB and refer to the internal
Log file.
CNC Machine Module Please make sure that the USB has been
removed
is missing
Note: For more information, please open the
AutoInit folder in the USB and refer to the internal
Log file.
CNC Machine Type is Please make sure that the USB has been
removed
missing
Note: For more information, please open the
AutoInit folder in the USB and refer to the internal
Log file.
Content
• Introduction
• Notes
• Execution Environment Requirements
• Operation
• Step 1. Download
• Step 2. Insert the software installation pack
• Step 3. Plug the USB into the controller and power on
• Initialize file content
• Log file
• Troubleshooting
6.8.1 Introduction
• This tool can automatically execute by plugging in the USB. It can initialize the controller and reset
related settings.
• This tool will format DISKC/DISKA, initialize Windows Registry, and remove all customized developing
files (PLC/Parameters...).
• This tool does not have built-in software installation package. The package of the corresponding
controller must be installed before use, and the recommended software version is 10.116.24Z.
6.8.2 Notes
• Please do not remove the USB while the tool is running, this action will cause serious damage to the
system.
• If an unexpectedly power failure occurs, user can first try to plug in the USB to reboot. The system will
try to continue the initialization operation. However, if an abnormal things occurs and the tool
cannot operate, please send the controller back to Syntec and attach the Log file of the AutoInit folder
in the USB.
• The software installation pack is to provide tools to automatically determine the version during
execution and to install automatically.
• Please make sure that there is only one installation pack in the AutoInit folder before plugging in
the USB to avoid system exceptions.
• AutoInitializer is a disposable tool, please download and use it again after use; otherwise, it will cause
problems such as the failure of the panel shortcut keys.
6.8.4 Operation
Step 1. Download
Unzip the installation pack to the USB, and the files in your USB are as shown in the figure below:
Please go to the official website to download the installation pack of the corresponding model
• Link: http://www.syntecclub.com/Download.aspx
Please plug the USB into the controller before power off, this tool will execute automatically.
Initialize (automatically)
• After the controller is initialized, the files in DiskA / DiskC will be removed and put into the files needed
for system operation.
The following is the description of some of the inserted files.
• Ladder
• Site: AutoInit\Data\DiskC\OpenCNC\Ladder\Cnc.lad
• Source: Ladder of the company's products before shipment
• Parameter file
• Site: AutoInit\Data\DiskC\OpenCNC\Data\param.dat
• Source: 21MA product parameter default, and set "axis board no. corresponding to X
axis" to 1 (Pr21=1)
• The number of function key is restored to five keys
• If user wants to restore the customized parameter file/ladder after initialization, you can change the file
according to the above site.
• Notes:
• Replace the ladder/parameter file for initialization by yourself, please strictly confirm the
correctness of the source file, otherwise it will cause serious problems such as unable to turn on
the controller.
(If the above problem occurs after the operation, user can use the initialization tool without any
replacement to try to initialize the system again)
• Valid version: AutoInitializer_1.0.2
• When this tool is executed, the Log file will be generated in the AutoInit folder in the USB
• Log file name: serial number_Log.txt
• Content:
• Execution time
• Execution details
• Record of execution mistakes
• Record of controller related information
Title Chinese
OS 作业系统
CPU 处理器
platform 平台
Serial number 序号
Maker ID 机械厂代码
NK Version 映像档版本
• Example:
Click to expand
6.8.7 Troubleshooting
• If the following screen appear during installation, please refer to the table below for possible
troubleshooting methods
CPU type not support Please confirm whether the CPU of the
controller is the supported type (am35x,
am335x, am3354)
Note: For more information, please open the
AutoInit folder in the USB and refer to the internal
Log file.
The CNC model of the Please check whether the installation pack in
the USB matches the CNC model
installation pack does
Note: For more information, please open the
not match
AutoInit folder in the USB and refer to the internal
Log file.
The machine type of the Please check whether the installation pack in
the USB matches the machine type
installation pack does
Note: For more information, please open the
not match
AutoInit folder in the USB and refer to the internal
Log file.
CNC Machine Module Please make sure that the USB has been
removed
is missing
Note: For more information, please open the
AutoInit folder in the USB and refer to the internal
Log file.
CNC Machine Type is Please make sure that the USB has been
removed
missing
Note: For more information, please open the
AutoInit folder in the USB and refer to the internal
Log file.
7.1 Introduction
• This USB tool automatically backs up the data in the controller when it is powered on, and for
situations without a screen, it can be backed up and removed through this tool.
Item Other
2 Ladder \DiskC\OpenCNC\Ladder\cnc.lad
7 Profile \DiskA\OpenCNC\NcFiles
7.3.3 STEP3. Plug the USB into the controller and power it on for backup
• The backup will be done automatically after you plug in the USB and turn on the controller
• When the following screen is displayed, it means the backup operation is finished, please remove the
USB and reboot the controller
• A Backup folder will be created in the USB, which will have a folder named according to the serial
number, and all the backup files will be placed in this folder
Introduction
• Function:USB Backup backup tool, it will backup according to the content in the configuration file
USB_BackupConfig.xml
Content
• The default standard configuration files are as follows, as well as the contents of the backup items
provided in the upper part of the chapter
USB_BackupConfig
<Config>
<BackupFile>
<SourcePath>\DiskC\OpenCNC\Data\Param.dat</SourcePath>
<TargetPath>Param.dat</TargetPath>
</BackupFile>
<BackupFile>
<SourcePath>\DiskC\OpenCNC\Ladder\cnc.lad</SourcePath>
<TargetPath>cnc.lad</TargetPath>
</BackupFile>
<BackupFile>
<SourcePath>\DiskC\OCRes\Common\Image\SB_logo.bmp</SourcePath>
<TargetPath>SB_logo.bmp</TargetPath>
</BackupFile>
<BackupFile>
<SourcePath>\DiskC\Bootcepc.bmp</SourcePath>
<TargetPath>Bootcepc.bmp</TargetPath>
</BackupFile>
<BackupFile>
<SourcePath>\DiskA\OpenCNC\User\Registry.dat</SourcePath>
<TargetPath>Registry.dat</TargetPath>
</BackupFile>
<BackupFolder>
<SourcePath>\DiskC\OCRes</SourcePath>
<TargetPath>OCRes</TargetPath>
</BackupFolder>
<BackupFolder>
<SourcePath>\DiskA\OpenCNC\NcFiles</SourcePath>
<TargetPath>NCFiles</TargetPath>
</BackupFolder>
</Config>
• The USB Backup tool will perform a software backup of the above text. For additional backups, please
refer to the following section
• Notice
• For arm series backup boot file, <SourcePath> is the same as x86, write \DiskC\Bootcepc.bmp
Backup to file
If the element value is
<TargetPath>
Param.dat </
TargetPath>
Backup to folder
If the element value is
<TargetPath>
NcFiles </
TargetPath>
Log introduction
This file records basic information of the controller and the backup contents and results during backup.
• File Name:Serial No..txt
• File Location: USBDisk\Backup\Serial No.\Serial No..txt
Log content
• After downloading and unzipping the USB Backup, the configuration file "USB_BackupConfig.xml" can
be found.
• Open "USB_BackupConfig.xml" with the text editor software
• To backup "files", add the following XML content to the USB_BackupConfig.xml file, and fill in the
source of the files to be backed up in SourcePath and the target location to be backed up to the
USB\Backup\Serial No.\ folder in TargetPath
BackupFile
<BackupFile>
<SourcePath>the source of the files to be backed up in the controller</
SourcePath>
<TargetPath>target location to be backed up to the USB</TargetPath>
</BackupFile>
• To back up the "folder", add the following XML content to the USB_BackupConfig.xml file, and fill in the
source of the folder to be backed up in SourcePath and the target location of the folder to be backed up
to USB\Backup\Serial No.\ folder in TargetPath
BackupFolder
<BackupFolder>
<SourcePath>the source of the folder to be backed up in the
controller</SourcePath>
<TargetPath>the target location of the folder to be backed up to USB</
TargetPath>
</BackupFolder>
• Archive the file after editing, the following usage is as described in the section " Operation Method "
above.
• Valid Version: USB Backup v1.1.0
7.5.2 Examples
Backup config
<BackupFile>
<SourcePath>\DiskC\OCRes\Common\AppData\Test.xml</SourcePath>
<TargetPath>Test.xml</TargetPath>
</BackupFile>
<BackupFolder>
<SourcePath>\DiskC\OCRes\CHT\String</SourcePath>
<TargetPath>OCRes\StringTest</TargetPath>
</BackupFolder>
• After archiving, the backup will be completed as described in the previous section, as shown below
File: Folder:\DiskC\OCRes\CHT\String
\DiskC\OCRes\Common\AppData\Test.xml
7.6 Q&A
7.6.1 How do I troubleshoot the backup results that are not as expected?
1. Check the log in USB, the file name is controller serial number, the path is USB\Backup\Serial No.
\Serial No..txt
Take the following picture as an example
2. After opening the above file, check the Config Path Check in the second section for any errors.
a. If there are any errors, please refer to the error causes recorded below for troubleshooting
3. After checking the Config Path Check, check the results of the backup items below, if there is any item
with Backup Fail
a. Check the cause of the error after Backup Fail and troubleshoot the cause
Not exist <config> element, <config> does not exist in the • Check
please check USB_BackupConfig.xml USB_BackupConfig.xml,
USB_BackupConfig.xml and check <config> for
errors
Unknown element: xxxx The tag that does not meet the • Remove the tag that does
specification appears in the not conform to the
USB_BackupConfig.xml specification
Path error: Source Path is empty Source Path is empty • Fill in the source of the
backup item
Path error: Target Path is empty Target Path is empty • Fill in the destination of
the backup item
Path error: Source file is not Source file is not exist • Check if the file path of the
exist backup project is incorrect
Path error: Source folder is not Source folder is not exist • Check if the folder path of
exist the backup project is
incorrect
No item need backup No item need backup • Check if the backup profile
is empty
• Check if the backup profile
is in the wrong format
Backup Fail: Copy file error, xxxx Copy file error • Check if the configuration
file format is wrong
• Power off and restart to
confirm if the problem still
exists
Backup Fail: Create Folder error, Create Folder error • Check if the configuration
xxxx file format is wrong
• Power off and restart to
confirm if the problem still
exists
8.3 Instruction
The format of "Setting0.ini" is as follows:
ACTION=aaa
PARAMETER=ppp
EXT=eee
OPTION=yyy
EXE Execute the program of Parameter(ppp). If user wants to run a program *PARAMET
named CncMonCE.EXE, ER uses full
qualified
ACTION=EXE
path
PARAMETER=CncMonCE.EXE
<Notes>
1. "OPTION=yyy" is the newly added extended instruction format of 10.116.16G, 10.116.24, and 10.117.24.
2. If OPTION=REPEAT is set in Setting0.ini, Setting0.out will still be generated after the corresponding
command is executed, but the corresponding ACTION will still be executed next time when it is rebooted.
The regenerated log will still be written in Setting0.out, continuing with the last time log.
3. If OPTION=REPEAT is not set in Setting0.ini, the original specifications will be maintained, which means the
"Setting0.out" file will exist, and the "Setting0.ini" command will not be executed when booting.
Syntec Dipole function separates the human machine interface from the core (Figure 1 & Figure 2),
allowing users to control the back end controller via the Internet through front end applications (such as
standard human machine interface). Users can use this framework for remote monitoring and diagnosis.
The development environment of front end applications is no longer limited to Windows CE, and general
applications of Windows XP, Windows 7,... can be developed, creating unlimited possibilities.
This user manual teaches users how to install CNC simulation software to the front end Windows user
terminal, and start to use the functions of RemoteCNC one-to-many API.
9.1.2 How to set the controller to turn on Dipole through the human machine
interface
Servo setting is on the human machine interface FenuBar:(The interface will be slightly different from
different controller.)
1. F6 Parameter settings → F10 Next page→ F7 Core Server(Figure 3)。
2. F5 Maintain → F2 Internet settings → F5 Core server
This FenuBar function will open the "Core Server Setting Page" (Figure 4).
The following is the description of each parameter:
• "Whether to turn on the server when booting up" is whether to automatically activate the core
Dipole function when booting up.
• "Timeout" means that when the network has no response after this time, the network connection
will be disconnected.
After the user completes the core Dipole settings, pressing "F3 Confirm" to save the settings, or press "F4
Cancel" to recover the settings. After setting, the Dipole function will be automatically activated when next
time booting up.
9.2.1 Precautions
1. Please confirm the controller version first, and check the table below to find the corresponding
RemoteAPI version.
2. If you use the v1 version of RemoteAPI, please install the 32 simulation software MacroDev first, and
its version must same as the controller.
3. Syntec.OpenCNC.dll, Syntec.RemoteCNC.dll, Syntec.RemoteObj.dll, OCAPI.dll, OCUSER.dll... and
other dlls need to be placed in the same folder as the main program.
1. The computer firewall needs to turn on port 5568, port 5570 for the controller to connect to the
computer. "In Windows environment, you can go to Firewall> Advanced Settings> Input Rules> Add
Rule> Port> TCP> Input 5568,5570> Allow all the connections"
2. Note that the computer has two network interface cards, and adjust the priority of the card
connected to the controller to a higher level, so the connection can be made. "In the Windows
environment, you can go to Internet and Sharing Center> Enter to setting of changing the interface
card> Press F10 to show the toolbar> Advanced> Advanced settings> Adjust the priority of network
interface card to a higher level"
3. If you find that the network is unstable and an error message displayed while using v4 version,
please try to connect again after ten seconds.
4. If you found that Syntec.RemoteCNC.dll and Syntec.RemoteObj.dll are missing while using
1.0.12_v1 version, please go to the official website to download the 1.0.12_v1 again.
Note: If the above Windows operation appear error, please search for related settings by yourself.
10.116.36.x 1.0.12_v4
10.116.24.x 1.0.12_v3
V12
Data Type
Type Name Size
byte 8 bits
short 16 bits
int 32 bits
float 32 bits
string unlimited
-17 Protocol error (Ethernet Data from Ethernet Board is incorrect.Contact with the service
version only) section or the section in charge.
-16 Socket error (Ethernet Investigate CNC power supply, Ethernet cable and I/F board.
version only)
-15 DLL file error There is no DLL file for each CNC series corresponding to
specified node.
-7 Version mismatch between The CNC/PMC version does not match that of the library.Replace
the CNC/PMC and library the library or the CNC/PMC control software.
-2 Reset or stop request The RESET or STOP button was pressed.Call the termination
function.
1 Error(function is not Specific function which must be executed beforehand has not
executed, or not available) been executed.Otherwise that function is not available.
2 Error(data block length Check and correct the data block length or number of data.
error, error of number of
data)
12 Error(CNC mode error) The CNC mode is incorrect.Correct the CNC mode.
20 Error(Need to Update RemoteAPI version is too old for connected controller, need to
RemoteCnc Version) update RemoteAPI version.
Argument
variable name type [in/out] descriptions
N/A
Return Value True => there is an USB plugged in, False => there isn't an USB
plugged in
Argument
variable name type [in/out] descriptions
N/A
Argument
variable name type [in/out] descriptions
N/A
Argument
variable name type [in/out] descriptions
N/A
READ_information:Basic Information
Function Name short READ_information(…)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_status:Status Information
Function Name short READ_status(…)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_position:Coordinate Information
Function short READ_position(…)
Name
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_gcode:G Code
Function Name short READ_gcode(…)
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_spindle:Feedrate/Spindle Speed
Function Name short READ_spindle(…)
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_time:Time
Function Name short READ_time(…)
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_part_count:Number of Workpieces
Function Name short READ_part_count(…)
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_MakerConfigInfo:Machinery Information
Function Name short READ_MakerConfigInfo(…)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_alm_current:Current Alarm
Function Name short READ_alm_current(…)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
note The arrangement rule of the alarm array is from new to old.
The format of alarm message is("motion" "number"
"descriptions")
READ_alm_history:Alarm History
Function Name short READ_alm_history(…)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
note The arrangement rule of the alarm array is from new to old.
The format of alarm message is("motion" "number"
"descriptions")
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes
series return value descriptions model
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes The second array of Offset Data, with the title name (Length
Geom...).
Get the data start from the first tool.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes Start from the first tool, until finish writing all the offset.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
EXT 0
MPG Shift 1
G54 2
G55 3
G56 4
G57 5
G58 6
G59 7
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument type 1
variable name type [in/out] descriptions
Argument type 2
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
DOWNLOAD_nc_mem:Download NC program
Function Name short UPLOAD_nc_mem(…)
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_nc_freespace:Remaining Space(k)
Function Name short READ_nc_freespace(…)
Argument
variable name type [in/out] descriptions
Argument
variable name type [in/out] descriptions
Notes 1. 'Count' input the number of the log to be read, and returns
the number of log be read.
2. When the input parameter count is 0, all operation log will
be returned.
3. When a timeout error occurs, you can use the
SynetcRemoteCNC(ip,timeout) constructor to increase the
timeout. Timeout=0 means none, and the unit of timeout is
ms.
4. The OPLog returned can refer to the appendix for relevant
information
Note:If there is no Log, return the original array and write "No
Log".
This is NOT supported for V12.
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes ※ When the specified parameter number does not exist on the
controller or fails to read, ParamType will be set to -1
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes The number of input & output depends on the selected I/O card
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes The read value will be inputed in the array of PlcData(B,S,I). If the
number fails to be read, the array value will be set to null.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_plc_ver:PLC Version
Function Name short READ_plc_ver(…)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes: The system diagnostic variables 77 and 78 are specific
information of controller. For the remaining system memory, please
refer to diagnostic variable 7.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes:Only support the software version after 10.116.24x
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument N/A
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Note:Clear all the buffer (ex:series number, mainboard, model,
code, then call the related API to read the right data
READ_SSV_GetDeviceInfo
Function Name READ_SSV_GetDeviceInfo( ... )
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_ServiceReg
Function Name READ_SerialStateVar_ServiceReg(...)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_ServiceUnReg
Function Name READ_SerialStateVar_ServiceUnReg( int nHandle )
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_GetCapacity
Function Name READ_SerialStateVar_GetCapacity(...)
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_Dump
Function Name READ_SerialStateVar_Dump(...)
Argument
variable type [in/ descriptions
name out]
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_GetValue
Function Name READ_SerialStateVar_GetValue( ... )
Argument
variable type [in/ descriptions
name out]
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions.
Notes:After the update, the controller must be rebooted to
complete the update
9.14 Appendix
READ_nc_OPLog meaning
KeyPressed 0x0005
R 0x0020 Index
P 0x0021 Index
@ 0x0022 Index
L 0x0023 Index
D 0x0024 Index
K 0x0025 Index
Precautions
1. Please confirm the controller version first, and check the table below to find the corresponding
RemoteAPI version.
2. If you use the v1 version of RemoteAPI, please install the 32 simulation software MacroDev first, and its
version must same as the controller.
1. The computer firewall needs to turn on port 5568, port 5570 for the controller to connect to the
computer. "In Windows environment, you can go to Firewall> Advanced Settings> Input Rules> Add
Rule> Port> TCP> Input 5568,5570> Allow all the connections"
2. Note that the computer has two network interface cards, and adjust the priority of the card connected
to the controller to a higher level, so the connection can be made. "In the Windows environment, you
can go to Internet and Sharing Center> Enter to setting of changing the interface card> Press F10 to
show the toolbar> Advanced> Advanced settings> Adjust the priority of network interface card to a
higher level"
3. If you find that the network is unstable and an error message displayed while using v4 version, please
try to connect again after ten seconds.
4. If you found that Syntec.RemoteCNC.dll and Syntec.RemoteObj.dll are missing while using 1.0.12_v1
version, please go to the official website to download the 1.0.12_v1 again.
Note: If the above Windows operation appear error, please search for related settings by yourself.
10.116.36.x 1.0.12_v4
10.116.24.x 1.0.12_v3
Data Type
byte 8 bits
short 16 bits
int 32 bits
float 32 bits
string unlimited
-17 Protocol error (Ethernet Data from Ethernet Board is incorrect.Contact with the service
version only) section or the section in charge.
-16 Socket error (Ethernet Investigate CNC power supply, Ethernet cable and I/F board.
version only)
-15 DLL file error There is no DLL file for each CNC series corresponding to specified
node.
-7 Version mismatch between The CNC/PMC version does not match that of the library.Replace
the CNC/PMC and library the library or the CNC/PMC control software.
-2 Reset or stop request The RESET or STOP button was pressed.Call the termination
function.
1 Error(function is not Specific function which must be executed beforehand has not
executed, or not available) been executed.Otherwise that function is not available.
2 Error(data block length Check and correct the data block length or number of data.
error, error of number of
data)
12 Error(CNC mode error) The CNC mode is incorrect.Correct the CNC mode.
18 Error(Not found Machine ID) Please Check or not send CNC_CONNECTION command.
20 Error(Need to Update RemoteAPI version is too old for connected controller, need to
RemoteCnc Version) update RemoteAPI version.
Argument
variable name type [in/out] descriptions
N/A
Return Value True => there is an USB plugged in, False => there isn't an USB
plugged in
Argument
variable name type [in/out] descriptions
N/A
Argument
variable name type [in/out] descriptions
N/A
Argument
variable name type [in/out] descriptions
N/A
READ_information:Basic Information
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_status:Status Information
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_position:Coordinate Information
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_gcode:G Code
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_spindle:Feedrate/Spindle Speed
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_time:Time
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_part_count:Number of Workpieces
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_MakerConfigInfo:Machinery Information
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_alm_current:Current Alarm
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
note The arrangement rule of the alarm array is from new to old.
The format of alarm message is("motion" "number"
"descriptions")
READ_alm_history:Alarm History
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
note The arrangement rule of the alarm array is from new to old.
The format of alarm message is("motion" "number"
"descriptions")
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes
series return value descriptions model
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes The second array of Offset Data, with the title name (Length
Geom...).
Get the data start from the first tool.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes Start from the first tool, until finish writing all the offset.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
EXT 0
MPG Shift 1
G54 2
G55 3
G56 4
G57 5
G58 6
G59 7
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument type 1
variable name type [in/out] descriptions
Argument type 2
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes Since the NC lists of machineries are different, the following format
is recommended:
NcList[][0]:NC Name
NcList[][1]:Size (byte)
NcList[][2]:Last Write DateTime
NcList[][3]: file / directory
Note:If there is no NC program list, return -1(CNCBUSY), please
pay attention to this.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
DOWNLOAD_nc_mem:Download NC program
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_nc_freespace:Remaining Space(k)
Argument
variable name type [in/out] descriptions
Argument
variable name type [in/out] descriptions
Notes 1. 'Count' input the number of the log to be read, and returns the
number of log be read.
2. When the input parameter count is 0, all operation log will be
returned.
3. When a timeout error occurs, you can use the
SynetcRemoteCNC(ip,timeout) constructor to increase the
timeout. Timeout=0 means none, and the unit of timeout is ms.
4. The OPLog returned can refer to the appendix for relevant
information
Note:If there is no Log, return the original array and write "No Log".
This is NOT supported for V12.
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes ※ When the specified parameter number does not exist on the
controller or fails to read, ParamType will be set to -1
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes The number of input & output depends on the selected I/O card
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes The read value will be inputed in the array of PlcData(B,S,I). If the
number fails to be read, the array value will be set to null.
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_plc_ver:PLC Version
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes: The system diagnostic variables 77 and 78 are specific
information of controller. For the remaining system memory, please
refer to diagnostic variable 7.
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Notes:Only support the software version after 10.116.24x
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable name type [in/out] descriptions
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument N/A
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Note:Clear all the buffer (ex:series number, mainboard, model,
code, then call the related API to read the right data
READ_SSV_GetDeviceInfo
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_ServiceReg
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_ServiceUnReg
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_GetCapacity
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_Dump
Argument
variable type [in/ descriptions
name out]
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
READ_SerialStateVar_GetValue
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions
Argument
variable type [in/out] descriptions
name
Return Value 0: Operation completed, else please refer to 3-2 Return Error
Descriptions.
Notes:After the update, the controller must be rebooted to
complete the update
9.16.12 Appendix
READ_nc_OPLog meaning
KeyPressed 0x0005
R 0x0020 Index
P 0x0021 Index
@ 0x0022 Index
L 0x0023 Index
D 0x0024 Index
K 0x0025 Index
Solution Framework
Syntec Dipole function separates the human machine interface from the core (Figure 1 & Figure 2), allowing
users to control the back end controller via the Internet through front end applications (such as standard
human machine interface). Users can use this framework for remote monitoring and diagnosis. The
development environment of front end applications is no longer limited to Windows CE, and general
applications of Windows XP, Windows 7,... can be developed, creating unlimited possibilities.
This user manual teaches users how to install CNC simulation software to the front end Windows user
terminal, and start to use the functions of RemoteCNC one-to-many API.
How to set the controller to turn on Dipole through the human machine interface
Servo setting is on the human machine interface FenuBar:(The interface will be slightly different from
different controller.)
1. F6 Parameter settings → F10 Next page→ F7 Core Server(Figure 3)。
2. F5 Maintain → F2 Internet settings → F5 Core server
This FenuBar function will open the "Core Server Setting Page" (Figure 4).
The following is the description of each parameter:
• "Whether to turn on the server when booting up" is whether to automatically activate the core Dipole
function when booting up.
• "Timeout" means that when the network has no response after this time, the network connection will
be disconnected.
After the user completes the core Dipole settings, pressing "F3 Confirm" to save the settings, or press "F4
Cancel" to recover the settings. After setting, the Dipole function will be automatically activated when next
time booting up.
SYNTEC controller has upgraded from the early DOS system to CE6 system (also known as x86 system), and
now it has been converted to CE7 system (also known as ARM system), and the hardware has been
improved from the initial need to use CF card to no CF card.
During this process, no matter the software or hardware changes, it is accompanied by changes in system
architecture and human-machine screen, so the simple backup action can no longer cope with the
maintenance needs.
To simplify SOP for front-line personnel during maintenance, a software tool has been provided to assist
front-line personnel in data conversion, which is also packaged into an installation package that can be
installed on the controller panel.
This tool includes two items:
• Dos to x86
• x86 to ARM
The relevant instructions are detailed in this manual.
3. Select the drive where the CF card is located in the interface. Only the removable device will be
displayed in the interface.
4. The Log window will notify which type of CF card is in the disk when it is selected.
5. Check the boxes for the files to be backed up, and uncheck the boxes for the files not to be backed
up.
If the registry is checked, the profile will pop up with the following prompt to insert a second CF
card for backup.
The prompt window will automatically detect the insertion of the CF card and an OK button will
appear for the user to confirm.
If the file is not on the second CF card, then click Cancel to back up the first CF card.
LOG screen will show the current packing progress and results.
9. Then, take the installation package to the controller to install the software.
This software can also be used to back up the CF card contents of x86 systems. The procedure is the same
as for DOS to x86, and a zip file will be generated at the end of the process for the controller to install.
Extended Parameter CNC\Data\ParamExt.pxt Merge pxt and pin files into a single
file(The pxt file content has higher
priority)
CNC\Data\ParamExt.pin
OpenCNC\Res\ParamExt.pxt
CNC\APP\appeng.str OCRes\Common\String\AlarmPLC_COM.
xml
CNC\EXE\Appdata.res的 OCRes\CHT\String\AlarmMacro_CHT.xm
CNCCHI.STR l
OCRes\CHT\String\AlarmMacro_CHS.xm
l
CNC\EXE\Appdata.res的 OCRes\CHT\String\AlarmMacro_COM
CNCENG.STR
CNC\Data\HelpENG.txt OCRes\Common\Help\HelpPLCAlarm.ht
m
CNC\LKN\Registry.lkn (Pr3219)\OpenCNC\LKN\Registry.lkn
CNC\MIR\Registry.mir (Pr3219)\OpenCNC\MIR\Registry.mir
Note:
1. Customized alert string : The format must adhere to the specifications; otherwise, the alarm string
will fail to convert.
• Content format: 24xxx="1;MSG=Alarm content"
2. Profile:Pr3219=(0 → DiskA, 1→ No backup, 2→ DiskA, 3→ DiskA)
3. Registry: Pr3219=(0 → DiskA, 1→ No backup, 2→ No backup, 3→ DiskA)
10.4 Compatibility
Item Description
Parameter When the DOS parameter Pr3209 is set to 3 (Dos Simplified), the tool
will process the compatibility and convert it to 119 (CE Simplified) to
maintain the system with the same language.
10.5 Notifications
• Bootcepc is not included in the generated installation package, please refer to step 5 to update
it.
• The boot screen must match the screen resolution in length and width when updating. If it is not
possible to perform the installation, please recreate the boot image file.
• Reference: Update Boot Image File
• File size:
• 800x600:1.37MB (1,440,054 bytes)
• 1024x768:2.25MB (2,359,350 bytes)
• Please make sure the PC can read the file normally through the file manager after inserting the CF
card.
• IP Settings
• Backup restore is not available, please redo the settings.
• Reference: Dipole Setting Manual.
• Font File
• Currently, there is no font file backup function available, if there is any need, please
contact SYNTEC technical center.
STEP 1
• Insert CF1 (DiskC) first. And insert CF2 (DiskA) in step 5 if Pr3219 is set to 3.
STEP 2
STEP 3
STEP 4
STEP 5
• The current status of the execution is displayed above once the conversion starts.
• When the tool reads that Pr3219 is 3, it will prompt the user to insert CF2 (DiskA).
• After the tool is executed, the file manager will be opened and the current output of the
installation package will be displayed.
• A log file will be generated at the same time next to the installation file.
• If the window is displayed, please check if the CF card is inserted correctly through the Windows file
browser.
STEP 6
STEP 7
Parameter • \DiskC\OpenCNC\Data\PARAM.DAT
Ladder • \DiskC\OpenCNC\Ladder\CNC.LAD
Macro • \DiskC\OpenCnc\MACRO\*
OnlineHelp • \DiskC\OCRes\Lang\Help\*.htm
• \DiskC\OCRes\Lang\Help\*.help
IO Mapping • \DiskC\OpenCNC\Data\IoMap_Customer.xml
Profile • (Pr3219)\OpenCNC\Ncfiles\profile
• (Pr3219)\OpenCNC\Ncfiles\profile
Registry • (Pr3219)\OpenCNC\User\Registry.dat
• (Pr3219)\OpenCNC\User\Registry.dat
Gncfile • (Pr3219)\OpenCNC\GNcfiles\*.*
Bootcepc • \DiskC\Bootcepc.bmp
• Must do a bootcepc renew when bootup.
Note : Pr3219 = (0→ No backup, 1→No backup, 2→DiskA, 3→DiskA, 4→No backup)
10.8 Compatibility
Item Description
11 AutoUpgrade Guidance
11.1 AutoUpgrade Guidance
According to different situations, there are two AutoUpgrade tools currently. The differences between two tools are
below.
Using time When problems are caused by DiskA If the image file version is before 9.16 (included), it
malfunction, use this tool to perform easily causes lag for human machine or all-in-one
hardware reforming. driver occasionally send out the MOT-11 alarm,
Upgrade version 9.17 to solve it.
Official website download path: Customer Support > Downloads > Other Tool > AU or AU_iMX6
11.2.1 Introduction
This tool is for models with motherboard i.MX6 to install image files and software which the target versions are 9.17
and 10.116.56K respectively.
When to use:
If the image file version is before 9.16 (included), it is often that the HMI freezes or the all-in-one drive occasionally
triggers the alarm MOT-11. Upgrading to 9.17 can solve the problem, and compared with installing an image file on
the HMI, this tool can ensure a higher completion rate.
11.2.2 Precautions
• This tool is only applicable to models with motherboard i.MX6 and will not have any effect on models with
other ones.
• Please make sure that the remaining space of the USB is greater than 1 G after inserting AutoUpgrade.
• Please pay attention to the prompts on the controller and remove the USB before the first reboot to avoid
starting the installation process again at the next boot.
11.2.3 Instructions
Steps
1. Please log in to SYNTEC official website and download AutoUpgrade_iMX6 via the path: Customer Support>
Downloads> Other Tool.
2. After decompressing the downloaded file AutoUpgrade_iMX6_{version number}.zip, put all the files in the
USB root directory. (It is recommended that this USB is dedicated to AutoUpgrade, and stores AutoUpgrade
related files only.)
3. Plug the USB into the controller.
4. Reboot the controller.
5. When the controller turns on, AutoUpgrade will be executed automatically.
6. After installation is completed, the controller will display "remove the USB and reboot". (First prompt)
7. After removing the USB, reboot the controller.
8. The controller will prompt to reboot for the second times. Reboot the controller again.
9. Continuing on point 8, there is a certain probability that the controller will directly complete booting
up, which means that the second prompt will not appear. Please note that you still have to reboot, no
matter that it prompts or not.
10. After successfully booting up, AutoUpgrade is completed.
Confirmation
1. Go to the "System Information" page and check whether the image file version is 9.17 and the software
version is 10.116.56K.
11.2.4 Troubleshooting
• If AutoUpgrade is not executed, please check the following:
a. Please make sure that the decompressed file is placed in the "root directory" of the USB, not in any
other folders. If the path is wrong, please move the file to the USB root directory and try again.
b. Please make sure that the controller motherboard is i.MX6. You may look up this information on the
controller "System Information" page. If the motherboard model is not i.MX6, this tool is not
applicable to this controller.
c. If all of the above are confirmed to be correct, please provide the log file for problem analysis.
-Log file location: USB Disk/Backup/{controller serial number}/{controller serial number}.txt
-E.g. E:\Backup\M7A0001\M7A0001.txt
11.3.1 Preface
The purpose of this tool is to perform hardware reforming (update the image file) when DiskA encounters a
problem. During the process, it will automatically back up the system files and restore the files after the reforming.
11.3.2 Note
1. For the complete AutoUpgrade process, the controller needs to be restarted at least three times. Therefore,
if an abnormal thing occurs after the execution of AutoUpgrade, such as a panel malfunction, please restart
the controller several times to restore the function.
2. After executing AutoUpgrade, a folder with the same name as the serial number of the controller will be
generated in the backup folder of the USB, and there is a txt file (Log file) with the same name as the serial
number of the controller.
a. If AutoUpgrade has not completed normally, please provide this txt file so that the technology center
can analyze the problem.
3. If the image file version is older than 7.21 / 7.42, user can only use AutoUpgrade to upgrade the image file, do
not use the controller human-machine to upgrade.
4. After upgrading the image file with AutoUpgrade, please do not degrade to the older version.
5. By default, AutoUpgrade only supports 6/11/21/21-H/eHMC series controllers. If there's need for other
models, please refer to the steps below.
a. Please download the installation package of the required model and unzip it, remove the software
version number , and put it in the Setup folder. For example, change 60CPrintCE7_ARM from
60PrintCE7_ARM_10.116.54T.
6. Please use AutoUpgrade when the controller can boot normally.
7. After AutoUpgrade is completed, it is recommended to reload all processing files to avoid using the
damaged processing files, which may cause the risk of collision.
11.3.3 Operation
Preparation
1. Please make sure that the remaining space of the USB is greater than 1G after inserting AutoUpgrade.
2. AutoUpgrade only supports the controller software version 10.116.x or after. If the original version is
10.114.x, please manually upgrade to version at least 10.116.x before using the AutoUpgrade.
3. If the controller cannot boot normally, please try to repair it (for example, format DiskA first), and then use
AutoUpgrade. If it cannot be repaired, please send it for repair directly.
4. If the OP-022 or OP-003 alarm has appeared on the controller, please try to back up the important files (login
files and processing files) in DiskA first, then enter SA to format DiskA, and then use AutoUpgrade. .
5. In addition, if the backup cannot be completed, please format DiskA directly, and then use AutoUpgrade.
Steps
1. Go to Syntec official website and download the latest version of AutoUpgrade. (Classified as "Other Tool")
2. Unzip the file and put all files in the USB root directory. (It is recommended that this USB dedicates only for
AutoUpgrade, do not put other files.)
6. While booting up next time, whether a reboot prompt appears (refer to the figure below), or it has
successfully entered the HMI, user must reboot for the second time to ensure the complete execution of
AutoUpgrade.
Confirmation
1. After the upgrade is completed, go to the system information screen and confirm that the controller
software version and image file version are correct.
a. Image file version: 7.21 / 7.59
b. Software version: Built-in version is 10.116.24Z, if the initial version is later than this version, no
software upgrade will be needed.
i. If there are other versions, please confirm by yourself.
2. If user wants to confirm the execution result of AutoUpgrade, you can open the log file (*.txt file) with the
same name as the controller serial number in the backup folder, and drag it to the bottom to confirm
whether there is a string in the figure below. If it does, it means the upgrade is successful. .
3. After AutoUpgrade is completed, if the OP-022 or OP-003 alarm still appears afterwards, it means that the
hardware is seriously damaged. Please replace the controller directly.
11.3.4 Troubleshoot
The following figure shows the operation of AutoUpgrade. Please refer to the flowchart and the following QA while
handling your problems.
QA1:
Problem:
• The screen shows that the remaining space of the USB Disk is less than 1G, please replace the USB Disk
and reboot
Solution:
• Please replace a USB with a free space greater than 1G, and then execute again.
QA2:
Problem:
• The screen shows that insufficient files required for low-level formatting, please replace the USB Disk
and run again
Solution:
• Check whether all files of AutoUpgrade have been put into the USB, and then run it again.
• Replacing the USB then execute it again.
QA3:
Problem:
• The screen shows that DiskA file system read failure. This is a serious error. Please format DiskA
manually before executing AutoUpgrade
Solution:
• Please try to manually back up important files in DiskA, such as login files, processing files, etc. If some files
cannot even be backed up manually, it means that the file is damaged and user can give up the backup.
• After the manual backup is completed, please enter the SA to format DiskA, and then execute AutoUpgrade
again.
• Continuing, if the version is too old, SA does not provide formatting function. Please refer to Handling of
abnormalities in ARM second sector, ask for the USB formatting password from Syntec Taiwan Technology
Center.
QA4:
Problem:
• The screen shows that DiskC file system read failure, this is a serious error, please stop executing
AutoUpgrade.
Solution:
• Please manually install the controller software version (the same version or a later one), and execute
AutoUpgrade again after installation.
• After completing the previous step, if the same situation still occurs, it means that AutoUpgrade cannot be
executed on this controller.
• If the controller can still operate normally, please evaluate the on-site conditions to see whether to use it
continuously or to replace the controller.
QA5:
Problem:
• The screen shows that the drive file backup is incomplete, please check the update record and re-run
AutoUpgrade after troubleshooting (the screen text is still based on the system).
Solution:
• Please find the backup folder in the USB, there is a folder with the same name as the serial number of the
controller, and there is a txt file with the same name as the serial number of the controller in this folder.
• Open the txt file and drag it directly to the bottom to check which file failed to back up.
• If the backup of the parameter, PLC, or login file fails, please confirm whether there is a previous backup file
that can be restored, or try to directly export the file from the controller and then import it.
• If the file that failed to backup is at the core system file level, please refer to the Q4 solution.
QA6:
Problem:
• The following picture appears.
Solution:
• Please reboot. If the controller continues to perform AutoUpgrade after rebooting, just wait for AutoUpgrade
to complete.
• If it is stuck on the Syntec Logo screen after rebooting, it means that the reforming has failed. Please replace
the controller.
Others
• If user encounters booting problem during the AutoUpgrade process, please try the following steps first:
power off> plug and unplug the USB> reboot. If this action works, it means that the cause of the problem is
USB read failure, and can continue to execute AutoUpgrade at this time.
Version :
10.118.60 M,
10.118.66G,
10.118.70A,
10.118.71
• If the file
name is
Chinese,
the value
of device
must be
encoded
with
ANSI
Note: The
original name of
this action is
"open the
system large
keyboard".
Choose Yes,
according to the
Schema
definition, save
the current
settings in
FileName.cyc
Choose No,
nothing will
happen
g. Please note
CUSTOMFILE_CYCLE2 <action>CUSTOMFILE_CYCLE2</ 1. Specify
that this custom
action> the
Action will
existing
change the file
CycleNa
location where
me
the system
as "Cust
reads XMLDB,
omXMLD
such as
BData2"
DBOPEN/
2. Specify
DBLOAD
the file
storage
location
as
"GNcFile
s\CYCLE2
"
Notice
Conditions for
uploading files
using the file
management
screen
1. The file
name
storage
device used
by
CycleTable,
need to be
the same as
the file
managemen
t screen
L39XX
correspond
ing to the
file
manageme
nt screen
Open the
CYCLEX
folder on
the file
manage
ment
screen,
and the
correspo
ndence
between
the file
name
storage
device
L39XX
• If
C
Y
C
L
E
1
is
t
u
r
n
e
d
o
n,
t
h
e
u
s
e
r
s
el
e
ct
s
t
h
e
st
o
r
a
g
e
d
e
vi
c
e
L
3
9
8
0
c
o
rr
e
s
p
o
n
di
n
g
t
o
t
h
e
fil
e
n
a
m
e
• If
C
Y
C
L
E
2
is
t
u
r
n
e
d
o
n,
t
h
e
u
s
e
r
s
el
e
ct
s
t
h
e
st
o
r
a
g
e
d
e
vi
c
e
L
3
9
6
0
c
o
rr
e
s
p
o
n
di
n
g
t
o
t
h
e
fil
e
n
a
m
e
• ...
• If
C
Y
C
L
E
5
is
t
u
r
n
e
d
o
n,
t
h
e
u
s
e
r
s
el
e
ct
s
t
h
e
st
o
r
a
g
e
d
e
vi
c
e
L
3
9
0
0
c
o
rr
e
s
p
o
n
di
n
g
t
o
t
h
e
fil
e
n
a
m
e
2. Need to
operate
during the
file
managemen
t screen is
opening
The CTLoadFile
issued only at
this time can
load the file
selected in the
file
management
screen
In other cases,
the issued
CTLoadFile will
directly load the
file according to
the "file name
variable"
MMI Variant set value <Action fill up the value of • Only VAR/ 10.118.39
name="SetVariantVal device STR are
Arg1: Variant type
ue"> supported
(VAR/STR)
<Arg
Arg2: Variant number index="1">STR</Arg>
(ex: 100) <Arg
index="2">100</Arg>
Arg3: Variant value
<Arg
(ex: G01)
index="3">G01</Arg>
</Action>
• requirement description
The special machines in some industry (such as automation, woodworking machines, etc.), in order to save
costs, ease of operation and other factors, most of the hardware is not equipped with a hardkey operation
panel.
Syntec provides a solution to replace the traditional physical buttons, and provides a HMI standard software
panel dedicated to various industries (this software panel can be customized through eHMI according to
different needs), so that the user only needs to trigger the software button display on the HMI software
panel without using the hardkey operation panel to achieve various machining operations. (Such as: trigger
cycle start, pause, JOG, machining mode switching, etc.).
Take the most commonly used cycle start as an example. The traditional operation method is to press the
cycle start button on the HardKey. This button will trigger a specific I point, so when the PLC scans, it will be
based on the logic written by the PLC, detecting whether the I point On. If on, it will trigger C0 On to notify the
core, and when the core finds C0 On, it will execute the cycle start action accordingly. However, in the above
process, not only a hardware operation panel (HardKey) is required, but also the PLC must cooperate with
writing related logic to correctly notify the core to execute the cycle start action.
Using the software panel function to trigger the software buttons displayed on the HMI software panel
directly informs the core to execute the cycle start action, instead of notifying the core through the PLC
first.
Set the machine _SetMachinePos R160 Trigger This R value One- read
coordinates of Axis_N 70 Software corresponds to Shot
the specified Panel _SetMachinePosAxi
[argument] N is
axis (refer to s_1 action of the
the axis ID, only _SetMachine
R38) software panel.
integers 1~16 are PosAxis_1
accepted Action When the user
triggers_SetMachine
[example]
PosAxis_1 on the
_SetMachinePos software panel, the R
Axis_16 value equal to 1.
represents to set
the mechine
R160 Disable If the R value is - read /edit
coordinate of the
71 Direct Set X equal to 0, the
sixteenth axis to
Axis Machine _SetMachinePosAxi
the value of R38
Position by s_1 of the software
Software panel is triggered
Panel and will directly
notify the
system Set X Axis
Machine Position;
If the R value is not
0, the
_SetMachinePosAxi
s_1 of the software
panel is triggered,
and will not notify
the system Set X Axis
Machine Position。
The gain of the _IncrementFeed R161 Software This R value Hold read
first MPG and _N 40 Panel Increm corresponds to the
JOG settings ent Feed argument value of
[argument] N is
_IncrementFeed_N
the override, only
Action, and
integers are
corresponding to the
accepted
gain of the first MPG
[example]
and JOG.
_IncrementFeed
For example: if
_10 represents
_IncrementFeed_10
the gain of the
is triggered, the R
first MPG and JOG
value is equal to 10
is 1
and represents the
the gain of the first
MPG and JOG is 10.
The movement
distance of JOG
changes from 0.001
to 0.010.
Note:
[Action type]
One-Shot: the software panel design needs to be rising edge triggered ( ex: cycle start, feedhold, reset, ...)
Hold: the software panel design needs to maintain the state after triggering( ex: Axis JOG +/-, mode selection,
Feedrate Override, Rapid Traverse Override, Axis MANUAL CONTROL, ...)
• Precautions
• When there is a need for customized machining actions, please use the R value corresponding to
the software button function to close the software button and directly trigger the
corresponding machining operation.
• At present, for the selection of machining mode & override, Jog, this type of regularly used button,
if there are hardware buttons and software buttons both existing, or the software buttons
conflict with the logic in the PLC, please use the R value corresponding to software button
function to close the software button and directly trigger the corresponding machining
operation.
• When using this function, please first check whether the function already has a physical key, and
whether the PLC has the logic to trigger the same action. If there is the above situation, please set
the corresponding R value equal to 1. Turn off the HMI and directly notify the core to perform various
machining actions to avoid unexpected actions.
• The R value switch corresponding to the software button function requires some waiting time after
being triggered and cannot take effect immediately. Therefore, it is recommended to avoid
dynamic switching in the application to avoid unexpected misoperation due to update timing
issues.
• The override of software button function, only supports percentage, not the levels.
• [When there is requirement for customized machining actions, how to meet it?]
For example, before Cycle Start, you need to trigger a certain O point to release the brake, or check
that the safety door I point must be On before machining can be performed.
If you press the button on the HMI to directly notify the core Cycle Start, the above protection
cannot be provided, which may cause the machine error and cause problems such as collision.
Please be careful.
In this application scenario, the user must edit the relevant protection logic through the PLC and
set the corresponding R value equal to 1 and turn off the mechanism that HMI directly notify the
core start cycle. For details, please refer to the Action name and R value of the software panel
function table.
For example, I7 represents the safety door I point. If the requirement is to check the safety door, the
I point must be on to start cycle. Then the PLC must be protected as follows. First, R16001 must be
set to 1, and the mechanism that the HMI directly notify the core to start cycle must be turned off.
Then judged R16000 signal that will be filled in when the cycle start API is called and the
corresponding safety door I point I7 On are established at the same time, and then C0 can be
triggered to notify the core to start cycle.
If the mechanism that HMI directly notifies the core Cycle Start is not properly turned off, the
required protection will not be achieved, which may cause the machine error and cause
problems such as collision. Please be careful.
• [If the hardware button and software button both exist or the software button conflicts with
the PLC logic]
Please be sure to set the corresponding R value equal to 1, turn off the mechanism that the HMI
directly informs the core to perform machining actions. For details, please refer to the Action
name and R value of the software panel function table, otherwise it may cause the machine error
and cause problems such as collision. Please be careful.
For example, there is a machining mode selection in both the hardware button and the software
button, or the machining mode selected in the PLC is different from the machining mode set by the
software.
Assuming that the hardware buttons or PLC logic is set to automatic mode, and the software
buttons are set to MPG mode, there is a conflict between the two modes, and the system will not
operate normally.
Therefore, please select the corresponding R16038 equal to 1 of the machining mode, and turn
off the path of software directly notifying the core to switch the machining mode.
Same as other situations, such as cycle start or JOG, which may cause twice trigger.
All in all, when using this function, please first check whether the function corresponding to
the software already has a physical key, and whether the PLC has logic to trigger the same
action.
Please be sure to set the corresponding R value equal to 1, turn off the mechanism that the HMI
directly informs the core to perform machining actions, avoid unexpected actions happen.
13 AutoSDUpgrade_2021 Manual.
中文版 Mandarin Version: AutoSDUpgrade_2021 操作手冊
• Introduction
• Note
• Operation Guide
• Preparation
• Steps
• Result
13.1 Introduction
This tool helps to upgrade the controllers/servo drives to a stable version which has fixed problems listed below.
2. Software restrictions
• Only support software version between 10.116.36P and 10.118.48.x.
( 10.116.54.x、10.118.12.x ...etc. are all included )
3. Product restriction
• This tool does not support Laser product(70CA, 70CB, 70CB-5, 710CA, 70SA,
70SB, 71SA, 710SA)
Servo-drive- Only take normal axes as fix targets Only take normal axes version as check targets
Upgrade If any normal axis needs to be upgraded, every
• Original version at 2.4.0~2.14.14 : will
target Syntec servo drive will be upgraded.
be upgraded to 2.14.15
versions
• Original version at 3.0.0~3.0.20 : will • Versions need to be upgraded
be upgraded to 3.0.21 • 2.4.0~2.14.14
• Original version at 4.0.0~4.0.9 : will • 3.0.0~3.0.22
be upgraded to 4.0.10 • 4.0.0~4.0.10
If version is not in the range above,
• Upgradation target(According to
upgradation will not be execute.
hardware)
• 3.0.23
• 4.0.11
13.2 Note
1. Before using the tool, please make sure that the controller is under servo-off status(ATC/ROT...etc. axes that
can be controlled by PLC, please make sure servo-off R-bit is triggered, too.).
2. After executing the tool,there will be a log-file named "AutoSDUpgrade.log" in the root folder of the USB.
a. If the tool do not function normally,Please provide this log file and contact with Syntec.
3. After executing the tool , please remove the USB and restart the controller.
4. Please do not remove USB or restart before any message start with "***" to prevent damage.
5. Please do not replace any file under tool folder to prevent any damage to the drive or the controller.
6. If encounter "Space not enough" hint, please wait until drives check finished and restart to fix by steps:
a. Check and clean up Macro files.
b. Check and simplify OCRes/PrdMMIRes/ESI, backup them and remove them via SA first before reinstall
a newer version.
c. If steps above can not fix the problem, please contact with Syntec.
13.3.1 Preparation
1. Check the controller's image version is available. If image version too old, please upgrade via
AutoUpgrade_DiskA_2018 tool first.
2. Make sure that the controller's software version fit the rules listed in the introduction.
3. Please check that the controller parameter works right and the connection with the servo drive is
established correctly.
13.3.2 Steps
1. Download the newest tool from https://www.syntecclub.com/Download.aspx(under category "Other
Tool")
a. This tool provides packages with different product group, please download according to product
type.
b. Package bane machine machine model 模擬器
type
Robot 81RG
2. Unzip the package and copy all the contents to USB root. (recommend: keep the USB clean without any
other files excepts tool data)
* WOOD package will contain an extra folder "Monitor" to provide font-end software.
13.3.3 Result
1. After the upgrading process, check the software version in System info. screen.
Make sure that the controller version is not in version range with problem.
a. If the log file present text below, means the upgradation succeeded.
b. If the log file present text below, means the controller is fine without upgradation.
2. After the upgrading process, check the servo drive version in DeviceManager screen.
Make sure that the servo drives are not in version range with problem.
a. Check the whole process by log file. If the final message as below, means the process was finished
successfully.
*** The whole upgradation succeeded, please remove the USB and restart the controller. ***
b. If log file or message on the screen show the message as below, means there is no servo drive need to
be upgraded.
*** No upgradable Syntec servo drive, please remove the USB and restart the servo drives and
the controller. ***
3. If using SDPatch_2021_3.0.0
a. After the upgrading process, check the image version in System info. screen.
b. Check Cloud Software by checking R8=1; R9=205
Flow chart
detail
14 AutoSDUpgrade_2022 Manual.
• Introduction
• Note
• Operation Guide
• Preparation
• Steps
• Result
14.1 Introduction
This tool helps to upgrade the controllers/servo drives to a stable version which has fixed problems listed below.
2. Software restrictions
• Only support software version between 10.116.36P and 10.118.48.x.
( 10.116.54.x、10.118.12.x ...etc. are all included )
3. Product restriction
• This tool does not support Laser product (70SA, 70SB, 71SA, 710SA)
Servo-drive- Only take normal axes as fix targets Only take normal axes version as check targets
Upgrade If any normal axis needs to be upgraded, every
• Original version at 2.4.0~2.14.14 : will
target Syntec servo drive will be upgraded.
be upgraded to 2.14.15
versions
• Original version at 3.0.0~3.0.20 : will • Versions need to be upgraded
be upgraded to 3.0.21 • 2.4.0~2.14.14
• Original version at 4.0.0~4.0.9 : will • 3.0.0~3.0.22
be upgraded to 4.0.10 • 4.0.0~4.0.10
If version is not in the range above,
• Upgradation target(According to
upgradation will not be execute.
hardware)
• 3.0.23
• 4.0.11
14.2 Note
1. Before using the tool, please make sure that the controller is under servo-off status(ATC/ROT...etc. axes that
can be controlled by PLC, please make sure servo-off R-bit is triggered, too.).
2. After executing the tool,there will be a log-file named "AutoSDUpgrade.log" in the root folder of the USB.
a. If the tool do not function normally,Please provide this log file and contact with Syntec.
3. After executing the tool , please remove the USB and restart the controller.
4. Please do not remove USB or restart before any message start with "***" to prevent damage.
5. Please do not replace any file under tool folder to prevent any damage to the drive or the controller.
6. If encounter "Space not enough" hint, please wait until drives check finished and restart to fix by steps:
a. Check and clean up Macro files.
b. Check and simplify OCRes/PrdMMIRes/ESI, backup them and remove them via SA first before reinstall
a newer version.
c. If steps above can not fix the problem, please contact with Syntec.
14.3.1 Preparation
1. Check the controller's image version is available. If image version too old, please upgrade via
AutoUpgrade_DiskA_2018 tool first.
2. Make sure that the controller's software version fit the rules listed in the introduction.
3. Please check that the controller parameter works right and the connection with the servo drive is
established correctly.
14.3.2 Steps
1. Download the newest tool from https://www.syntecclub.com/Download.aspx(under category "Other
Tool")
a. This tool provides packages with different product group, please download according to product
type.
b. Package bane machine machine model 模拟器
type
Robot 81RG
2. Unzip the package and copy all the contents to USB root. (recommend: keep the USB clean without any
other files excepts tool data)
* WOOD package will contain an extra folder "Monitor" to provide font-end software.
14.3.3 Result
1. After the upgrading process, check the software version in System info. screen.
Make sure that the controller version is not in version range with problem.
a. If the log file present text below, means the upgradation succeeded.
b. If the log file present text below, means the controller is fine without upgradation.
2. After the upgrading process, check the servo drive version in DeviceManager screen.
Make sure that the servo drives are not in version range with problem.
a. Check the whole process by log file. If the final message as below, means the process was finished
successfully.
*** The whole upgradation succeeded, please remove the USB and restart the controller. ***
b. If log file or message on the screen show the message as below, means there is no servo drive need to
be upgraded.
*** No upgradable Syntec servo drive, please remove the USB and restart the servo drives and
the controller. ***
3. If using SDPatch_2021_3.0.0
a. After the upgrading process, check the image version in System info. screen.
b. Check Cloud Software by checking R8=1; R9=205
15 FixFontFile Manual
中文版 Mandarin Version : FixFontFile 操作手册
Content
• Introduction
• Notes
• Environment Requirement
• Operation
• Trouble shootings
15.1 Introduction
• This tool is applied to the character issue because of the broken file of IQC fixture ( G1K00006 ).
• This tool can automatically execute by plugging in the USB, it can fix the character issue of controller.
• This tool will replace the broken font file in the controller ( MINGLIU.TTC, COMICBD.TTF, MONACO.TTF ).
Supported version Log
15.2 Notes
• Please do not remove the USB while the tool is running, this action will cause serious damage to the
system.
• If an unexpectedly power failure occurs, user can first try to remove the USB and reboot completely, then
plug the USB back in and reboot the controller again. The system will try to process font fix again.
However, if an abnormal phenomenon occurs and the tool cannot replace the font file normally, Please
contact Syntec Customer Service.
15.4 Operation
1. Please download the tool from the official website:
a. Link : http://www.syntecclub.com/Download.aspx
b. Path : Download => 06. Other Tool => FixFontFile
2. Unzip the installation pack to the USB, and the files in your USB are as shown in the figure below:
The OS does not match Please confirm whether the current operating
system is WindowsCE7
Failed to move the font file Please try to remove the USB and reboot
in controller completely, then plug the USB back in and reboot
the controller again.
Failed to import the font file a. Please check the following files in
from USB the folder of FontFixTool.
• Data
• MINGLIU.TTC
• COMICBD.TTF
• MONACO.TTF
• FontFixTool.exe
b. Please try to remove the USB and
reboot completely, then plug the
USB back in and reboot the
controller again.
Content
• Introduction
• Notes
• Environment Requirement
• Operation
• Trouble shootings
15.6.1 Introduction
• This tool is applied to the character issue because of the broken file of IQC fixture ( G1K00006 ).
• This tool can automatically execute by plugging in the USB, it can fix the character issue of controller.
• This tool will replace the broken font file in the controller ( MINGLIU.TTC, COMICBD.TTF, MONACO.TTF ).
Supported version Log
15.6.2 Notes
• Please do not remove the USB while the tool is running, this action will cause serious damage to the
system.
• If an unexpectedly power failure occurs, user can first try to remove the USB and reboot completely, then
plug the USB back in and reboot the controller again. The system will try to process font fix again.
However, if an abnormal phenomenon occurs and the tool cannot replace the font file normally, Please
contact Syntec Customer Service.
15.6.4 Operation
1. Please download the tool from the official website:
a. Link : http://www.syntecclub.com/Download.aspx
b. Path : Download => 06. Other Tool => FixFontFile
2. Unzip the installation pack to the USB, and the files in your USB are as shown in the figure below:
The OS does not match Please confirm whether the current operating
system is WindowsCE7
Failed to move the font file Please try to remove the USB and reboot
in controller completely, then plug the USB back in and reboot
the controller again.
Failed to import the font file a. Please check the following files in
from USB the folder of FontFixTool.
• Data
• MINGLIU.TTC
• COMICBD.TTF
• MONACO.TTF
• FontFixTool.exe
b. Please try to remove the USB and
reboot completely, then plug the
USB back in and reboot the
controller again.