serialinterface
| FORUM | LATEST POST | # TOPICS |
|---|---|---|
|
General Discussion Forum about anything you want to talk about. |
Moehahahahah by Ingo 2019-11-22 |
2 |
Recent Activities
-
skyefire
posted
a comment
on
discussion Engineering 🇬🇧
I'll try out the "always update" setting, thanks. But I am using them in code. I have some "blinking LED" code running where I mapped my MainTask local variables to the %Q bits of the Turck module. In the CodeSys EIP Mapping screen, I can see the %Qs changing state. But the actual "physical" outputs on the Turck module (ie, the output indicator LEDs on the module) never light. The %Is are the same, but in reverse -- I can trigger the hardware inputs and see the LEDs light, but the %Is in the Mapping...
-
Chris.O
posted
a comment
on
discussion Visualization 🇬🇧
create a variable which is blinking (e.g. with Blink FB) and write this variable into the "invisible" property
-
maespinosa
modified
a comment
on
discussion Engineering 🇬🇧
Hi, I've created a project in Codesys interface. After, I've exported project tree in PLCopenXML from python scripts. Then I create a Codesys project from python using the exported files. When I print library information I have some error libraries because placeholders can not be resolved. Is it a way to resolve placeholders libraries from Python? Here is the libraries information: *Library Manager: Error: Could not open library '#CBML'. (Reason: The placeholder library 'CBML' could not be resolved.)...
-
jaka
posted
a comment
on
discussion Engineering 🇬🇧
I tryed the scrip but it did not work. It shows an error at line with "byte0 = input["Byte0"]" It says "Operation not allowed on simple types"
-
eschwellinger modified a comment on discussion Motion 🇬🇧
If you use the generic DS402 driver these parameter should be there. In which version is SoftMotion? You could update SoftMotion by updating the SoftMotion package, current version is 4.9.0.0
-
If you use the generic DS402 driver these parameter should be there. In which version is SoftMotion? You could update SoftMotion by updating the SoftMotion package, current version is 4.9.0.0
-
mike-at-gms posted a comment on discussion Motion 🇬🇧
I did not know about the device configuration option, thank you. I have an 'axis' function block that encapsulates all the functionality of an axis. All the MC function blocks are included and cyclically called based on inputs to the main FB. My motion FB's are all called the same way, which is why this error is so frustrating. I cannot see any difference between my calls to MC_Power or MC_MoveAbsolute and my call to MC_Home. I would expect a different error if my drive object was not configured...
-
The drives are slightly different in case the of the behavior, which bit should set homing etc... There are some parameters to set may this helps. See attached picture. ( You need to enable Tools-options->device editor ->'show generic device configuration views' to see this parameter page. Another point to check in which task do you call the mc_home FB?
-
The drives are slightly different in case the of the behavior, which bit should set homing etc... There are some Parameter to set may this helps. Another point to check in which task do you call the mc_home FB?