Third party software and hardware support forums. > CS-Lab

Lag on inputs

(1/2) > >>

lion_rapid:
Hello
Short code:

--- Code: ---SetOutBit(90, 2)
    CamRdy = false
    While(Not CamRdy)
        If(GetInBit(90, 10)) Then
        ResetOutBit(90, 2)
            CamRdy = true
        End If
    Wend
--- End code ---

Oscilloscope hooked up to input nr 10 and output nr 2. There is a lag of about 100ms!

If I use code:

--- Code: ---SetOutBit(90, 2)
Sleep(100)
ResetOutBit(90, 2)
Sleep(100)
SetOutBit(90, 2)
Sleep(100)
ResetOutBit(90, 2)
--- End code ---

Then the impulse width on the output is 102-103ms.
So nothing wrong here, looks like there is lag on the inputs.

TPS:
contact CSLAB via:  office@cs-lab.eu

and ask Wojtek Trawicki for Support.


 

lion_rapid:
That was the first thing I did :-)

lion_rapid:
Today I got an answer: "We tested it on our setup and average lag time was 90ms, we advise to use PLC in this case".

lion_rapid:
Two-three hours later something came to my mind:
It's weird, when I run one of the axis against a limit switch, the reaction time is usually below 10ms.
When I run the tool length macro it's the same.
Why on earth here is 90-100ms?
Tomorrow I'll define those inputs and outputs from Csmio in the MACH3, then declare them in my test macro and see what happens.

Navigation

[0] Message Index

[#] Next page