About CodeWasi

CodeWasi · ‎12-20-2023

Hello alink, could you please describe your case and the changes a bit to get an impression about the rootcauses. Otherwise its hard. or leave some describing screenshots. former version of PLCEng? Update of the same program done? Functional working and just the debugging w/o expected behaviour? Changes on the Tasks can be neglected. Bye and happy xmas.

CodeWasi · ‎12-20-2023

Hi Markus, would you mind to check the configuration via the startup parameters (PDI objects). Prepared in advance the byte stream to configure the SSI interface like the sensor seems to expect. The S20-SSI-AO Datasheet provides detailed info on how to arrange the config-data of object 0x0080. Keep in mind that this command only belongs to the SSI Interface. The AO setup is not covered. Bye Jens

CodeWasi · ‎11-29-2023

Hello, did you check/do you know the Support-Forum of the BCI Nexeed Forum: The BCI Support is concentrated in their forum https://community.developer.bosch.com/t5/Nexeed-Automation/ct-p/bosch_developers-nexeed-automation I assume the fastest help on that product can be reached directly at their plattform. Bye

CodeWasi · ‎11-21-2023

Operating with persitent vars can lead to the following compile info : "Not enough persistent memory"... Most pleople facing the memory-comment won't agree intuitively since there is much memory left and the persitent-allocation is much less then the limits. But the compiler-comment is related to the increase of additionally needed persitent memory. The compiler allocates for a persistent-variable a memory-range with additonally reserve of around 10%. That provides little flexiblity for smaller changes. In case the modificaton on the persitent var result in a bigger memory-space than available by the reserver the compiler-error pops up. Since the memory needs to reorganiszed the system needs to get rid of the former allocation! Clean/CleanAll clears the allocation-history!

CodeWasi · ‎11-02-2023

The monitoring is useful in any case since the timing e.g. may differ from core and drives. The Ecat status provides an overview to retrigger the OP-switching again (Not all slaves in Masterstate...). The data is available in the Datalayer. PLC provides the data with IL_ECATRead ...

About CodeWasi

Re: Debbung time delay with CtrlX PLC Engineering v1.20.5

Re: Absolute encoder with SSI on CtrlX-Core

Re: CtrlX PLC with Nexeed system

C0414: Not enough persistent memory - What is reasonable, what's happening?

Re: CoreX3 and EFC master sync confusion