Activity for dawidr
-
dawidr modified a comment on discussion Engineering 🇬🇧
Hi! What are the best practices for querying multiple Modbus devices? Single PRG or maybe multiple PRG (so basically multiple thread) per each Modbus device. In my current implementation I'm using single PRG and I'm utilizing FbMbMasterMultiQuerySerial and WagoAppPlcModbus.FbDigitalTwinMbSlaveDevice in eCockpit with PFC200. I've the timer with 2 seconds delay there and it was working fine for single device. But now I have three Modbus devices and for two of them I need to run 2/3 queries to get data...
-
Hi! What are the best practices for querying multiple Modbus devices? Single PRG or maybe multiple PRG (so basically multiple thread) per each Modbus device. In my current implementation I'm using single PRG and I'm utilizing FbMbMasterMultiQuerySerial and WagoAppPlcModbus.FbDigitalTwinMbSlaveDevice. I've the timer with 2 seconds delay there and it was working fine for single device. But now I have three Modbus devices and for two of them I need to run 2/3 queries to get data from all registers....
-
-
Did you manage to solve the problem with time out? I got the same issue and I've no idea what I'm doing wrong.
-
Did you manage to solve the problem with time out? I got the same issue and I've no idea what I'm doing wrong.
-
Did you manage to solve the problem with time out? I got the same issue and I've no idea what I'm doing wrong.
-
Well, that is what I did but I wonder if there is something build-in.
-
Is there build-in function block which acts like R_TRIG and F_TRIG at the same time? So basically detects both rising or falling edge?
-
@GaryPratt I learned that yesterday evening by reading the CodeSys documentation where it is stated that: CODESYS always treats variables declared with the type of an interface as references
-
@GaryPratt I learned that yesterday evening by reading the CodeSys documentation where it is stated that: CODESYS always treats variables declared with the type of an interface as references
-
I'm using Wago PFC200 for my home automation. I got base function block: FUNCTION_BLOCK ABSTRACT Room and two the interface: INTERFACE IBlinds - BlindsUp - BlindsDown and ILights -TurnOffLights -TurnOnLights My room's instances looks like this: FUNCTION_BLOCK Garage EXTENDS Room IMPLEMENTS ILights, IBlinds In my PLC_PRG I've all instances of my rooms: PROGRAM PLC_PRG VAR Bedroom: Bedroom; Garage: Garage; Hall: Hall; Boilerroom: Boilerroom; ... END_VAR Under the PLC_PRG I've some methods to e.g.:...
-
I'm using Wago PFC200 for my home automation. I got base function block: FUNCTION_BLOCK ABSTRACT Room and two the interface: INTERFACE IBlinds - BlindsUp - BlindsDown and ILights -TurnOffLights -TurnOnLights My room's instances looks like this: FUNCTION_BLOCK Garage EXTENDS Room IMPLEMENTS ILights, IBlinds In my PLC_PRG I've all instances of my rooms: PROGRAM PLC_PRG VAR Bedroom: Bedroom; Garage: Garage; Hall: Hall; Boilerroom: Boilerroom; ... END_VAR Under the PLC_PRG I've some methods to e.g.:...
-
I manage to figure it out by myself. You need to generate the code and in the messages you will see how much memory free (in bytes and in percentage):
-
I manage to figure it out by myself. You need to generate the code and in the messages you will see how much memory free (in bytes and in percentage):
-
I manage to figure it out by myself. You need to generate the code and in the messages you will see how much memory free (in bytes and in percentage):
-
I manage to figure it out by myself. You need to generate the code and in the messages you will see how much memory free (in bytes and in percentage):
-
I don't know how it looks like in CodeSys but in Wago e!Cockpit you can add Persistent Variables file but right clicking on the application and selecting it from the menu like this:
-
Hi, Is there a way to check how much of RETAIN PERSISTENT memory is used for PLC PFC200 in e!Cockpit?
-
What is the best way to make an HTTP request? I'm using e!Cockpit and Structured Text and I need to make an HTTP request to one of my Shelly 1 relays to turn on the light. It will look like: https://IP_ADDRESS/relay/0?turn=on or https://IP_ADDRESS/relay/0?turn=off and I don't care about the response.
-
I've problems with BLIND_NIGHT from OSCAT BUILDING. This function block seems not to be working in my case. I've been connected to the PLC when the sunset comes and nothing happened My code looks like this: FUNCTION_BLOCK Blind VAR_INPUT xBlindDown: BOOL; xBlindUp: BOOL; xAutoSunset: BOOL := FALSE; xAutoSunrise: BOOL := FALSE; tSunsetOffset: TIME; tSunriseOffset: TIME; END_VAR VAR_OUTPUT xBlindControlUp: BOOL; xBlindControlDown: BOOL; END_VAR VAR BlindInput: OSCAT_BUILDING.BLIND_INPUT := (SINGLE_SWITCH...
-
I've problems with BLIND_NIGHT from OSCAT BUILDING. This function block seems not to be working in my case. I've been connected to the PLC when the sunset comes and nothing happened My code looks like this: FUNCTION_BLOCK Blind VAR_INPUT xBlindDown: BOOL; xBlindUp: BOOL; xAutoSunset: BOOL := FALSE; xAutoSunrise: BOOL := FALSE; tSunsetOffset: TIME; tSunriseOffset: TIME; END_VAR VAR_OUTPUT xBlindControlUp: BOOL; xBlindControlDown: BOOL; END_VAR VAR BlindInput: OSCAT_BUILDING.BLIND_INPUT := (SINGLE_SWITCH...
-
I'm having some problems with blinds (described in separate post) and I started to think that maybe I'm using outdated libraries. Where I could find the latest OSCAT Basic and OSCAT Building libraries for Wago e!Cockpit? Where there any updates in last few years?
-
I was trying almost everything with no luck. With such an approach buttons works fine: BlindControl( UP := BlindSecurity.QU, DN := BlindSecurity.QD, S_IN := BlindSecurity.STATUS, PI := BlindSecurity.PO ); But in this case there is an automatic calibration which I don't like. All blinds are going up and then down. I'm going to move in to new house within a week, I will be modifying my program a lot a the beginning , I don't want the blinds to move witch each download. Witch such approach the calibration...
-
I'm using OSCAT library to control blinds. Everything works fine but I would like to get rid of automatic calibration after power failure built in the BLIND_CONTROL_S function block. As it is written in the last sentence the "The automatic calibration however can be prevented if both inputs UP and DN are FALSE". And it actually stops the blinds to be calibrated (basically moving up) but afterwards I can't control the blinds any more - UP and DOWN buttons are not working. BlindControl( UP := FALSE,...
-
I'm using OSCAT library to control blinds. Everything works fine but I would like to get rid of automatic calibration after power failure built in the BLIND_CONTROL_S function block. As it is written in the last sentence the "The automatic calibration however can be prevented if both inputs UP and DN are FALSE". And it actually stops the blinds to be calibrated (basically moving up) but afterwards I can't control the blinds any more - UP and DOWN buttons are not working. Anyone has successfully turn...
-
I'm using OSCAT library to control blinds. Everything works fine but I would like to get rid of automatic calibration built in the BLIND_CONTROL_S function block. As it is written in the last sentence the "The automatic calibration however can be prevented if both inputs UP and DN are FALSE". And it actually stops the blinds to be calibrated (basically moving up) but afterwards I can't control the blinds any more - UP and DOWN buttons are not working. Anyone has successfully turn it of?
-
I'm using OSCAT library to control blinds. Everything works fine but I would like to get rid of automatic calibration built in the BLIND_CONTROL_S function block. As it is written in the last sentence the "The automatic calibration however can be prevented if both inputs UP and DN are FALSE". And it actually stops the blinds to be calibrated (basically moving up) but afterwards I can't control the blinds any more - UP and DOWN buttons are not working. Anyone has successfully turn it of?
-
I don't known what kind of project you are working and what is a structure of your code but take a look at my post here: https://forge.codesys.com/forge/talk/Engineering/thread/ed30e6d1a1/. I'm using Wago PFC200 in my home automation project and in order to save me from such kind of issues I'm not storing whole function blocks in persistent memory. Even though, my data is rather small (for now, who knows how it will grown...). I've extracted all variables which needs to be stored in persistent memory...
-
I know about "Declarations/Add all instance paths" function but I was thinking that it will store the whole function block in the retain memory area. Just like it was written in the manual (https://help.codesys.com/api-content/2/codesys/3.5.12.0/en/_cds_vartypes_retain_persistent/). I will try to do some tests just like you did in your post.
-
That is the question I'm also looking answer for! Anyone has more info?
-
I'm using WAGO PLC PFC200 in my home automation project. I've plenty of POUs, each for one room. Each room implements IRoom interface and uses base POU for common logic like turning off all lights. For lights management, I'm using FbEvaluateShortLongPress from WagoAppBuilding to handle short and long press of buttons on the wall (it could also be a function block from OSCAT library) FbLatchingRelay from WagoAppBuilding as a toggle for PLC digital output I want to save the state of FbLatchingRelay...
-
I'm using WAGO PLC PFC200 in my home automation project. I've plenty of POUs, each for one room. Each room implements IRoom interface and uses base POU for common logic like turning off all lights. For lights management, I'm using FbEvaluateShortLongPress from WagoAppBuilding to handle short and long press of buttons on the wall (it could also be a function block from OSCAT library) FbLatchingRelay from WagoAppBuilding as a toggle for PLC digital output I want to save the state of FbLatchingRelay...