the IF1 and IF2 of a 6PPT30 device are a 2-port switch, so I agree it should work.
What’s about the connection between PLC and HMI, is that connection working? I mean, is the visualization (from the screenshot, it looks like you’re using a VC4 visualization) of the PLC displayed on the PPT?
If “no”, what’s about the ethernet link leds of PPT’s IF1 and PLC’s IF2, are they showing any activity?
thanks for reply!
Until now, everything sounds normal to me, I can’t see a problem.
Whats the IP address and subnet mask of your notebook? And is something changing when you switch the cables from PLC and PC at the PPT’s two interfaces (don’t think so, just for curiosity)?
okay, thanks.
One last question: if you’re using a external switch to connect the PLC, the PPT and your Notebook instead of both IF1+2 of the PPT, is then everything working?
Usando un switch externo tampoco me detecta el plc…
he probado a conectar mi portatil a la red desde el mismo puerto que uso para el plc, usando de switch la pantalla, he quitado el plc y le he dado a mi portail la ip del plc para saber si hay problemas con la ip pero haciendo todo esto SI que me hace ping a la .52.
Es decir que creo que el problema es que el plc rechaza de alguna manera la comunicacion.
la pantalla sigue comunicando, funciona bien el switch de la pantalla, usando un switch externo tambien comunico el pc pero no el plc, la red esta probada y da ping con el portatil usando la ip del plc… ya solo me queda cambiar de plc por probar….
no se si me esta rechazando el plc la comunicacion por algo aunque parpadee el led de if2…
Hmm, strange.
Are you using the firewall on the PLC, if yes how is it configured? (firewall is the only thing on PLC side that I know that could block pinging)
Even if it doesn’t fit exactly to the error description I would also propose the check the DHCP server settings about the range of the dynamic IPs used there (only to confirm that there’s no overlap of static and dynamic IP addresses which could cause some strange behavior, too).
Good look, please update us when you found the cause!
Solucionado.. al final era el error mas tonto…
En los parametros de ETH dentro de la configuracion del automata no estaba bien configurada la default gateway.