Unfortunately I cannot edit this ticket... So sorry for the layout issues... P.
Flexible way for text formatting - Another use of ANY type
I don't understand the point of this. Isn't just better to use __SYSTEM.AnyType instead of making your own type? Also if you wanted to make it an object, shouldn't you just wrap a FB around __SYSTEM.AnyType and then have some conversion Methods? Maybe I am missing the purpose of this code. Maybe add more details on how you would use MyMappingFB
Update: Meanwhile I understood the meaning of this call. At least I think I did. Roughly: PLEASE FEEL FREE TO CORRECT ME IF I AM WRONG, I AM STILL JUST EXPLORING IoDrvUpdateMapping is not needed, if you take care all of your input / output parameters at IoDrvUpdateConfigurtion, by providing a memory location, where the IoDrv should read/write the parameters from. This is done by assigning a pointer to memory location, probably to a variable instance with the proper type and size the parameter.dwDriverSpecific...
Hmmmm... After messing some hours with that error message, I finally found this ticket - and yes, the solution is suggested in the title. So the module, inputs, outputs were working OK, just this stupid message in the PLC Log. Seems like, in order to implement ICmpIoDrv one have to say something about Module Mapping. Looking at the Parameters for the call, I assume It has stg to do with the possible mapping of parameters to different tasks... Has stg to do with this: As all this was working OK, I...
Hmmmm... After messing some hours with that error message, I finally found this ticket - and yes, the solution is suggested in the title. So the module, inputs, outputs were working OK, just this stupid message in the PLC Log. Seems like, in order to implement ICmpIoDrv one have to say something about Module Mapping. Looking at the Parameters for the call, I assume It has stg to do with the possible mapping of parameters to different tasks... Has stg to do with this: As all this was working OK, I...
Initial
commentChange
addStart
Library Manager -> Library Parameters (near placeholders) There you can change parameters like the max number of test suites, the max number of tests per test suite or the max number of asserts per test
this can be closed BTW
I think this is the same or similar to https://forge.codesys.com/lib/counit/tickets/58/ I figured out that this was occurring because assert was being called continuously
MQTT Host Library VfInit
MQTT Host Library VfInit