Error 1501 on SMC_Interpolator ^{CODESYS Forge talk (Thread)}
Error 1501 on SMC_Interpolator
Last updated: 2011-05-24

SMC_Interpolator + SMC_controAxislbyPos ^{CODESYS Forge talk (Thread)}
SMC_Interpolator + SMC_controAxislbyPos
Last updated: 2024-02-08

SMC_Interpolator liefert Fehler in Simulation ^{CODESYS Forge talk (Thread)}
SMC_Interpolator liefert Fehler in Simulation
Last updated: 2018-01-06

control additional axis with smc_interpolator ^{CODESYS Forge talk (Thread)}
control additional axis with smc_interpolator
Last updated: 2021-06-04

Programm mit SMC_Interpolator funktioniert nicht mehr ^{CODESYS Forge talk (Thread)}
Programm mit SMC_Interpolator funktioniert nicht mehr
Last updated: 2010-01-11

SMC_Interpolator output to SMC_Trafo_Tripod input Error ^{CODESYS Forge talk (Thread)}
SMC_Interpolator output to SMC_Trafo_Tripod input Error
Last updated: 2019-08-27

What wrong with FB SMC_Interpolator? ^{CODESYS Forge talk (Thread)}
What wrong with FB SMC_Interpolator?
Last updated: 2024-04-30

Confused by dwIpoTime input for SMC_Interpolator ^{CODESYS Forge talk (Thread)}
Confused by dwIpoTime input for SMC_Interpolator
Last updated: 2024-07-22

SMC_Interpolator error: velocity at corner more than zero ^{CODESYS Forge talk (Thread)}
SMC_Interpolator error: velocity at corner more than zero
Last updated: 2023-06-30

Interpolation von aktueller Achsposition aus starten, statt von Referenzposition mit SMC_Interpolator? ^{CODESYS Forge talk (Thread)}
Interpolation von aktueller Achsposition aus starten, statt von Referenzposition mit SMC_Interpolator?
Last updated: 2021-04-14

Post by axilleas on SMC_Interpolator + SMC_controAxislbyPos ^{CODESYS Forge talk (Post)}
Thanks tk096. I have done projects running exactly as you described and I failed to help myself by just searching more. Thank you again
Last updated: 2024-02-08

Post by xabier on What wrong with FB SMC_Interpolator? ^{CODESYS Forge talk (Post)}
hi Getdone I have the same problem with you...Could resolved this problem?? Can you move with more speed??... I have cicle time 1 ms and the moment increase speed >5mm/s the FB SMC_Interpolator not fine work....Tell me plese if you resolved this problem Thanks Regards XABI
Last updated: 2024-04-30

Post by tk096 on Confused by dwIpoTime input for SMC_Interpolator ^{CODESYS Forge talk (Post)}
Hi, dwIpoTime should be set to the cycle time of your motion task. It defines the interpolation interval of the interpolator. E.g. in the attached screenshot, the task has a task interval of 4ms. The dwIpoTime input of the interpolator should be set to 4000.
Last updated: 2024-07-22

Post by k2saki on CNC / G01 Speed is very slow (or go-stop motion) in Continuous short segment . ^{CODESYS Forge talk (Post)}
Hi, gseidel. Thank you so much for your advice. I have created a program to preprocess G-code as follows 1.SMC_ReadNCFile2 2.SMC_Interpreter 3.SMC_CheckVelocities Then I put SMC_OUT_QUEUE in SMC_Interpolator. Where should I insert SMC_SmoothMerge and SMC_SmoothPath? Or are there any example link for it ?
Last updated: 2024-04-30

Post by trusty-squire on Confused by dwIpoTime input for SMC_Interpolator ^{CODESYS Forge talk (Post)}
OK, that makes sense. Because the FB is provided a specific interval period, it would change the target position accordingly based on the time it "thought" elapsed. If it has the wrong interval provided, it updates the target positions every cycle incorrectly so the axes will end up moving faster or slower. Thanks!
Last updated: 2024-07-22

