DDCSV macro variable Description:

#0- #49 for each subroutine internal private variables;
#50- #499 is the system internal variable area 1;
#500- #999 is the system parameter area;
#1000- #1999 is the system internal variable area 2;

The chs or eng file defines the system parameters that the user needs to configure, for example:

#1 -t2 -s1 "language setting" -m16 -min = 0.000 -max = 1.000 -i0 "Eng" -i1 "Chinese"

#n n is the parameter number (0-499), n + 500 is the macro variable number of this parameter;
-t is used to specify the type of parameter, t0 is an integer, t1 is a real number, and t2 is a selection type.
-s1 defines the name of the parameter;
-s2 defines the parameter unit;
-m parameter group, m0 that the parameters in the parameter configuration page does not show;
-min minimum parameter
-max maximum parameter
-i The text of the relevant entry is configured through it when the parameter type is selection type;

Will_D Posted at 2018-3-2 07:09
Few of us have rar. Please use .zip format

Hi!
Sorry, I will use .zip format later

Hi JPoepsel!
102 subprogram is used to play back the track of the tool. Before using the 102 subroutine, the track must be recorded, the attachment is an example related to it.

Thank you for the information provided.

https://www.facebook.com/groups/ ... k/2530082060342283/

Hello 71taa

      Currently DDCSV2.1 only supports simple serial protocol, and can not use macro program to control sending and receiving.
       The DM500 Handheld CNC Motion Controller supports the MODBUS communication protocol, and the data transfer can be controlled by a macro program to meet your needs, you can try it.

Serial port interface uses Max3232 device

When #108(M Bus IO command response) is set to 1 (yes), DDCSV periodically generates an output IO instruction packet according to the #1032-#1063 macro variable and sends it. In addition, DDCSV will periodically receive the bus input IO instruction packet and update the #1000-#1031 macro variable according to it. The #1000-#1031 update is real-time, which means that as soon as the bus input IO packet is received, #1000-#1031 will be updated.

Hi JPoepsel.
the "serial port" is the one feed out on the MPG conector.

Sorry, I am still on a business trip, and I will sort out the relevant information when I go back.

Hi Lukasz!
DDCSV through RS232 protocol bus IO expansion, the current version does not support communication with the serial MPG.

Output data packet 7 bytes, including three parts:
1. Data packet header 2 bytes "0x90 0xeb"
2. Output IO word 4 bytes, 0 bit -31 bit are mapped to # 1032- # 1063 macro variables
3. the checksum, XOR result of the first 6 bytes

Input data packet 7 bytes, including three parts:
1. Data packet header 2 bytes "0x90 0xeb"
2. Input IO words 4 bytes, 0 bit -31 bit are mapped to # 1000- # 1031 macro variables
3. the checksum, XOR result of the first 6 bytes

Bus output IO signal Instructions for use:
Change the IO status by assigning the relevant macro IO bus output
Example:
# 1032 = 1; set bus IO channel 0 to logic '1'

Bus input IO signal instructions:
M100 bus input IO instruction
#1100 Bus input IO channel number
#1101 Bus input IO expectations value
#1102 waiting time (ms),if <= 0, infinite waiting for the signal to reach the desired value; if> 0,   if the signal does not reach the expected value within the specified time，paused.

Example:
(If channel 2 is logic '1', subsequent codes are executed; otherwise, pauses after 1s.)
# 1100 = 2
# 1101 = 1
# 1102 = 1000
M100
...