ACCEPTED SOLUTION
Accepted Solutions
Let's start here. This is a user defined profile. It has 5 entries. The 6 second delay... the ramp... the hold... the decel ramp... and the final delay.
Note how "t" is used in the expressions because the current value of "t" must be considered to use them in calculations (same with angle for position profiles).
Unfortunately, I cannot find a way to show more datapoints on the graph. It is a bit misleading. If you look at the formulas, and the time domains, you will see where the ramp actually starts and where it ends. You can tweak the position of the "=" sign to fine tune when these milestones are actually hit. It does make a difference in relation to your frame settings during the analysis.
Plot these and see if you get the analysis to run. Remember to use kinematic on the analysis type. Set the time for 19 seconds and I recommend a frame rate of 25 <<== this is so the time will match a video capture at a frame rate of 25. Options are 25, 30 or 50 in the play dialog.
An S profile or sinus profile is the advanced form of traphezoidal profile.which lkooks line the profiles shown in the pictures attached.Picture 1A is the S curve and 1B is the taphezoidal curve.the second picture is the profile mentioned here http://communities.ptc.com/docs/DOC-3546#comment-11213 by Antonius Dirriwachter
while the first picture has taken from http://www.pmdcorp.com/news/articles/html/Mathematics_of_Motion_Control_Profiles.cfm
I have applied a traphezoidal profile for velocity which is shown here and have made this velocity profile by dividing the the total travel into 3 segments.ie the first acceleration portion covers 1/3 of the total angle the second 1/3 of the angle with constatnt accel and the 3rd with deaccel and 1/3 of total anlge.I have attaeched an excel file for velocity data vs time.that might help in converting the attached profile to the requested profile.
Let's start here. This is a user defined profile. It has 5 entries. The 6 second delay... the ramp... the hold... the decel ramp... and the final delay.
Note how "t" is used in the expressions because the current value of "t" must be considered to use them in calculations (same with angle for position profiles).
Unfortunately, I cannot find a way to show more datapoints on the graph. It is a bit misleading. If you look at the formulas, and the time domains, you will see where the ramp actually starts and where it ends. You can tweak the position of the "=" sign to fine tune when these milestones are actually hit. It does make a difference in relation to your frame settings during the analysis.
Plot these and see if you get the analysis to run. Remember to use kinematic on the analysis type. Set the time for 19 seconds and I recommend a frame rate of 25 <<== this is so the time will match a video capture at a frame rate of 25. Options are 25, 30 or 50 in the play dialog.
I will add this little video here to expand on graphing of motion profiles. It turns out there are 50 nodes, so if your profile is divisible using this figure, it will make for a cleaner graph. For instance, I used the above example and extended the end time to 25 seconds. This creates a node every 0.5 seconds. Now you can accurately see the transitions of the profile.
I also noted the fact that you -can- read the nodes on the graph itself. Problem is, it is intermittent. If you click one, it will read on the bottom of the graph, and sometimes, you will get a dynamic reading on the face of the graph. I suspect this is a graphics driver issue, but it is an interesting bug. I will submit a CS case on this if others see this same problem. Please post here if you also have intermittent issues with the on-graph readback.
edit: furthermore... you can keep the servo profile at 25 seconds while still making the analysis only 19 seconds(End Time). Just a thought 
