Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

Drive ES not installed

Created by: Soufiani at: 4/2/2024 11:05 AM (3 Replies)

Rating (0)

Thanks 2

4 Entries

4/2/2024 11:05 AM	Rate (0)
Soufiani Regular Member Joined: 2/25/2018 Last visit: 2/10/2025 Posts: 7 Rating: (0)	Hello, we have an old production pc running a STEP7 project ( v5.1 ) and DRIVE ES Basic V5.1. that is used for configuring Micromaster drives We want to install a new pc running Windows 10. On the new PC we have: STEP 7 V5.7 Drive ES Basic v5.6 When opening the archived project I noticed that the drives are not showing up in the project tree despite Drive ES being installed. When I go to the hardware config I see the drives there but I get an error saying "The project contains objects of the sw package 'Drive ES' which cannot be edited because the SW package is not installed or exists in an earlier version." I cannot do anything in the HW config. Drive ES is clearly installed, but I uninstalled it/reinstalled it but still nothing. I also installed an older version (V5.5 SP1), this doesn't work. and before you ask, yes the Drive ES options are installed for Micromaster and Micromaster 4xx. I also right clicked on the project -> object properties and executed a search for missing software packages to hopefully fix the issue but still nothing. Btw, I also opened the same project in a VM running Windows 7 Step 7 V5.5 and it works perfectly and shows the drives. All the software versions are the exact same except for Step7 itself (V5.5 in the VM) Attachment Schermafbeelding 2024-04-02 130333.png (431 Downloads)
	Last edited by: Soufiani at: 04/02/2024 11:08:05
Suggestion To thank Quote Answer

4/2/2024 1:57 PM	Rate (0)
JWilson Experienced Member Joined: 9/16/2008 Last visit: 8/26/2025 Posts: 60 Rating: (3)	for a test.... do a save as > reorganization slow Let us know how it goes.

Suggestion To thank Quote Answer

4/3/2024 5:39 AM	Rate (0)
Soufiani Regular Member Joined: 2/25/2018 Last visit: 2/10/2025 Posts: 7 Rating: (0)	My apologies, I forgot to mention I already tried that, the issue is that it messes up my hardware configuration for some reason. When I do a save as + reorganize slow, my Profibus network names and connections seems to disappear and it keeps throwing errors when i try to compile it. It doesn't show the drives in the project tree either then Edit: Also, with the reorganized project's hardware config, I cannot even add a Profibus network address to a module. There's no option for that, while it is an option for the original retrieved project.
	Last edited by: Soufiani at: 04/03/2024 05:45:03 Last edited by: Soufiani at: 04/03/2024 05:53:00
Suggestion To thank Quote Answer

4/4/2024 9:03 AM	Rate (0)
Soufiani Regular Member Joined: 2/25/2018 Last visit: 2/10/2025 Posts: 7 Rating: (0)	I seem to have fixed it. The solution is to disable integrity monitoring in Options -> Customize in Simatic Manager and then doing a Save as > Reorganize gets rid of the "Drive ES missing" popup and my drives are finally showing up in the project tree with the correct Profibus configuration in the HW config. Stumbled upon this solution in an article explaining a similar problem but with Simotion. Just in case this could help anyone

Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users Jen_Moderator Martin472

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on