Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Timer ET in HMI 30 seconds ahead of actual ET

Created by: JHanko at: 11/3/2018 4:15 AM (13 Replies)

Rating (0)

Thanks 4

Result pages:: |; 1 | 2; |

14 Entries

Entries per page: 10 | all

11/3/2018 4:15 AM	Rate (0)
JHanko Posts: 10 Rating: (0)	Working with a 1215 PLC and KTP700 HMI. I wrote a simple little program with a start/stop, on delay timer and output. That is working perfectly fine. On the HMI, I have a start button, stop button, timer PT entry field and timer ET display. I wanted to enter the timer PT in minutes and display ET in minutes also, so I simply used linear scaling on the PT and ET HMI tags. I scaled both tags 60000 to 1. The PT entry works exactly as it should. The ET display is always 30 second ahead of the actual timer. For example, If I set PT for 5 minutes, it shows up properly on the timer monitor and the output turns on at the correct time. The ET on the HMI will advance to "1" after approximately 30000 ms has passed instead of 60000. It will advance to "2" 60 seconds later. It continues advancing every 60 seconds after this. In the example given, the HMI will display an ET of "5", when only 4.5 minutes have elapsed. 30 seconds later, the output will fire. I've triple checked everything and can't figure out why the first count is happening so early. Any suggestions would be appreciated. Thank you! Attachment Network.JPG (266 Downloads)
JHanko Posts: 10 Rating: (0)	Last edited by: JHanko at: 11/3/2018 4:15:58 AM Last edited by: JHanko at: 11/4/2018 6:18:39 PM
Suggestion To thank Quote Answer

11/3/2018 4:17 AM	Rate (0)
JHanko Posts: 10 Rating: (0)	Attachment Screen.JPG (213 Downloads)
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/3/2018 4:18 AM	Rate (0)
JHanko Posts: 10 Rating: (0)	Attachment PT Scale.JPG (318 Downloads)
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/3/2018 4:18 AM	Rate (0)
JHanko Posts: 10 Rating: (0)	Attachment ET Scale.JPG (260 Downloads)
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/3/2018 4:41 AM	Rate (0)
JHanko Posts: 10 Rating: (0)	Forgot to mention.... If I turn off linear scaling on the ET tag, the ET is displayed correctly on the HMI in milliseconds.
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/4/2018 4:14 PM	Rate (0)
JHanko Posts: 10 Rating: (0)	This certainly appears to be a bug in the software. When I change the scaling on the ET tag to 1000 to 1, the HMI displays the ET in seconds perfectly. Can anyone please offer a recommendation on this? I am pulling my hair out.
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/4/2018 6:19 PM	Rate (0)
JHanko Posts: 10 Rating: (0)	Video added to original post.
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/5/2018 4:32 AM	Rate (0)
Prof. Frink Platinum Expert Joined: 7/5/2013 Last visit: 11/1/2024 Posts: 3116 Rating: (514)	Hello JHanko, JHanko [...] The ET on the HMI will advance to "1" after approximately 30000 ms has passed instead of 60000. [...] in my opinion it is the correct behaviour, because of rounding. The value goes to one "1" when 30000ms passed. 29999 / 60000 = 0.4999, ROUND(0.4999) = 0 30000 / 60000 = 0.5000, ROUND(0.5000) = 1 So when you want to show the passed time, you may calculate the rounded value in the PLC. Regards, Frink
	Pi is exactly three! All you have to do is think of things which people need but which don’t exist yet.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users JHanko

11/5/2018 6:22 AM	Rate (0)
JHanko Posts: 10 Rating: (0)	Prof. Frink in my opinion it is the correct behaviour, because of rounding. The value goes to one "1" when 30000ms passed. 29999 / 60000 = 0.4999, ROUND(0.4999) = 0 30000 / 60000 = 0.5000, ROUND(0.5000) = 1 So when you want to show the passed time, you may calculate the rounded value in the PLC. Regards, Frink Thanks for the reply, but I don't understand that at all. It is scaled to count to "1" when 60000 ms has elapsed. Why would it round from 30000 to 60000? Also, why doesn't this rounding theory happen on every other subsequent count? They do not count until the full 60000 ms has elapsed. No rounding happening there.
JHanko Posts: 10 Rating: (0)
Suggestion To thank Quote Answer

11/5/2018 7:43 AM	Rate (0)
CaOd Platinum Member Joined: 5/6/2010 Last visit: 10/30/2024 Posts: 1986 Rating: (279)	Hello JHanko, Prof. Frink show you the right solution for your "problem". If you use the linear scaling there is in the background a calculation. This calculation round your result. You can test also the follow: create a variable at your PLC with a value of 1.55. create 3 different I/O-fields which showing the same variable field 1 with a resolution of 9.99 field 2 with a resolution of 9.9 field 3 with a resolution of 9 Then should it show you this 3 values at your HMI field 1 - 1.55 field 2 - 1.6 field 3 - 2 Thats the same function like rounding the showed value. I hope this help you against tearing out your hair. regards CaOd

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users JHanko

|

Share this page:

Share this page on...

Related topics by keywords:

TIA WinCC Communication

Follow us on