Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

S7-1215C not compatible

Created by: Derick81 at: 6/10/2016 7:29 PM (5 Replies)

Rating (0)

Thanks 4

6 Entries

6/10/2016 7:29 PM	Rate (0)
Derick81 Posts: 13 Rating: (1)	Hi, I'm using TIA portal V13 sp8 on a virtualbox win7 (host is win 10). It is a new CPU and HMI (KTP700). I can detect the cpu and HMI and change their name and IP. When I try to detect the hardware in a new project using unspecified CPU it says "device not compatible". All subnet 255.255.255.0 PLC: 192.168.0.1 HMI 192.168.0.2 PC 192.168.0.100 (I also tried some other ip's in the 192.168.0.x range) I also tried downloading the program after I manually configured the hardware, that also didn't work. I also have simatic manager v5.5 installed on the same virtual machine, but I doubt that would be an issue? Any suggestions? Edit: forgot to say: I can also see the correct MAC address when I scan for accessible online devices.
Derick81 Posts: 13 Rating: (1)	Last edited by: Derick81 at: 6/10/2016 7:32:23 PM
Suggestion To thank Quote Answer

6/10/2016 8:01 PM	Rate (0)
William_B Posts: 5225 Rating: (1195)	Hi. i do not know how to resolve your problem - I have not yet done the VM thing. Some guesses though.. Check if there is a link between the VM network adapter and that of the physical. It can be either a bridged connection or come configuration in the VM itself (where you set the memory usage). I suggest you make sure the Win10 side has a fixed IP address and not dynamic. You will also have to investigate that the all the required Ports are open and not blocked by security software, Win10 or the VM. Hopefully these thoughts may help you make a targeted search for the answer. w
William_B Posts: 5225 Rating: (1195)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Derick81

6/10/2016 8:38 PM	Rate (0)
Derick81 Posts: 13 Rating: (1)	Thanks, it is a bridged adapter link, pretty sure I used the same settings as the guy in this video and he seemed to have got it to work. Although his UI is in Spanish and mine in English, I'm pretty sure I have the right settings. I did have a dynamic IP on my host(win10). I will change that to fixed on Monday(I'm assuming I was a different IP to the virtual machine) and also try with VMWare instead of virtualbox as I read in another thead that that is what Siemens suggests. Firewall was disabled on the virtual machine (win7 professional sp1, 32bit). I will try disable my firewall on the host machine next time as well. I assumed I wouldn't be able to even detect the PLC or change the IP if it was a connection issue though. Another other suggestions anyone? Really need to get this to work asap :/
Derick81 Posts: 13 Rating: (1)	Last edited by: Derick81 at: 6/10/2016 8:42:07 PM
Suggestion To thank Quote Answer

6/10/2016 11:08 PM	Rate (0)
grrrrrroooo Platinum Member Joined: 3/16/2015 Last visit: 10/10/2021 Posts: 1250 Rating: (173)	Sorry for seeming to be repeating myself. From my experience, device incompatible never had anything to do with the device and always had to do with connection issues that were windows related. screenshots will always help, the more the merrier. What you did by trying to download a program or hardware configuration to the device is what I would do. From that you should be able to provide step by step screen shots of the errors which will help us help you. In my case, almost everything interfered with my connection. Wifi had to initially be turned off and it could be turned on after connecting. Windows defender had to be turned off and if it was already off I had to turn it on and then off again. The same issue with firewall, I had to turn it on then off. Good luck Edit: Do they show up under accessible devices?
	Last edited by: Kal.A at: 6/10/2016 11:12:53 PM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Derick81

6/11/2016 1:58 PM	Rate (0)
Derick81 Posts: 13 Rating: (1)	Thank you, yes it did turn up under accessible devices. I will try again on Monday with your suggestions.
Derick81 Posts: 13 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users grrrrrroooo

6/13/2016 8:21 PM	Rate (0)
Derick81 Posts: 13 Rating: (1)	Thanks guys, it was either the firewall or using a dynamic IP address on the host OS (win 10). I changed both and it worked.
Derick81 Posts: 13 Rating: (1)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users grrrrrroooo

|

Share this page:

Share this page on...

Follow us on