Ask our Experts
Didn't find what you are looking for? Ask our experts!
New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Support Forum for HVAC and pumping machines, Modicon M17x and EcoStruxure Machine Expert HVAC software for chillers, AHU, CRAC units for datacenters or process chillers applications - from design, implementation to troubleshooting and more, by Schneider Electric.
Search in
Please select a country to continue with beta search.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-10-26 04:12 PM
Hi
I used the operation hours in structured text but it did not seem to work. I am a little confused with the pins in the manual.
The input is a local digital input, the output is a status variable UDINT.
Should I be getting the hours from the input pin ptrE2_OpHours ? Then saving this to an eeprom once a day?
Alternatively, I was going to use the sysTimer to build the hour meter, or retentive timers. It looks like the system timer is a millisecond timer running forward but it must reset to zero after the UDINT gets full or does it reset every 24 hours?
I really appreciate the help. Thank you
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-10-26 11:42 PM
You need to add the EEPROM value via Pointer (ADR) or (?) to the input. This is the save value. The Output value of the block could be connected to a status variabel. Then you can show the Status Variable as Read Only. You find examples in FBD in the integrated TVDAs.
This point is often in the beginning confusing. All blocks which have an @datatype as input await an pointer value. This is related to the point how the writing on EEPROM work. (via syswrite****)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-10-26 11:42 PM
You need to add the EEPROM value via Pointer (ADR) or (?) to the input. This is the save value. The Output value of the block could be connected to a status variabel. Then you can show the Status Variable as Read Only. You find examples in FBD in the integrated TVDAs.
This point is often in the beginning confusing. All blocks which have an @datatype as input await an pointer value. This is related to the point how the writing on EEPROM work. (via syswrite****)
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-10-28 03:40 AM
Thank you very much for the help.
Do you know how the sysTimer function works? When does it reset?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-10-31 09:23 AM
Hi Bastian, thank you for the help.
I tried to use the pointer in structured text but I seem to have the wrong syntax.
PP1_Hours_fb_lv is the running hours function block, PP1_Hours_sv is the UDINT status variable and PP1_Hours_eep is the UDINT eeprom. Would you be able to assist with the correct syntax please?
Also do you know about the sysTimer, when does it reset? Every 24 hours? Much appreciated.
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.