You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Issue KISEMA-1609 migrated from JIRA, first reported on 2021-03-23]
In SCCharts dataflow, all simple arithmetic actors such as +, *, &, etc. which are commutative should have free port constraints to allow the layout to avoid some edge crossings. See the SCChart below and the attached image for an example where this could yield a diagram with at least two less edge crossings.
@ClocksUseSDscchartRollingBall {
outputfloataccel// output acceleration changeinputfloattargetV = 10// target velocity inputinputfloatcurrentV = 0// current velocity inputinputfloatKp, Ki, Kd// PID calibration variables inputinputfloatdT = 0// delta Time inputfloatprevError = 0// error in the previous tickfloaterror = 0// divergence from the target velocityfloatP, I, D// internal variables for PID calculationclockt = 0// clock for real time calculationdataflow:
prevError = errorerror = targetV - currentVP = Kp * errorI += error * tD = (currentV - prevError)/taccel = P + Ki * I + Kd* D
}
Edit 2022-04-20: included attatched image
The text was updated successfully, but these errors were encountered:
[Issue KISEMA-1609 migrated from JIRA, first reported on 2021-03-23]
In SCCharts dataflow, all simple arithmetic actors such as +, *, &, etc. which are commutative should have free port constraints to allow the layout to avoid some edge crossings. See the SCChart below and the attached image for an example where this could yield a diagram with at least two less edge crossings.
Edit 2022-04-20: included attatched image
The text was updated successfully, but these errors were encountered: