Activity for Alexey
-
Alexey posted a comment on discussion Engineering 🇬🇧
Hi CoDeSys! Another question about CANOpen Device Stack. Is Expedited, Segmented or Block SDO transfer mode supported on stack level? I need to transfer large portion of data between two PLCs over CAN using SDOs and could not find any suitable solution...
-
Hi eschwellinger! Thank you for reply, I always use method described above. I am using IFM CR710S combined Standard/Safety PLC and this code sits on Safety PLC side. I think the problem is that safe retain GVL, safe PLC_PRG, non-safe PLC_PRGs and CANOpen Slave Device stack on Safety PLC have either different starting sequences OR non-safe PRG (to which I am only allowed to map CANOpen Slave Device variables) are randomly "floating" within task time because safe data processing takes highest priority....
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I'm playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
GDay guys! I playing with CANOpen Slave Device in CoDeSys 3.5.11.0 and trying to achieve behaviour of any off-the-shelf CANOpen slave device (encoder, inclinometer, etc...) inside CoDeSys, particularly with SDOs. Usually then you use any CANOpen configuration software (e.g. IFM Maintenance) to change SDO parameter of any CANOpen slave, the change is either automatically retained OR you should write "SAVE" string to 0x1010h and power cycle device. Unfortunately I could not achieve similar behaviour...
-
I am using IFM CR1058 display which has build-in keyboard and has NO touchscreen. I am using standard keyboard handling. Codesys manual says, that if I operate keyboard arrows (UP, DOWN, LEFT, RIGHT) the focus jumps to the element that is in the direction as indicated by the arrow. And if I press INPUT (ENTER) the visualization detects INPUT at the focused element and triggers the input action. This all works fine, except for the fact that if I trigger user action to call VisuDialogs.Keypad and keep...
-
I am using IFM CR1058 display which has build-in keyboard and has NO touchscreen. I am using standard keyboard handling. Codesys manual says, that if I operate keyboard arrows (UP, DOWN, LEFT, RIGHT) the focus jumps to the element that is in the direction as indicated by the arrow. And if I press INPUT (ENTER) the visualization detects INPUT at the focused element and triggers the input action. This all works fine, except for the fact that if I trigger user action to call VisuDialogs.Keypad and keep...
-
I am using IFM CR1058 display which has build-in keyboard and has NO touchscreen. I am using standard keyboard handling. Codesys manual says, that if I operate keyboard arrows (UP, DOWN, LEFT, RIGHT) the focus jumps to the element that is in the direction as indicated by the arrow. And if I press INPUT (ENTER) the visualization detects INPUT at the focused element and triggers the input action. This all works fine, except for the fact that if I trigger user action to call VisuDialogs.Keypad and keep...
-
Hi mate! There is a special PLC described in this topic: https://forge.codesys.com/forge/talk/Visualization/thread/7bfd114b72/ Which required such function, but after long discussion with the manufacturer, they decided to add key change functionality in the future
-
Hi guys! In Visualization MAnager there is a check-box "Activate standard keyboard handling". I need to turn this option ON and OFF from the code in real time. Is there any way to do it?
-
Yes its possible with pointers. See code example below. This was done for IFM basic screen and example is using left and right arrow keys to move across STRING line and up and down keys to increment/decrement single character. Bottom part of the code blinks between '_' and entered symbol to give user some sort of idea which character of string is located on. PROGRAM VISU VAR_IN_OUT SYNC: ST_SYNC; IO: ST_IO; END_VAR VAR sIdentifier: STRING; sIdentifierBuffer: STRING; fbBlink: BLINK; pCharacter: POINTER...
-
Hi guys! I have a PLC without touch screen and 4 hardware key buttons: https://crosscontrol.com/en-us/products/ccpilot-vi CrossControl made these 4 hardware buttons as standard keyboard keys 'C', 'D', 'E', 'F'. From the Visualization Manager's point of view if I activate standard keyboard handling I will get 4 keyboard buttons 'C', 'D', 'E', 'F' which are a bit useless for visualization as I don't have 'UP', 'DOWN', 'LEFT', 'RIGHT' arrows for table navigation, 'ENTER', 'TAB', 'ESC' for dialogs, etc......
-
Hi guys! I have a PLC without touch screen and 4 hardware key buttons: https://crosscontrol.com/en-us/products/ccpilot-vi CrossControl made these 4 hardware buttons as standard keyboard keys 'C', 'D', 'E', 'F'. From the Visualization Manager's point of view if I activate standard keyboard handling I will get 4 keyboard buttons 'C', 'D', 'E', 'F' which are a bit useless for visualization as I don't have 'UP', 'DOWN', 'LEFT', 'RIGHT' arrows for table navigation, 'ENTER', 'TAB', 'ESC' for dialogs, etc......
-
Hi guys! I have a PLC without touch screen and 4 hardware key buttons: https://crosscontrol.com/en-us/products/ccpilot-vi CrossControl made these 4 hardware buttons as standard keyboard keys 'C', 'D', 'E', 'F'. From the Visualization Manager's point of view if I activate standard keyboard handling I will get 4 keyboard buttons 'C', 'D', 'E', 'F' which are a bit useless for visualization as I don't have 'UP', 'DOWN', 'LEFT', 'RIGHT' arrows for table navigation, 'ENTER', 'TAB', 'ESC' for dialogs, etc......
-
Hi guys! I have a PLC without touch screen and 4 hardware key buttons: https://crosscontrol.com/en-us/products/ccpilot-vi CrossControl made these 4 hardware buttons as standard keyboard keys 'C', 'D', 'E', 'F'. From the Visualization Manager's point of view if I activate standard keyboard handling I will get 4 keyboard buttons 'C', 'D', 'E', 'F' which are a bit useless for visualization as I don't have 'UP', 'DOWN', 'LEFT', 'RIGHT' arrows for table navigation, 'ENTER', 'TAB', 'ESC' for dialogs, etc......
-
Hi guys! I have a PLC without touch screen and 4 hardware key buttons: https://crosscontrol.com/en-us/products/ccpilot-vi CrossControl made these 4 hardware buttons as standard keyboard keys 'C', 'D', 'E', 'F'. From the Visualization Manager's point of view if I activate standard keyboard handling I will get 4 keyboard buttons 'C', 'D', 'E', 'F' which are a bit useless for visualization as I don't have 'UP', 'DOWN', 'LEFT', 'RIGHT' arrows for table navigation, 'ENTER', 'TAB', 'ESC' for dialogs, etc......