Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
HVAC and Pumping Forum
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.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-13 09:50 PM
Hi,
I've previously asked for a feature to set register values after compilation in this post. A similar function could be added if there was a section in the Project Options to allow for 'prebuild' commands i.e. scripts/calls that could be executed prior to the build of the project.
Is this something that can be added in for the next version of ESME HVAC?
Thanks.
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-08-25 12:03 AM
Hi,
I'm sorry but I'm quite sure it won't be possible to add it in the next release, but I will track this request.
At the moment I think you have to play with the IFDEF directives to enable/disable part of code
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-08-26 12:38 AM
Can you tell me which kind of scripts you would like to execute in the pre-build phase?
Which is the goal?
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-08-26 11:12 PM
Hi @FedericoM
I'd like to store build information in the source files. For example, the build date/time, some version control information, related to git, or checking that I have maintained the software release version with respect to changes in the code. I would also like force updates of any other files I want to included in the 'extra' folders. So that they don't have to be maintained.
The goal is to recognise the PLC software on installed products, so that opening debugging sessions can occur without having to update the PLC; we don't have any form of tracking of what code goes on what product we make; it would be easier to have the code recognisable.
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-08-26 11:24 PM . Last Modified: 2025-08-26 11:25 PM
Note that the source files are loaded into memory when the project is opened, so source modification will work only after you close and reopen the project.
Have you already tried to use the post-build?
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-09-01 06:44 PM
That makes sense. I have not tried to using post-build. I'd like to have these changes automatically compiled with the source, in the same way that C or C++ preprocessors work. I'd like to avoid loading anything from the file system or any other construct that works as a read-only value that is dynamically loaded.
Link copied. Please paste this link to share this article on your social media post.
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.