Jump to content

vasovas

Members
  • Posts

    26
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by vasovas

  1. Hello, Ausman, the production is not always 7/7, it might be 5/7, 6/7 or 7/7, it depends. HSC definitely is not necessary, because the counting frequency vary from 15 to 30 Hz. I am not the author of the original program, so I tried to add only what was necessary for SCADA project. 

    Regarding the set of SI, I used SI 37 and the program works for the time being, I keep on monitoring it in case there is some bug.

  2. Hello, Ausman, thank you for your input, In fact, I have never faced such an issue with HSC values. My HSC values never have been lost on the next day.

    My task actually is to reset the HSC accumulated on previous day value once only - at the start of the machine next day. As Flex727  has advised, RTC SI and SB2 can be used for this purpose, and  I use SI 37 , its value is incremented with 1 and stored to MI, so at the next power up, if it happens on the next day, that accumulated HSC value is reset. It works. Of course, now I have to implement mechanism to correct the MI value depending on what current month is. It needs some work, but as Flex727, nothing difficult. If you have brighter ideas how to do that, please advise. Thanks a lot!

    P.S. To reset only once (first startup in the morning), I will use increment flag, so in case the machine has been restarted during the day (which happens couple of times actually), I will check that flag  value, if it is different from 0,  HSC will not be reset.

  3. Hello,

    I have an issue reading the values of HSC by Ignition SCADA. PLC type: SM35-J-R20.

    Shortly, there is a simple logic calculating the total output from the  machine, PNP proximity sensor is used to measure the number of the passing products, and it is connected to HSC input of the PLC.  SCADA monitors the current and the previous value of the counter, and in case the counter has been reset when the batch is being changed (the previous value is bigger than the current value), the previous value is memorized and it is added to the current counter value, at the same time  a tag value is incremented by 1 (this tag is like a flag, a  proof that the counter has been reset) . Now, the problem: without reset of the counter,  the flag shows increments, and the output is not calculated properly. The most important: 50% of the machines are equipped with SM35-J-R20, and the rest - with Omron CJ1M; the problem never has been faced on Omron machines. The communication protocol used for both type PLC is Modbus TCP.  Any ideas what might be the root cause? 

  4. Hello, Mr. Tauser,

    At first Happy and Prosperous New 2020!

    Thank you for your advises, most of the issues solved now. Attached you can find ML tags that I can read now (L1...L6), plus Ignition Modbus Address Map, as requested by you. To get the right readings, I had to reverse the word byte order, as you supposed. Reading MI was piece of cake, so I did not attached anything, except Double-Single Tag, which is visible on the  Tag Browser (file Tags).

    What still does not work, is MF tags reading - can you please double check the starting address, since I could not find the proper help file?

     

    Ignition Modbus Address Map.PNG

    ML.PNG

    Tags.PNG

×
×
  • Create New...