Configuration of axis feature "Signaling", CNC system

Ask Questions
1

Hello,

I would like to use the Axis feature “Signaling” to trigger a camera system. The mechanical setup consists of a gantry in which the X and Y axes are designed as an XY CNC system:

Aufbau
Aufbau647×537 98.4 KB

I have configured the 2-Axes CNC (XY) according to the help, as well as the Signaling feature.

In addition, I also had to add the M-Functions feature to the axis group (which is not mentioned in the help) as otherwise a corresponding error would be output when the CNC program is executed.

M-Function
M-Function1061×829 62.6 KB

I tried to trigger the camera with a simple program, the number of triggers is correct but the timing does not fit at all:

%001                   (Main program definition)
N05 G90                (absolute coordinates)
N10 F40000             (Feed rate 50000 Units/min)
N20 G01 X10 Y10
N30 G01 X84.36 Y39.5 G220 0.0 TriggerCam
N40 G01 X93.36 Y39.5 G220 0.0 TriggerCam
N50 G01 X102.36 Y39.5 G220 0.0 TriggerCam
N60 G01 X111.36 Y39.5 G220 0.0 TriggerCam
N70 G01 X120.36 Y39.5 G220 0.0 TriggerCam
N80 G01 X129.36 Y39.5 G220 0.0 TriggerCam
N90 G01 X138.36 Y39.5 G220 0.0 TriggerCam
N100 G01 X147.36 Y39.5 G220 0.0 TriggerCam
N110 G01 X156.36 Y39.5 G220 0.0 TriggerCam
N200 M30                (NC program end)

I was wrong with that:

What I have noticed:
The variable ::FG_VB:diTimeStamp is incremented correctly, but it does not match the current NetTime of the SoC at all:

Nettime
Nettime1133×286 33.3 KB

I would have expected the generated NetTimestamp to be calculated by the “Signaling” feature based on the NetTime of the SoC, but this does not seem to be the case.
Which settings are missing?

The timestap does seem ok but something is wrong with the prediction.

Best regards,
Simon

2

can anyone help @simon.buschor?

3

Well, the whole process wasn’t easy, especially since the NetTime module has countless settings. The main issue, however, was the override on the MpCnc2Axis FUB, which was set to 60. Since the Signaling feature doesn’t have access to this value, the prediction is calculated using an override of 100.

image
image783×300 20.5 KB

The feedrate used in the CNC program is written in the PlcTask and is calculated with a different override. That was the solution.

VAR {AT 'FG_VB'}
    arstTipPositions : ARRAY [1..96] OF McPointType;
    uiFeedRate : UINT;
    rDelay : REAL;
END_VAR

VAR
    diLoopIndex : DINT;
END_VAR

PROGRAM _MAIN
    Feedrate(uiFeedRate);
    FOR diLoopIndex := 1 TO 96 BY 1 DO
        MoveJ(arstTipPositions[diLoopIndex]);
        SignalTime(rDelay, ConfiguredSignal := TriggerCam);
    END_FOR
END_PROGRAM
1 Like