Scout 5.3 TIA systematically crash on MCC editor

Hi there,
I've the same issue.
I'm running TIA 15.1 on Vmware.

10GB RAM, 2 cores, 90GB HDD, Virtualization enabled.

Anyway, all seems pretty good (around 40 secs to start TIA, 40 secs to open a project and 60 secs to open SCOUT) - except the MCC Variable assignation crash.

I don't understand what could cause that.

At the moment the Virtual Machine runs the following software:
TIA Portal 15.1 Update 3;
STEP 7 Safety;
Startdrive 15.1;
SCOUT TIA 5.3.1.0;
STARTER 5.3 hotfix 3;

Microsoft Antivirus disabled - and no other software installed.

What can i do?

Thanks goodness, ChristophD gave us a workaround - but force people to use the stand-alone version, when it's still possible to download a bugged version of SCOUT TIA, it's quite incorrect.

(I haven't tried yet this workaround, but ChristophD is never wrong, so it must work).

Where i can officially report this crash?
Someone that had the same issue, solved it?How?

Regards

Astroke67

Where i can officially report this crash?

 Start a Support Request...

Pigro, probably you are really "pigro" because you did not note what I wrote.

 Davinator,

I'm definitely "pigro" ; lazy for anyone outside of Italy. I use to read those thread meanwhile I'm doing something else (developing software for instance ) and sometimes I loose text.

I just want to report you the test performed right now (I'm wasting my time in a hotel room):

37 seconds VM start to have the W7 ready for any application
29 seconds TIA15.1 is available to open a project
30 seconds to open a project containing some thirdy parts servomotors, S7-1500 and Simotion
28 seconds Scout open and ready to open a unit

I can't report any MCC unit open because I don't have MCC on my application; I just have ST unit and open their editor take the same time as release the mouse.

My hardware:
HP Zbook 15 G3 core I7-6700HQ CPU @2.60GHz - W7pro-64
SSD1 SanDisk SD7TN3Q 256Gb; 
SSD2 Samsung D 860 Pro 2Tb for VM;
24Gb Ram
VM settings : 16Gb Ram 2 processors, most of the keysettings as default HD 100 Gb
VMware workstation 12 pro
I had to break the piggy bank to buy it but I'm not working disappointed.

I guess those information will point you to sort out of your issue.

have a lazy night, pigroplc

pigroplc

Pigro, probably you are really "pigro" because you did not note what I wrote.

 Davinator,

I'm definitely "pigro" ; lazy for anyone outside of Italy. I use to read those thread meanwhile I'm doing something else (developing software for instance ) and sometimes I loose text.

I just want to report you the test performed right now (I'm wasting my time in a hotel room):

37 seconds VM start to have the W7 ready for any application
29 seconds TIA15.1 is available to open a project
30 seconds to open a project containing some thirdy parts servomotors, S7-1500 and Simotion
28 seconds Scout open and ready to open a unit

I can't report any MCC unit open because I don't have MCC on my application; I just have ST unit and open their editor take the same time as release the mouse.

My hardware:
HP Zbook 15 G3 core I7-6700HQ CPU @2.60GHz - W7pro-64
SSD1 SanDisk SD7TN3Q 256Gb; 
SSD2 Samsung D 860 Pro 2Tb for VM;
24Gb Ram
VM settings : 16Gb Ram 2 processors, most of the keysettings as default HD 100 Gb
VMware workstation 12 pro
I had to break the piggy bank to buy it but I'm not working disappointed.

I guess those information will point you to sort out of your issue.

have a lazy night, pigroplc

 Hello Pigro,

yes, mine was just a "funny" thing because, as being italian like you, I joked on the term "Pigro".

Anyway it was just to tell you that we performed LOT of tests, using various OS guests and always making things "clean" , in order to have a fast response from the VM.

But we failed.

But after we won, because we realized that using VMWare (and not Virtualbox), the timings are amazingly reduced, moreor less by one half. And of course 2.15 minutes more or less to open a project starting from opening the VM are acceptable.

I don't know why but it really seems that for some reasons, VMWare has a dramatic increase of performances respect Virtualbox, expecially for the WIn10 (Guest) and TIA 15.1.

For the TIA 13.1 the differences are unnoticeable.

But everything now is fine, at least we are "up to date" with this 15.1.

THe funny thing is that when you open Scout for the first time it takes some seconds (30-35) , if you close Scout (5.3 TIA) and you reopen it, it needs more or less 2 seconds and this is nice.

So ... Let's enjoy the 15.1.

But anyway (just to go back to the topic) the bug of the MCC editor is well known to Siemens (we asked also to the Hot service) and the procedure of the Master (ChristophD) is correct : install Step7 5.6 and Scout Stand Alone. Of course this is a bug that I hope that Siemens will fix (this bug did not exists in 15.0 or 13.0 or 13.1).

Regards,

Davinator

ChristophD

Merhaba,

step7 / Scout Classic'i yan yana TIA / Scout TIA kurulumuna kurun, sonra kilitlenme düzeltildi

Saygılarımızla

Christoph

 https://support.industry.siemens.com/tf/ww/en/posts/simotion-scout-v52-setup-eror/221760/?page=0&pageSize=10 

Well,

Scout can be downloaded in two flavours :

1) SCOUT TIA, where Scout program is integrated in TIA environment, so basically you cannot launch Scout, but you launch TIA Portal and after that you open Simotion configuration and automatically TIA opens Scout. This Scout version uses TIA Portal Hardware Configuration

2) SCOUT "Classic", where Scout is a stand alone program which needs of course the installation of Step 7 environment to handle the Hardware configuration. With this program you do not need TIA for programming Simotions. It was the only "flavour" that was available before Scout 4.4 which was the first version of scout that came in this two flavours, since V4.3 was available only in Classic version.

Look here (Scout 5.2, not the newr 5.3, for it you have to google , I cannot find the link):

https://support.industry.siemens.com/cs/document/109755392/simotion-scout-scout-stand-alone-and-scout-tia-v5-2-sp1-?dti=0&dl=en&lc=de-WW