Search talk: -128到127是什么数据类型

 
<< < 1 .. 881 882 883 884 885 .. 922 > >> (Page 883 of 922)

Post by timvh on Active vs Unacknowledged Alarm CODESYS Forge talk (Post)
See: https://forge.codesys.com/forge/talk/Engineering/thread/33ecf1ac41/
Last updated: 2026-09-29

Active vs Unacknowledged Alarm CODESYS Forge talk (Thread)
Active vs Unacknowledged Alarm
Last updated: 2026-09-29

PM564 online problem CODESYS Forge talk (Thread)
PM564 online problem
Last updated: 2026-09-29

Post by timvh on Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5 CODESYS Forge talk (Post)
Yes, you can use the .eds files also in CODESYS 3. Install them through the menu Tools - Device Repository. Then you can add the CANopen devices to your CANopen manager in your device configuration.
Last updated: 2026-09-29

OPC-Server V3 - keine Items zu sehen... CODESYS Forge talk (Thread)
OPC-Server V3 - keine Items zu sehen...
Last updated: 2026-09-29

Post by timvh on PM564 online problem CODESYS Forge talk (Post)
You cannot. The code in the PLC is compiled. You either need the source code, or create a new application.
Last updated: 2026-09-29

Post by mankh on Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5 CODESYS Forge talk (Post)
Thanks,You sure there are not compatibility issues with the old IFM EDS files, PDO mapping, or startup SDO configuration in CODESYS 3.5?
Last updated: 2026-10-01

Post by timvh on Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5 CODESYS Forge talk (Post)
I don't work for IFM, nor for CODESYS and didn't create the .eds file or developed the CAN protocol. I have no knowledge of the exact contents and SDO's or PDO's which are exchanged. So no, I am not sure. But if the .eds file confirms to the CANopen specifications, why shouldn't it?
Last updated: 2026-10-02

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5 CODESYS Forge talk (Thread)
Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5
Last updated: 2026-10-02

Post by pernockham on How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter CODESYS Forge talk (Post)
Im trying to read out active license by CmpCodeMeter but am not sure of the combination of ProductCode and FeatureMap that each of CONTROL, VISU and COM / SMALL, MEDIUM, LARGE equals. Started by trying CodeMGetContentByFirmcode (and productCode) expecting error 18 / Not Available if asking for a higher level of license compared to what I know is active, but function just returned the requested productcode and a featuremap Is this the way or is it better to use CodeMOpen? Which seems to also require a featureCode. Where can I find info on required featureCode? ProductCodes according to google: Control (PLC Runtime) Small (S) 16#00002FFF 12287 * Medium (M) 16#00003000 12288 Large (L) 16#00003001 12289 Visualization (WebVisu) Small (S) 16#00003002 12290 Medium (M) 16#00003010 12304 * Large (L) 16#00003003 12291 Communication (Com) * Small (S) 16#00003004 12292 Medium (M) 16#00003005 12293 Large (L) 16#00003006 12294 Thanks!
Last updated: 2026-10-06

Post by pernockham on How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter CODESYS Forge talk (Post)
Solved finally, in short by: listening to eventId = EVT_CmpMgr_LicenseState, make a callback, extract the event-parameter which contains the RUNTIME_LICENSE_STATE. This gives me the license state as LICENSED / LICENSED_LOS / DEMOMODE etc. What Im not certain of at this point is this the aggregation of all three licenses or just the RUNTIME? Ie, what if my CONTROL-license is ok but my Visu-license is to low, will that set LICENSE_LOST, or would I need other listeners to find out if my VISU will shut down?
Last updated: 2026-10-07

Post by pernockham on How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter CODESYS Forge talk (Post)
I think google has fooled me here, the only thing I can conclude so far is what i now from reading the licenseManager, which tells me that my valid license have the following product-code CONTROL - 16#3000 VISU - 16#3003, feature map: 1000 COM - 16#3004, feature map: 0200 Will different level of license give different product codes or will I see the active license level by other means? What I am trying to achieve is block Starting a machine with time limited operation should the application be larger than what the license permits (DEMO-mode). And give this information to the user by an alarm/information.
Last updated: 2026-10-06

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter CODESYS Forge talk (Thread)
How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter
Last updated: 2026-10-07

Post by pernockham on How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter CODESYS Forge talk (Post)
Third update. I figured that even knowing the level of the license, it will not tell me if its level is enough for the current application. There must be some other way to find this out? I see a component CM write in the Log if starting without license-dongle. "License lost - time left.. " Can I access this CM to check status from inside the application? This function is essential, why is it so hard to find info about implementation?
Last updated: 2026-10-06

Post by gseidel on Mismatch between coordinate monitor and actual motion using SMC_GroupJog2, MC_MoveLinearAbsolute (6DOF) CODESYS Forge talk (Post)
Hi darwin01, looking at the video and comparing the movement with the first figure in https://content.helpme-codesys.com/en/libs/SM3_Transformation/Current/SM3_Transformation/Function-Blocks/Standalone-Kinematics/Articulated-Robots/6AxisArticulated/Kin_ArticulatedRobot_6DOF.html, I think that the direction of rotation does not match between the RoboDK model and the CODESYS 6DOF kinematics. In the CODESYS kinematics, A1 and A2, when moved in positive direction, rotate into the opposite direction to what the RoboDK model does. This could explain the strange movements. For real axes, you could change the direction using the "Invert direction" flag of the scaling/mapping page. For your simulation, you could manually invert the position of the axes A1 and A2 before sending them to RoboDK. (A0 seems correct, please also check A3, A4, and A5. The figure I mentioned gives the order of positive rotation with arrows through the joints. You can use the right-hand-rule to see what the positive rotation is.) Best regards, Georg
Last updated: 2026-10-12

