Mismatch between coordinate monitor and actual motion using SMC_GroupJog2, MC_MoveLinearAbsolute (6DOF)

darwin03 — Fri, 09 Oct 2026 07:42:28 -0000

Hi Georg,

Thanks for your previous suggestion. I was able to resolve the issue!

I'm now trying to build the 6DOF robot again, but I'm not sure why this is happening. Even when I simulate it in RoboDK using the joint angles from my code, the robot's motion still seems abnormal.

Do you have any ideas what might be causing this?

Thank you for taking the time to look into my question!

Best regards,
darwin03

Video link: https://drive.google.com/file/d/1PBqS4yIY2R_CZ3celSKz-BXVRk8pCHKz/view?usp=sharing

Read a webclient value

Reinier Geers — Thu, 08 Oct 2026 19:16:24 -0000

Hi i get a json value from an energy site. Every hour a value. to cut the answer in an array so i can read every hour it try FindWString . find Marketprice. But it turns in every array on a diverent position. Why ?

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

pernockham — Wed, 07 Oct 2026 06:22:54 -0000

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?

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

pernockham — Tue, 06 Oct 2026 18:27:19 -0000

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?

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

pernockham — Tue, 06 Oct 2026 17:28:47 -0000

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. And give this information to the user by an alarm/information.

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

pernockham — Tue, 06 Oct 2026 16:35:30 -0000

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 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!

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5

TimvH — Fri, 02 Oct 2026 07:52:43 -0000

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?

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5

mankh — Thu, 01 Oct 2026 11:16:37 -0000

Thanks,You sure there are not compatibility issues with the old IFM EDS files, PDO mapping, or startup SDO configuration in CODESYS 3.5?

Codesys Virtual Safe Control mit Weidmüller UR20 FSOE Modulen

hluecke — Wed, 30 Sep 2026 14:10:28 -0000

Hallo,
ich versuche mit der Codesys Virtual Safe Control zwei Weidmüller UR20 FSOE Module zu betreiben. Allerdings läuft das zweite Modul nie an (Diagnosecode 16#C105), auch die Prozessdaten werden nicht aktualisiert. Jedes Modul einzeln läuft, auch bei getauschter Reihenfolge läuft immer das zweite Modul nicht an.
Codesys Version 3.5.22.30 mit den aktuellsten Packages. Weidmüller UR20 FBC-EC und die Module auf aktuellem Firmwarestand, neueste Gerätebschreibungsdateien.
Was mich dabei auch irritiert, ist dass beim ersten Gerät im E/A-Abbild mehr Ausgänge angezeigt werden, als beim Zweiten.
Hat schon einmal jemand so eine Kombination in Betrieb gehabt oder ein ähnliches Verhalten erlebt?
Vielen Dank!

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5

TimvH — Tue, 29 Sep 2026 12:04:18 -0000

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.

Recent posts to Talk

Mismatch between coordinate monitor and actual motion using SMC_GroupJog2, MC_MoveLinearAbsolute (6DOF)

Read a webclient value

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

How to recognize licenses SMALL, MEDIUM, LARGE by CmpCodemeter

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5

Codesys Virtual Safe Control mit Weidmüller UR20 FSOE Modulen

Legacy IFM CANopen I/O modules with CR710S / CODESYS 3.5