Jump to content

Vision & Samba PLC + HMI Controllers & VisiLogic Software

Welcome to the Vision and Samba series forum
Talk about issues related to the Vision and Samba PLC + HMI series and to VisiLogic software


3,316 topics in this forum

    • 6 replies
    • 1.4k views
    • 0 replies
    • 321 views
    • 4 replies
    • 4.5k views
    • 2 replies
    • 900 views
    • 14 replies
    • 1.8k views
    • 0 replies
    • 1.6k views
    • 7 replies
    • 4.9k views
    • 6 replies
    • 13.7k views
    • 5 replies
    • 17.3k views
    • 14 replies
    • 6.4k views
    • 0 replies
    • 7.4k views
    • 1 reply
    • 11.1k views
    • 8 replies
    • 114 views
  1. I broke my PWM output

    • 4 replies
    • 80 views
    • 4 replies
    • 270 views
    • 6 replies
    • 1.6k views
    • 14 replies
    • 2.7k views
    • 3 replies
    • 247 views
    • 7 replies
    • 1.1k views
    • 9 replies
    • 133 views
    • 7 replies
    • 131 views
    • 0 replies
    • 38 views
    • 8 replies
    • 2.1k views
    • 6 replies
    • 613 views
    • 2 replies
    • 701 views
  • Member Statistics

    6,342
    Total Members
    1,206
    Most Online
    BabbRust
    Newest Member
    BabbRust
    Joined
  • Topics

  • Who's Online (See full list)

  • Posts

    • Not once have I said that.   My responses are based on I don't know how much you know, as you are new here.  Don't forget I am not paid, I am a volunteer who has put in countless hours on this forum often explaining the same thing again and again to people who can't be bothered to look up help files or delve into the forum.  Think how you might react if you were again asked how to turn on a light switch! I have never had this issue myself, but I also only do linearisations on MIs.  What happens if you convert your input numbers to MIs?  Your needed output will still give the same accuracy on the smaller input range that is available with MIs.  Using a counter based on SB13 will let you test this easily with your wanted time of 5 hours.  I can't as I don't use 700s. cheers, Aus
    • Dan, I've always enjoyed finding my "nuder" settings on any of my Jazz.    🙂 cheers, Aus
    • Hi   In U90 Ladder program,  Look under  Help  - Examples - Flow Totalizing..-     Tank Level Single Pump Example. This will answer your questions.   DanT  
    • Thanks for the advice I will try this. Much appreciated!
    • 🤦‍♂️ @Ausman  you keep assuming I don't know what I am doing.... so, ok I will assume that you are NOT being arrogant and that maybe I was not clear on my previous statement due to a language barrier.  of course, the LINEAR function will not stop at ar min or max value, that's the point of a linearization you gave the "initial" and "end values" to calculate the "slope" you don't expect that the linearization ends at certain values, I have that on consideration on my actual program, and I handle the min arnd max values in a particular way to prevent being out of range. what I was trying to explain is that it overshoots over 7000, and the max value is 6000 which corresponds to 1800000 value on ML100, and at that point, since ML100 is near 1402000, then it couldn't be possible that the value at the output of LINZ is more than 6000 which is the value at 1800000 since 1402000 is less than 1800000 (you know... math). but, let me give you more information, in the machine that I was running the program I noticed the issue looking at the data after an imminent failure involving this LINZ problem: In this case, blue is what was sent to the analog output, in my program I have a condition to no update that value if it's out of range, I am not sending the max or min possible values if it is reached, instead I am just not updating the output (this is better for my particular process, and it helped in this situation because that spike after an hour the start of the ramp down would be very very bad, at least I got 1 HR of stable conditions after that ) anyway, as you see in the red line that I have drawn (which is what I concluded was happening in the background), at some point the value overshoot at above 7000, and then continue going down but 1 hr after that the value reached 6000 again (since was going down from 7000 now) since 6000 is within range, the output was updated again, that's what we see a "step" at the last 3 minutes, after that the system was shut down and then reset to the initial conditions, that's why it goes to 0 and 600 ( initial PW =600)  the orange line is what was desired to happen .... a linear and consistent ramp down from 6000 to 600 while counting downtime. I am not going to upload any other program, I already did it. It will be better if you could do a test and prove on your hardware,  maybe is a v700 issue, maybe is a Visilogic Issue, who nows! test different hardware could be good.  Start the countdown with these values X2=0 (End value as the timer goes to 0) X1=1800000 (timer value 5:00:00:00 loaded on ML) Y2 = 6000 Y1=600 countdown to 0 and wait. the overshoot happens near X= 1402000 (Not exactly at that number but I always override the timer at (3:55:00) and wait for until happens (a couple of minutes later) I already did it counting down from 1800000 and the same happens.    
  • Blog Entries

×
×
  • Create New...