adccommunitymod (AutomationDirect) asked a question.

Is this kind of logic possible with the Click PLC?

Created Date: June 12,2015

Created By: arbj

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

Hi, can the CLICK PLC (type: C0-01DD2-D) generate a pulse every 5 millisec using a for-next loop. Also how fast can the pulse rate be ?? I know 1 msec may be stretching it as the scan time is 2.5 msec. The program in the PLC would have the following tasks.. 1. monitor the RS485 port (Port 3) for activity, receive MODBUS RTU packets and process them. 2. Generate pulses as described above, when required, this will be enabled/disabled by a flag variable. 3. Monitor some inputs , these need to be quite fast as they are connected to some limit switches. The input states will also control the state of the pulse generation (ie: pulsing will disabled when inputs are active) 4. Monitor port2 for activity, receive ASCII packets/commands when available and process them. I hope the above description is not too vague, but unfortunately I am working on PLCs for first time but would like to learn, its the main reason why I am buying the CLICK PLC. thanks a


  • adccommunitymod (AutomationDirect)

    Created Date: June 12,2015

    Created by: Tinker

    Hi,

    can the CLICK PLC (type: C0-01DD2-D) generate a pulse every 5 millisec using a for-next loop.

    Also how fast can the pulse rate be ?? I know 1 msec may be stretching it as the scan time is 2.5 msec.

    Not using a for-next loop, but one can setup a timed interrupt for periods as short as 1 millisecond. Using a SET Yn (immediate mode) immediately followed by a RESET Y (same n) also immediate mode, will generate about a 50uS pulse, if that is done in a timed interrupt it will repeat at whatever the interrupt time was set for.

    One can also set up hardware interrupts for time sensitive inputs.

    I'm not sure I understand; "monitor the RS485 port (Port 3) for activity, receive MODBUS RTU packets and process them. "

    The only time I 've had a CLICK "receiving " MODBUS RTU was from a C-More. and it just happened automatically in the background without my doing anything

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: June 13,2015

    Created by: arbj

    Timed interrupts are very good idea, much better than loops. What is fastest time possible with the timed interrupt on the CLICK plc ??

    The only time I 've had a CLICK "receiving " MODBUS RTU was from a C-More. and it just happened automatically in the background without my doing anything

    Sorry, yes I meant that, I thought the application needed to handle this as well, I did not know this was done automatically..

    I have downloaded the CLICK programming software, is there any way of simulating the program, say like a offline debugger ??

    thanks

    a

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: June 13,2015

    Created by: arbj

    thanks Tinker,

    I have made a small program to pulse the output using the interrupt, also I have decided to buy the 100 USD model, with sourcing DC outputs. I think I can easily develop a RS 232 based pulse generator and interface it with this PLC.

    In the meantime I will tinker with the interrupt code and understand the system.

    Thanks

    a

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: June 12,2015

    Created by: arbj

    Hi,

    can the CLICK PLC (type: C0-01DD2-D) generate a pulse every 5 millisec using a for-next loop.

    Also how fast can the pulse rate be ?? I know 1 msec may be stretching it as the scan time is 2.5 msec.

    The program in the PLC would have the following tasks..

    1. monitor the RS485 port (Port 3) for activity, receive MODBUS RTU packets and process them.

    2. Generate pulses as described above, when required, this will be enabled/disabled by a flag variable.

    3. Monitor some inputs , these need to be quite fast as they are connected to some limit switches. The input states will also control the state of the pulse generation (ie: pulsing will disabled when inputs are active)

    4. Monitor port2 for activity, receive ASCII packets/commands when available and process them.

    I hope the above description is not too vague, but unfortunately I am working on PLCs for first time but would like to learn, its the main reason why I am buying the CLICK PLC.

    thanks

    a

    Expand Post