Motion Control System SIMOTION

IO on sinamics - connectinted to simotion - cpu goes to stop

Erstellt von lio5 am 01.05.2012 14:59 (4 Antworten)

  01.05.2012, 14:59

lio5 Beigetreten am: 05.01.2010 Letzter Besuch: 06.06.2013 Beiträge: 37 Bewertung:  (0)	(0)  hello all i have project , with simotion D425 connected via profibus to another CU320-2 DP . i am using the on board IO of the CU as part of my IO logic in the program . When there is no connection to the CU via profibus  and the cpu is trying to reach one of the IO on the sinamics CU, the CPU goes into stop . how can i avoid it ?
	Top

  01.05.2012, 17:13

ChristophD Beigetreten am: 12.05.2006 Letzter Besuch: 18.06.2013 Beiträge: 1590 Bewertung:  (120)	(0)  Hello, you must define a strategy (CPU-Stop, Last Value, Substitute Value) for you I/O's or check the IO state with the function _get/_setsSafeValue. Regards Christoph
	Top

  02.05.2012, 06:30

viralpatel Beigetreten am: 18.11.2010 Letzter Besuch: 18.06.2013 Beiträge: 170 Bewertung:  (8)	(0)  Dear Christophd, but i think this method will not solve this problem because when Simotion want to access CU IOs it will definate goes into stop mode because node access error as you say it will retain status only not force Simotion to continue in run mode.  regards, viral
	Top

  02.05.2012, 07:18

ChristophD Beigetreten am: 12.05.2006 Letzter Besuch: 18.06.2013 Beiträge: 1590 Bewertung:  (120)	(0)  Hello, no, bot ways prevent the CPU goes to stop. With the functions _get/_setsafeValue the system check the availability of the IO channels. With a strategy <> CPU-Stop the system get a defined value from the I/O's . I'm using this ways in many of my projects an i never go to Stop when i access any IO channels which are not present at the moment. When you use a peroipherialFaultTask so you can handle a station dissconect of an external CU also. Regards Christoph
	Top
	Für diesen Beitrag bedankt sich: viralpatel

  02.05.2012, 12:41

JUANSANCHEZ Beigetreten am: 04.08.2010 Letzter Besuch: 11.06.2013 Beiträge: 118 Bewertung:  (2)	(0)  hello you should call the peripherialFaultTask  J.SANCHEZ
	Top