7/12/2022 9:35 AM  
Joined: 4/28/2020 Last visit: 8/18/2022 Posts: 30 Rating: (0) 
Thanks. So, now, I have a length that I can give in myself ( in cm), and an analog value that's converted to a speed in cm/min. Is there a way to make a constant calculation of the remaining length? So: the length that I gave in should be constantly reduce, dependent on the speed (analog value). Purpose is to unroll a coil with fiber at a certain speed (analog value) and to know when the coil will be empty. In best case, we can constantly see the remaining length on the coil. Thanks in advance  
Last edited by: The Helping Hand at: 07/12/2022 15:37:56New subject after splitting 

7/12/2022 2:21 PM  
Joined: 4/28/2020 Last visit: 8/18/2022 Posts: 30 Rating: (0) 
Like you see above, I now have a little program: every second, the mathematic function does a calculation of the inserted value (here 10000) minus the analog (amplified) value (here 186). But in fact, he should take every second the new calculated value (here 10000186 = 9814) minus the analog value, and that over and over again. I should see the calculated value reduce every second. Is that possible? Thanks in advance 
7/12/2022 3:42 PM  
Joined: 12/18/2014 Last visit: 2/5/2023 Posts: 29106 Rating: (3570)

Here an example.
AttachmentConstant_calculation_of_the_remaining_length_0BA8.Standard.zip (155 Downloads) 
This contribution was helpful to1 thankful Users 
7/12/2022 3:57 PM  
Joined: 4/28/2020 Last visit: 8/18/2022 Posts: 30 Rating: (0) 
Thanks a lot! I'll try to understand that now :D 
7/13/2022 9:54 AM  
Joined: 4/28/2020 Last visit: 8/18/2022 Posts: 30 Rating: (0) 
Thanks for that! Now I made the program myself, but seems like there's still something wrong. When I enable the I1, to start the cyclus, it doesn't start from the given value (here 10000) but it starts reducing from 0. Any idea what I do wrong? Thanks in advance AttachmentLeegloopdetectie_2.zip (151 Downloads) 
7/13/2022 10:29 AM  
Joined: 12/18/2014 Last visit: 2/5/2023 Posts: 29106 Rating: (3570)

I make the example with LSC V8.0 for a LOGO! 0BA8.Standard. You have a LOGO! 8.3 and made the program with LSC V8.3. It seems that are not 100 % compatible. Insert a flag between the counter output and the input of the analog MUX. 
This contribution was helpful to1 thankful Users 
7/13/2022 11:42 AM  
Joined: 4/28/2020 Last visit: 8/18/2022 Posts: 30 Rating: (0) 
For the moment, my analog value is still in cm/min; but I reduce my given value (10000) every second. So, I have to divide my analog value by 60 to have it as cm/sec. But the problem is, the accuracy isn't good at all, the final value only changes when the initial value is a multiple of 60. Should there be a way to solve this? I can just let it be in cm/min and only reduce my value once a minute, but then there's also some accuracy problem. Thanks in advance 
7/13/2022 12:15 PM  
Joined: 12/18/2014 Last visit: 2/5/2023 Posts: 29106 Rating: (3570)

You only write about the theory. Please give real values. What would be a possible start value and which unit is it. Cm or m? 
7/13/2022 12:53 PM  
Joined: 4/28/2020 Last visit: 8/18/2022 Posts: 30 Rating: (0) 
I'm sorry, I'll try to explain it better. So I have a 010v signal, what in fact is a speed of 08 m/min. But in Logo, I can't scale accurate between 0 and 8, so I do it between 0 and 800. Because of that scaling, the unit becomes cm/min. Value I give in by hand is the length of the rope on the coil, in cm (here: 10000) Becaus of the fact I reduce that given value (10000) every second for the moment, the speed value (0800) does also have to be reduced by 60; to become cm/sec. So for example: speed of 4,2 m/min: after the calculations in Logo: 7 cm/sec. The value of 10000 has to be reduced by 7 every second. But my problem now is the conversion from the speed from cm/min to cm/sec. I have to divide by 60, but because of that, the accuracy is not ok. By example: 116 cm/min becomes 1 cm/sec; but 124 cm/min becomes 2cm/sec: little difference, but huge difference in outcome 
7/13/2022 1:21 PM  
Joined: 12/18/2014 Last visit: 2/5/2023 Posts: 29106 Rating: (3570)

That is the problem by LOGO!. The LOGO! can only calculate with integer values. 
Follow us on