Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Use of HVAC installer
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.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Link copied. Please paste this link to share this article on your social media post.
So I finally was able to complete can binding between two PLCs. It is tricky, because at HVAC machine expert software you need to check the CAN expansion bus as "not used" and define the communication with the installer. Moreover, there does not seem to be specific information about what the installer actually does, if there is it would be nice to know where to find it.
Anyway, the installer is in charge of transfering to each PLC the information about where to retrieve the data from the other PLCs in the network, right? So, how do I "grow" my project without needing to start from scratch every time?
What I mean is this: so far I am only reading one variable from the other PLC: Let´s say I add another variable ... Do I need to "Build all" and "Download all" everytime ?
Moreover, for a little insight on the file structure: I noticed that the installer created some folders, a CFN file and a couple of BINDING.PAR* files. I placed each PLC project on a folder below the main folder used by the installer in order to be able to create a single zip file out of the whole project.
In this case, both projects are exactly identical, it is a 60 hp chiller composed of two 30 hp chillers. So, if I modify anything on the project, it would be nice if I could just copy and paste the project (or work in one project and then "Save as" in the other folder). Can I have some tips in order not to break everything while adding new variables and modifying the project?
One last question: inside the project´s folders there is another CFN file ... Is this file also modified by the installer software?
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Hello,
Installer does more or less what the developer can do in the Commissioning perspective plus the binding.
It's the software which allow to manage an application in terms of settings&status without having access to the source code.
In case of a single plc project, it requires just the file .cfn to program and configure a M17x (it's not necessary the entire project folder).
About binding among M17x, if you change just the shared variable inside Installer, it is enough to update the BINDIN*.PAR file of each PLC.
In term of maintenance, I suggest to enable the option "Multiple File Project":
It will create a src folder where all your POU/function/FB will be stored into separate files.
If your 2 projects are exactly the same you don't need to duplicate them, you can link the same project to both PLC in the Installer project.
The CFN file inside Chiller2 folder is created/updated when you build all the Chiller2 project from ESME HVAC, this file allows to program with Installer the second chiller, but it does not download the BINDIN.PAR file.
For project with data binding you have to use the CFN file created by Installer.
Link copied. Please paste this link to share this article on your social media post.
Hello,
Installer does more or less what the developer can do in the Commissioning perspective plus the binding.
It's the software which allow to manage an application in terms of settings&status without having access to the source code.
In case of a single plc project, it requires just the file .cfn to program and configure a M17x (it's not necessary the entire project folder).
About binding among M17x, if you change just the shared variable inside Installer, it is enough to update the BINDIN*.PAR file of each PLC.
In term of maintenance, I suggest to enable the option "Multiple File Project":
It will create a src folder where all your POU/function/FB will be stored into separate files.
If your 2 projects are exactly the same you don't need to duplicate them, you can link the same project to both PLC in the Installer project.
The CFN file inside Chiller2 folder is created/updated when you build all the Chiller2 project from ESME HVAC, this file allows to program with Installer the second chiller, but it does not download the BINDIN.PAR file.
For project with data binding you have to use the CFN file created by Installer.
Link copied. Please paste this link to share this article on your social media post.
From Installer you can do also partial download:
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.