Post by tk096 on SMC_Interpolator + SMC_controAxislbyPos ^{CODESYS Forge talk (Post)}
Hi, you can define a start position for your GCode. How the start position can be defined depends on the CompileMode: For File and SMC_CNC_REF: Set the start position input of SMC_NCInterpreter (https://content.helpme-codesys.com/en/libs/SM3_CNC/Current/SM_CNC_POUs/NC2/Interpreter/SMC_NCInterpreter.html) For SMC_OutQueue: * Right-click on the CNC object in the project tree * Select Properties * Select the tab 'CNC' * Set the start position Concerning your second question: If the new set position cannot be reached with the given velocity limit (AXIS_REF_SM3.fSWMaxVelocity), SMC_controlAxisByPos will report bStopIpo and close the 'gap' with the given gap dynamics (SMC_controlAxisByPos.fGap*).
Last updated: 2024-02-07

Post by axilleas on SMC_Interpolator + SMC_controAxislbyPos ^{CODESYS Forge talk (Post)}
dear all I am working on a very generic gantry system (virtual drives + win v3 control) reading gcode from external file. In order to stop the interpolator function from running when gaps are detected, SMC_controlAxisByPos FB has the bStopIpo output which according to the manual is connected to the Interpolator's bEmergencyStop. Lets assume that the axis are parked in position X1000 Y1000 and the initial G code movement is G00 X500 Y500. The normal behavior is to travel from the actual x1000 y1000 to G00 X500 Y500. The SMC_Interpolator always gets the X0 Y0 as the initial position, meaning that the bStopIpo is active until the axis are in X0 Y0 and the release the interpolator to set the new positions to X500 Y500. Is there a suggested method to solve this behavior? bonus question: I get a lot of bStopIpo during standard interpolation movements (not gaps). While working with virtual axis this is not a problem but when real axis are installed this will be an issue. What exactly triggers the bStopIpo output? Slow axis accelerations compare to Gcode defaults? Kind Regards
Last updated: 2024-02-05

Post by trusty-squire on Confused by dwIpoTime input for SMC_Interpolator ^{CODESYS Forge talk (Post)}
Hi, Learning Codesys CNC, and I am confused by the dwIpoTime parameter. I have a basic demo application, using SMC_Interpolator feeding into SMC_TRAFO_Gantry2Tool2, which then sets the position of the x/y SM_Drive_Virtual axis. I also have a C axis which revolves the tool, which is controlled using a simple tangential angle calculation SMC_CalcDirectionFromVector. The GCode I'm using has feed/accel set at 500. The axis configuration limits are well above that (2000). What's strange is that, when I run the simulation, the feed speed changes drastically when I update the variable dwIpoTime. The larger the number, the faster it moves. What's going on here? The documentation only says "This variable has to be set for each call. It represents the cycle time in μsec." Why does it change the feed speed I'm seeing the in simulation? What is a good number to use? The example I was looking at set it at 5000. Screenshot attached.
Last updated: 2024-07-18

Post by manuknecht on Using SMC_MOVTYP.INITPOS without specifying the start position ^{CODESYS Forge talk (Post)}
I am using the object SMC_GEOINFO to generate a trajectory and move a system accordingly using the SMC_INTERPOLATOR function block similar to the sample project CNC10_DynamicPath.project. According to the documentation, the movement type INITPOS does not require a start position in the SMC_GEOINFO object, which is confirmed in the documentation of the SMC_GEOINFO object. When using the movement type INITPOS however, the motion will still start from the starting point defined in the SMC_GEOINFO object (0,0,0 if not specified otherwise). Does someone know how to resolve this or is there an example project that makes use of the INITPOS movement type without specifying the starting point? Thanks in advance!
Last updated: 2023-12-15

Post by k2saki on CNC / G-Code streaming processing ( to start quickly in long G-Code File ) ^{CODESYS Forge talk (Post)}
Is it possible like G-Code streaming processing (like FANUC or SIEMENS DNC Function )? Or Does anyone know the tips for CODESYS Motion to start moving long Long G-Code File quickly? I have to wait long time after "Start" button to start moving, I have to wait finishing interpreting whole G-Code file, ( and I have to prepare huge buffer to store. ) Now, I'm working on my CNC Project using SMC_ReadNCFile2, and SMC_NcInterpreter to preprocess G-Code. I tried to set SMC_Interpolator.xExecute to true to Start while after SMC_NcInterpreter processed more 50-line of G-Code, but that not worked, I had to wait SMC_NcInterpreter processed all lines to start SMC_Interpolator. G-Code have about 2000 lines of XY of G01 (or more over.. ) of short segment that a CAM software has exploded from NURBS Curve.
Last updated: 2024-05-03

Post by k2saki on CNC / G01 Speed is very slow (or go-stop motion) in Continuous short segment . ^{CODESYS Forge talk (Post)}
I'm using CAD/CAM that outputs GCode with G01 many short segments from NURBS Curve, only X-Y axis. But CODESYS CNC motion seems much slower ( or stop-go motion ) in simulation mode than F-Value (I checked value from SMC_Interpolator - dVel ). In GCode G01, F value is F500, but movement is very slow, actual speed (dVel) is between 0 to 30 back and forth. I think very old CNC can move like that, but nowadays, a lot of CNC can move smoothly to process free curve ( somethimes option switch ) I tried to use G51 Dxx but I got the same result. My questions are 1) How do I improve CODESYS CNC motion in this case ? 2) How can I graph the sampling from dVel of SMC_Interpolate in CODESYS? From my GCode N2006 G01 X1.4364 Y-14.6847 F500 N2007 G01 X1.6759 Y-14.6768 N2008 G01 X1.9152 Y-14.6486 N2009 G01 X2.1547 Y-14.6400 N2010 G01 X2.3943 Y-14.6090 N2011 G01 X2.6336 Y-14.6002 N2012 G01 X2.8732 Y-14.5716 N2013 G01 X3.1127 Y-14.5634 N2014 G01 X3.3520 Y-14.5410 N2015 G01 X3.5915 Y-14.5336 N2016 G01 X3.8308 Y-14.5307 ... Thansk.
Last updated: 2024-04-29

Sort by relevance or date