Visualization 🇬🇧 CODESYS Forge talk (Discussion)
Realizing operator screens with CODESYS HMI, Targetvisu, Webvisu
Last updated: 2026-10-12

Alarm Manager - Disk IO Error and Memory Double Free Exception CODESYS Forge talk (Thread)
Alarm Manager - Disk IO Error and Memory Double Free Exception
Last updated: 2026-10-12

Post by josul on Alarm Manager - Disk IO Error and Memory Double Free Exception CODESYS Forge talk (Post)
I have encountered an issue with Alarm management. A simple Alarm table to display active alarms. Historical alarms can be hidden and can also be cleared. Overall a history of 10000 alarms before it cycles. On one instance this error displayed: "Some kind of disk I/O error ocurred. Check disk space". Picture attached. I have seen this with an online change, but it was resolved by a full download. But this case was running for weeks and displaying alarms fine. The logged errors though were unusual. Associated log entries (multiples of these were logged): 2026-10-07T12:17:17.603Z, 0x0000001f, 8, 1, 0, #### Exception: Memory double free detected: <cmp>AlarmConfig</cmp> <addr>0x80330d0</addr> And later in the same day, the entire application encountered an exception: 2026-10-07T19:33:48.583Z, 0x00000011, 8, 81, 3, #### Exception: *EXCEPTION* [<excpt>AccessViolation</excpt>] occurred: App=[<app>Application</app>], T> 2026-10-07T19:33:48.583Z, 0x00000011, 8, 81, 3, #### Exception: *SOURCEPOSITION* App=[<app>Application</app>] area=<area>0</area>, offset=<off>9548256> I haven't found any explanation for a "Memory double free detected" and I'm unsure how to prevent it occurring. I suspect it might be the cause of the "Access Violation" exception, but how can I be sure of this? Would defining VISU_NO_EXCEPTION_HANDLING be advisable or not in a production environment? Any advice is welcome.
Last updated: 2026-10-12

Post by eschwellinger on Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running... CODESYS Forge talk (Post)
CODESYSControl_User.cfg [CmpCharDevice] PermittedPath.0=/dev/i2c PermittedPath.1=/dev/spidev PermittedPath.2=/sys/class/gpio/ PermittedPath.3=/dev/gpiochipPerm will be solved to 4.23.0.0 release
Last updated: 2026-10-15

Deutsch 🇩🇪 CODESYS Forge talk (Discussion)
German forum
Last updated: 2026-10-19

Post by dmb-fan on Nach "Alles Bereinigen" viele unklare Fehler, aber nur in Schrittketten CODESYS Forge talk (Post)
Offiziele CoDeSys Rückmeldung: Der Fehler ist bekannt und erfasst mit SFC-224 SFC with parallel branch without name is no more compilable. Das ist ein Accident zu 4.5.0.0. Lösung ist also entweder:  Downgrade auf SFC 4.4.0.0 oder  Vergabe von Namen für die parallelen Zweige
Last updated: 2026-10-19

Nach "Alles Bereinigen" viele unklare Fehler, aber nur in Schrittketten CODESYS Forge talk (Thread)
Nach "Alles Bereinigen" viele unklare Fehler, aber nur in Schrittketten
Last updated: 2026-10-19

Post by dmb-fan on Hilscher cards CoDeSys Control RTE CODESYS Forge talk (Post)
You have to know this (and the crap help site don't tell you): - Changes in CODESYSControl_User.cfg, not in CODESYSControl.cfg (crash of PLC/Win possible) - Redundancy is important for Profibus, also if you don't use it because the libarys depending on it - The no. after the device is the slot numer for PLC device config [ComponentManager] Component.1=CmpDrvSchedulerAMP Component.2=CmpCodeMeter Component.3=CmpHilscherCIFX Component.4=CmpNetXCanDlDrv ; this is not in help, but thats makes the internal driver load Component.5=CmpRedundancy Component.6=CmpRedundancyConnectionIP [CmpHilscherCIFX] TraceLevel=0xFFFFFFFF InterruptMode=0 DMAMode=1 ;DynamicFirmware=1 BootloaderFile=$Firmware$/HilscherCIFX/Firmware/NETX100-BSL.bin FirmwareFilePath=$Firmware$/HilscherCIFX/Firmware ;non-dynamic declaration of FW-files: ; 100 !!! CIFIX50 cards but files called 100 !!! Device.0.BootloaderFilePath=$Firmware$\HilscherCIFX\Firmware\NETX100-BSL.bin Device.0.Channel.0.FirmwareFile=$Firmware$\HilscherCIFX\Firmware\cifxcom.nxf Device.1.BootloaderFilePath=$Firmware$\HilscherCIFX\Firmware\NETX100-BSL.bin Device.1.Channel.0.FirmwareFile=$Firmware$\HilscherCIFX\Firmware\cifxdpm.nxf ;;;; And good luck, you will need it ! ;;;;
Last updated: 2026-10-23

Hilscher cards CoDeSys Control RTE CODESYS Forge talk (Thread)
Hilscher cards CoDeSys Control RTE
Last updated: 2026-10-23

Post by dmb-fan on Hilscher cards CoDeSys Control RTE CODESYS Forge talk (Post)
the information "license completly by Codesys" is WRONG. For DP Master function you need the license from Hilscher, too.
Last updated: 2026-10-22

<< < 1 .. 881 882 883 884 885 .. 922 > >> (Page 883 of 922)

Showing results of 23037

Sort by relevance or date