Post by matt-s on HMI Pushbutton/Move Instruction ^{CODESYS Forge talk (Post)}
I put the cross reference at the bottom of the pictures. It is not being written to elsewhere. I have tried the execute block too.
Last updated: 2024-01-26

Post by ben1 on HMI Pushbutton/Move Instruction ^{CODESYS Forge talk (Post)}
Hey mate, did you get to the bottom of this? If not, have you double checked the buttons are linked to the correct variables and/or performing the correct action? Have you tried always enabling the block to confirm false is moved to the variable if so?
Last updated: 2024-02-01

Post by camilloo on Control for Linux SL on Ubuntu Core ^{CODESYS Forge talk (Post)}
Hello, Has anyone tried running CODESYS Linux on Ubuntu Core? I'm having problems installing the runtime. The connection to UC cannot be established. I used the instruction: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_public_key_authentification.html I can connect to UC using SSH (putty, shell). Codesys can't. Do any of you have an idea?
Last updated: 2024-02-24

Post by mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Yes, this is the error the sometimes show up. What make me crazy is the fact that it happens randomly and not each times. I know very well where the problem is, in wich one program row it's located. For each actions of the state machine I have all events recorded with log on text file. it is not problematic for me to find the application point of the fault, but I need to understand why occasionally and for no apparent reason, switching the state machine and thus changing the motion FB, sends the axis into failure (but only occasionally). For example, one case that is often problematic is the execution of the Axis Halt instruction. When, after a MoveAbosulte instruction this returns the event as 'done' and indeed the axis is in standstill, the state machine first sets the move instruction to FALSE, and the next cycle sets the Halt request to TRUE. Some of the time everything works out fine. Occasionally, however, in this exchange, the axis goes into fault, also losing the OPERATIONAL state. Meanwhile, I would like to understand why the motion FB instances must still be called even after the Execute is set to FALSE, especially in view of the fact that the next instruction is programmed to abort the previous one, with BufferMode set to 'Aborting'. All these unnecessary FB calls are an unnecessary overhead on the CPU anyway. Is there any precise rule about when to cease calling the various instances? (It should precisely be the 'done' status that says this one has finished its work).
Last updated: 2024-07-18

Post by tk096 on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Meanwhile, I would like to understand why the motion FB instances must still be called even after the Execute is set to FALSE, especially in view of the fact that the next instruction is programmed to abort the previous one, with BufferMode set to 'Aborting'. All these unnecessary FB calls are an unnecessary overhead on the CPU anyway. Is there any precise rule about when to cease calling the various instances? (It should precisely be the 'done' status that says this one has finished its work). In general: - Motion function blocks have to be called until they report 'Done', 'Error', 'CommandAborted' or a subsequent motion FB with BufferMode=Aborting is started in the current cycle. - Setting the Execute input to FALSE will not abort any ongoing motion of the motion function block. For example, one case that is often problematic is the execution of the Axis Halt instruction. When, after a MoveAbosulte instruction this returns the event as 'done' and indeed the axis is in standstill, the state machine first sets the move instruction to FALSE, and the next cycle sets the Halt request to TRUE. Some of the time everything works out fine. Occasionally, however, in this exchange, the axis goes into fault, also losing the OPERATIONAL state. I think the error SMC_FB_WASNT_CALLED_DURING_MOTION is only a follow-up (and misleading) error that results from the axis not being in operational state anymore (bus problems). Is there an error 'regulator or start not set' in the device log before the error 'motion generating FB wasn't called for at least one cycle'? Which error does the respective function block (Halt.ErrorId) report?
Last updated: 2024-07-22

Post by svn123 on In Simulation Mode, logic is not executing ^{CODESYS Forge talk (Post)}
Please check the attached snapshot. I am converting an int to real and storing in rVlv01_SV and then scaling the value using LIN_TRAFO. In the bottom Status Bar of Codesys, both RUN and SIMULATION are visible. When I enter value 100 as input to INT_TO_REAL instruction and press Ctrl-F7, the value can be seen at the input but the logic seems not to work. I searched for help but could not find anything relevant. What could be the reason. Codesys ver3.5.11 svn
Last updated: 2023-12-25

Post by joep on Custom robotics kinematics model debugging ^{CODESYS Forge talk (Post)}
When trying to move my axis using any group move instruction I get the following error: SMC_CP_INVALID_PATH_ELEM and axisgroup goes into errorstop state. I tested my methods thoroughly which makes it hard for me to debug. Are there some hidden rules I need to abide to? How would one go about debugging a custom robotics model, since the information inside isn't accesible. Is it possible to find the source of where the function breaks? Any hint in the right direction would be appreciated. Best regards
Last updated: 2024-06-08

Post by mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Yes, this point is part of my misunderstanding. Why, after the execution ot the motion FBs is set to FALSE and exsecuted at lest one time, it must be continuosly called, even if the motion control it's take from another subsequent instruction. This is what I really don't undertand, but what in fact it's happening. For example, in case of stopping a MoveVelocity FB, then Halting the motion by the related FB, the axis at spot goes into error. If there was bad trigger management, the various instructions would NEVER work.
Last updated: 2024-07-18

Post by mikek10 on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
I was answering your last paragraph Meanwhile, I would like to understand why the motion FB instances must still be called even after the Execute is set to FALSE, especially in view of the fact that the next instruction is programmed to abort the previous one, with BufferMode set to 'Aborting'. All these unnecessary FB calls are an unnecessary overhead on the CPU anyway. Is there any precise rule about when to cease calling the various instances? (It should precisely be the 'done' status that says this one has finished its work).
Last updated: 2024-07-18

Post by dhumphries on install codesys runtime on linux ^{CODESYS Forge talk (Post)}
I'm running the 3.5.18.20 IDE, installed the control for linux SL package from the installer. Following the directions here: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_install_runtime_on_controller.html it says: Installing the runtime package with CODESYS on the Linux device Click Tools → Update CODESYS Control for <device> SL.</device> I don't have the update option in my tools menu. I've tried it without opening a project, as well as with a project open that uses the control for linux SL as a device. I have found the update device option by right clicking on the device in the device tree, but this only lets me change the device the project is using not load the runtime on the linux computer. Is there an updated instruction somewhere, or do I need to do some further preparation like install additional packages?
Last updated: 2023-11-04

Post by matt-s on HMI Pushbutton/Move Instruction ^{CODESYS Forge talk (Post)}
I am having an issue where the manual start/stop push buttons on the HMI are supposed to take the pumps/blowers out of auto. The logic I have attached works for the pumps, but not the blower. From what I can tell it is the exact same logic, but it is not writing a 0 to the Auto PB variable. Attached is the logic, cross reference list to show nothing else is writing to it, and the HMI screen. Any help? Am I missing something? I am using a Groov Epic PR1, my software version is 3.5 SP19 Patch 5 32 Bit.
Last updated: 2024-01-25

Sort by relevance or date