5/16/2024 1:21 PM | |
Joined: 3/30/2014 Last visit: 9/2/2024 Posts: 86 Rating:
|
There is no alarm in the ''Alarm'' tab in the lower left corner of the software when an abnormal situation occurs. |
5/17/2024 8:31 AM | |
Joined: 10/11/2006 Last visit: 9/5/2024 Posts: 5902 Rating:
|
Hello. the synchronisation strategy is described in the manual. Please choose one which fits to your requirement. 2.2.5 Synchronization In order for the following axis to follow the master value according to the transmission function, the following axis must first be synchronized to the master value. The type of synchronization is determined from several assignable parameters/settings: • The synchronization criterion/synchronization position, which corresponds to the setting specified in the synchronizingMode parameter; the synchronization position on the master value side and/or the synchronization position on the slave value side are directly specified here or are derived from the synchronization criterion and, if necessary, the transmission function • The synchronization direction, the motion direction of the slave values during synchronization; can be set in the synchronizingDirection parameter • Position of synchronization range relative to synchronization position: Leading, trailing, or symmetrical synchronization; can be set in the syncPositionReference parameter • the reference of the synchronization profile; can be set in the syncProfileReference – Synchronization over a specifiable master value distance The synchronization length over the master value is specified in the synchronization command. – Synchronization profile via specifiable dynamic response parameters (time reference) The dynamic response parameters are specified in the synchronization command. .............. ................ 2.2.5.9 “Synchronous” status during synchronization https://support.industry.siemens.com/cs/ww/en/view/109818984 |
With best regards, |
|
5/19/2024 1:03 AM | |
Joined: 3/30/2014 Last visit: 9/2/2024 Posts: 86 Rating:
|
Sorry, my native language is not English, and you may not have understood the question I expressed before. I will add some more in response to the information you provided. Here is my code: “ i32RetDINT[03]:= _enablecamming(followingobject := toAxisSync, direction := POSITIVE, mastermode := ABSOLUTE, slavemode := ABSOLUTE, cammingmode := CYCLIC, cam := Str_ACENAB.Cam, synchronizingmode := IMMEDIATELY, syncpositionreference := SYNCHRONIZE_WHEN_POSITION_REACHED, syncprofilereference := RELATE_SYNC_PROFILE_TO_TIME ,velocityType := direct ,velocity := 50.0 ,positiveAccelType := direct ,positiveAccel := 10000.0 ,negativeAccelType := direct ,negativeAccel := 10000.0 ,positiveAccelStartJerkType:= direct ,positiveAccelStartJerk := 50000.0 ,positiveAccelEndJerkType := direct ,positiveAccelEndJerk := 50000.0 ,negativeAccelStartJerkType:= direct ,negativeAccelStartJerk := 50000.0 ,negativeAccelEndJerkType := direct ,negativeAccelEndJerk := 50000.0 ,velocityProfile := SMOOTH, mergemode := IMMEDIATELY, nextcommand := IMMEDIATELY, commandid := CammingCommandId, synchronizingdirection := SHORTEST_WAY); ” You can see I used “syncprofilereference := RELATE_SYNC_PROFILE_TO_TIME” and “,velocityProfile := SMOOTH,”. As you can see in the screenshot I posted, the .state=camming has been there for a long time, but the .syncstate didn't shift, the .syncstate only shifted to YES when the Master Axis moved up. My temporary solution is to first change “toAxisSync.setconfigdata.SyncingMotion.masterReversionTolerance” to 0 when using the _enablecamming command, and when using _ enablegearing, and Master is an Axis technology object, change “toAxisSync.setconfigdata.SyncingMotion.masterReversionTolerance” to 40, else Otherwise, keep it at 0. Today local tech support gave me the advice is “syncingMotion.enableSyncWithinTolerance = YES”. My question is why a change in the .setconfigdata.SyncingMotion.masterReversionTolerance value would have this effect. |
Follow us on