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: 2022-06-03 08:25 AM
I get these warnings while compiling:
warning A4103: SYSFTP_COD_FILEFILTER => Data block not found
warning A4103: SYSIP_ADDRESS => Data block not found
warning A4103: SYSDEFGTWY_ADDRESS => Data block not found
warning A4103: SYSPRIDNS_ADDRESS => Data block not found
warning A4103: SYSSECDNS_ADDRESS => Data block not found
warning A4103: SYSMODBUS_MSG_RECEIVED_USB => Data block not found
warning A4103: SYSMODBUS_MSG_RECEIVED_RS485_1 => Data block not found
warning A4103: SYSMODBUS_MSG_RECEIVED_RS485_2 => Data block not found
warning A4103: SYSMODBUS_MSG_RECEIVED_RS485_PLUGIN => Data block not found
However, these mesages seem to pop-up almost randomly.
I am not implementing these functions, neither ftp or modbus access in this project.
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: 2022-06-03 08:38 AM
These are datablocks of TM172, maybe you are compiling connected to a different target (check your current connection settings), if this is the case the SW will upload the target image of what is connected.
A "refresh current target" (from menu Project), before compiling should solve the warning issue.
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: 2022-06-03 08:38 AM
These are datablocks of TM172, maybe you are compiling connected to a different target (check your current connection settings), if this is the case the SW will upload the target image of what is connected.
A "refresh current target" (from menu Project), before compiling should solve the warning issue.
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: 2022-06-04 04:10 AM
Checking your answer, it looks right. I got the warnings, refresehed the target and compiled again and the warnings disappeared.
If you can further help me, I would like to have any idea of the different targets available. For example, this project is for a TM172PDG28R. If I select Project/Select target the choice here is quite obvious.
However when I connect to the actual PLC, I get a warning, telling me that I am trying to connect to a different release (I recall maybe 596.10 instead of 596.12 but I am at home now).
In any case programming works fine at the real PLC so I have never bothered too much about these warnings. Is it advisable to go to Commissioning/Bios Downloads and upgrade the firmware ? Does this solve this other issue ?
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: 2022-06-04 05:26 AM
Warning comes when the project target is different from the plc fw version.
You should have always plc version equal or higher than the project version, e.g. m172 596.12 project 596.10.
This situation can causr a warning but it is not a problem, to avoid it you have to update the project target (I prefer to update project only when it is rrally necessary).
The opposite situation can cause a problem in case the project uses some datablocks or target blocks not defined in the old bios version.
It is better to upgrade the bios to the latest version available.
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.
With achievable small steps, users progress and continually feel satisfaction in task accomplishment.
Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.
of