Nirtec Studio Forum

General Category => EasyPLC v.5 => Topic started by: Automaiton Fan on July 19, 2012, 02:24:38 PM

Title: problem while sending the project to Virtual PLC
Post by: Automaiton Fan on July 19, 2012, 02:24:38 PM
Hi guys,

I have problems with running Virtual PLC and also connecting Step 7 to Machine Simulator.

The problem is when I want to run Virtual PLC I always get this massage showed in the picture 1 ( attached  files) and when I click on continue and then hit the compile and send icon I get this massage ( Picture 2) and then Easy PLC stops working and the project won't be send to the Virtual PLC.

I have Microsoft .NET Framework 4 Client profile installed on my computer but I don't know why I get this massage frequently.

Any suggestions?



[attachment deleted by admin]
Title: Re: problem while sending the project to Virtual PLC
Post by: EasyPLC_Master on July 20, 2012, 10:19:24 AM
Hello Automaiton Fan, welcome to the forum.
Can you upload your PLC program here?, I can study it in order to check if have some trouble.

Thanks.
Title: Re: problem while sending the project to Virtual PLC
Post by: Automaiton Fan on July 20, 2012, 12:13:02 PM
Hi,

I worked on it and could solve the problem. The problem wasn't related to the PLC program because I copied that directly from the available project on Easy PLC.

Thank you for your thoughts on this.

Regards,

Title: Re: problem while sending the project to Virtual PLC
Post by: EasyPLC_Master on July 20, 2012, 01:08:41 PM
Can you tell us what was the cause of the problem?, perhaps could helps others users with the same problem.
Thanks.
Title: Re: problem while sending the project to Virtual PLC
Post by: Automaiton Fan on July 20, 2012, 02:45:35 PM
Sure, the cause of the problem was elementary.

When I wanted to compile and send the project to the Virtual PLC, first I clicked on compile & send project icon and then lunch virtual PLC and I always got that massage but next time I clicked on compile project icon first and then compile & send project icon and finally lunched the virtual PLC and the problem was gone.