Dars

MrPLC Member
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dars

  • Rank
    Hi, I am New!

Profile Information

  • Country Canada
  1. Hi everyone, I want to be able to read period measure between 1,000 us to 1,000,000 us (1 to 1,000 Hz). My problem is that my VALIDITY bit is cleared when my signal period is lower than 5,000 us. From what I understood in the user manual (http://download.schneider-electric.com/files?p_File_Id=1060793571&p_File_Name=35013355_K01_000_09.pdf), this card can only give one measurement every 5 ms but the shortest period that can be measured is 100 us. I want to have a measure every 20 ms in my M340 periodic task but I suspect that by default the card updates its measurement at every input signal period end. So if the input signal has a period of 4 ms for instance, then a measure update is requested every 4 ms and the card doesn't support it. How can I slow down the update rate so I can read smaller period? See my settings below. I also force "FORCE_SYNC (%Qr.m.c.4)" bit to 1 at any time to enable the measuring update. Thank you!
  2. Let's say I have a 3rd periodic task, what would be my options? Is MAST and FAST task are the only one I can use or I can create others? Also, is there a tool in Unity Pro 7.0 or 8.0 that show in real time every task execution time? Thanks.
  3. Hi everyone, I'm trying to translate Allen Bradley program to Schneider. My program has 2 tasks : - 1 periodic task which has to run precisely every 20 ms - 1 periodic task which run every 100 ms and doesn't need to have a fixed step of calculation In Allen Bradley, I've simply created 2 periodic tasks with priority #1 and priority #2 and that did the job. In Unity Pro, I see MAST and FAST tasks. What is the best practice to achieve the same thing? Thank you.