Activity for mr337
-
mr337 posted a comment on discussion Engineering 🇬🇧
I ran into same issue. Just updated the Codesys Automation plugin and now Codesys refuses to start. Error Message: the installation is corrupted, executing it would result in unpredictable behavior.
-
Wow I ran into the same thing. Can't believe this is even an issue. Thanks!!
-
FAQ page not working
-
I too am running into something similar. The issue is the library has been installed. In this case I'm running into issues with CANbusDevice and IoDrvJ1939. Funny enough the libraries are installed in C:\ProgramData\CODESYS\Managed Libraries\3S - Smart Software Solutions GmbH. I can see them but Codesys refuses to find them :S
-
Dang, thanks for the info!
-
Thanks for the info. For our application we need to be able to pull the logs "if needed" from the PLC. No network available to send etc. The part that caught me by surprise is I thought this would be part of the standard tooling from CodeSys or a solved solution but very much feels like a roll your own. I'll look into the Datalog Manager and Alarm Manager. Also found [1] Persistence Manager as well. Sooo many options lol 1 - https://help.codesys.com/webapp/f_application_composer_persistence_mana...
-
Is the project file corrupted some how? Getting the following when trying to open in CodeSys 3.5 SP11
-
Hi! How is it possible to log events for auditing such as when a sensor has hit a state, user press e-stop, or event has occured? Does anyone have a working example of logging application events to be retained after a power cycle? Things I have found: - AC_Persist library that looks to have CmpLog [1] - cannot find any documentation and sadly sample project won't open - Writing to a dedicated CSV file, concerned of a bad implementation and wearing out flash storage or overwriting system files etc...
-
Wanted to add that worked perfectly. An interesting thing is the ReceiveWatchdog has an xEnabled param while the ReceiveParameterGroup need a rising edge signal. I think as a general rule the rising edge frequency needs to be faster than the timeout on the ReceiveWatchdog.
-
Ah, I was some what close! I saw ReceiveWatchdog and thought it was only at the ECU leve. Gotta try this!
-
Hi All, I am looking into getting the last received timeout for a specific PGN. I am interfacing with a few actuators that use the same address ECU address 0, but different reporting PGN to separate the actuators. In addition the PGN does not have a heartbeat bit or byte of anykind. This is not ideal but outside our ability to change. In Codesys we build out an Actuator remote ECU and all actuators report back to the ECU, just under different PGNs. The issue is using the ECU watchdog will only check...
-
So funny enough we had another ECU device that started having issue. The vendor broke down the DM messages for us and sounds like I'll be deep diving on the DMs one way or another as I missed this during implementation. From the responses it sounds like either 1003h array or DMs are the way to go. I appreciate the responses!
-
New Codesys user seeing if anyone has a good design or pattern for handling application specific errors to be sent over canbus/j1939 for notification to the user. Application errors such as e-stop engaged, voltage not in bounds, or circuit disconnected etc to help inform the user what is wrong. Possible Requirements: 1. Persistent till error condition clears up in the event a high priority message on the bus comes in 2. Only have to be one error code at a time, variable error list would be nice :)...