Ask our Experts
Didn't find what you are looking for? Ask our experts!
A forum for topics related to the scope of Modicon PAC offers and ecosystem along the whole lifecycle: Modicon M580 and 340, EcoStruxure Control Expert, EcoStruxure Process Expert (Unity Pro) and more.
Search in
Link copied. Please paste this link to share this article on your social media post.
Posted: β2025-09-24 06:56 AM
I completed Phase one of this project one year ago. My client wants to be able to control the speed of the VFD via the HMI. Ethernet was the easiest choice. I already had the IP addresses of the CPU. IT has items above the IP address. When I created the DTM CE automatically placed them at these locations. Even though I manually added them also with the desired IP addresses. But they don't use the Powerflex EDS. Do I need to change the IP address of the ECPU and then recreate these DTMs?
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-25 07:21 AM
I bit the bullet and moved everything down to the area IT wanted. The IODDT variables are not what I am used to in StudioLogix. How would I fix this. These variables are not intuitive. I am using the correct EDS for the VFDs and the DTM was obviously properly created.
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-27 07:28 AM . Last Modified: β2025-09-27 07:42 AM
Looks like a broken EDS import π Free means nothing is assigned to that scanned variable. This is usually the case with Modbus if you don't specifically name the variables in the DTM browser. It should probably not happen with an EDS if the file is not broken somehow. If you can't get the EDS file working correctly you can create your own structure and link it to those unnamed "Free" variables by copying them into a new structured variable using the EXTRACT FB which is a way many seems to prefer due to the inflexibility of the DTM browser. EXTRACT is like a MOVE but copies a range of data instead of single variables. You need two EXTRACT operations to handle both inputs and outputs. Just point it to your device.inputs and device.outputs as src and dst of each and add your new structured variable as the other part, specify copy length of src and dst in bytes.
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-29 05:50 AM
Not necessarily a broken EDS import. Some vendors provide EDS files that do not have any data structure and have to do it manually like you described above.
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.