Hello, i am facing a problems when configuring my Acopos Drive digital Inputs on the channels. I put the source to ‘Force by function block’, and transfer it to the PLC, but they are still changed by the physical electric input.
When I open Mapp cockpit it says the source is ‘not used’ even though I can see the input changes with the electric signal.
When I change it to ‘Force by function block’ in Mapp Cockpit, it works, and I can control the input with the ‘MC_BR_ForceHardwareInputs’ FB.
It seems kind of problematic that these settings can not be configured in the configuration file for the drive.
Has anyone had similar issue, or know how to fix it?
Mapp Motion 5.27.1
The settings in the configuration file that for some reason is not written to the drive:
How it is after transferring and rebooting:
Changing it in Mapp Cockpit:
Then it works as it should have done based on the settings in the configuration file…
EDIT / Update:
The issue seems to be when MpAxisBasicConfig FB is used.
When the configuration is read to a variable and later written back in to the drive, for some reason it overwrites the digital inputs with the source ‘not used’, if the initial configuration of any input was set to ‘Force by functionBlock’.
The only solution I see is to not use MpAxisBasicConfig, and just use ‘MC_BR_ProcessParam’ instead.
Please let me know if you have encountered similar and have any fixes.
Thanks 
Hi,
I have just tried it with 5.27.1, no problem.
Is there perhaps any motion error visible in the mappCockpit that could have interrupted the initialization phase of the axis?
On the other hand, you could try ‘force initial initialization’ so that all configuration files are written cleanly.
1 Like
Hi,
There are no visible errors in the logger or in mappCockpit. Beside this issue the axes operate as intended, and other changes to the configuration file does work (Mechanical elements)
Initial install did not work.
The issue remains. Any other ideas? I must admit i am completely clueless on what can be the cause.
Does my runtime versions look like yours, in the project where you had it working?
Hello Nicklas,
to let us investigate this phenomenon please post the following files.
From your project: <your_project_name>\Binaries\ <your_config_name> \ <your_cpu_name>\ashwac.br
A drive log saved with mapp Cockpit after the start-up of the system (after the axis changes to state Disabled).
I have further investigated, and found out the issue is not with the configuration file. Initially it is written correctly.
But when I am using the ‘MpAxisBasicConfig’ FB the error occurs when writing to the config file.
I am currently investigating why it does not overwrite with ‘not used’ when inputs are default values. But when I change just one of them to ‘Force by functionBlock’ all inputs are overwritten with ‘not used’
I will keep on looking into this, and figure out exactly what is read and written via the data type, and add more information, when I have figured it out.
I have run it in debug mode one cycle at a time to figure out when it changes from ‘force by functionBlock’ to ‘not used’
I can see that when running the write operation of the ‘MpAxisBasicConfig’ FB, the digital inputs are changed to ‘not used’ at this point:
Screenshot of output in MappCockpit, showing the latest action, which resulted in the inputs to be changed to ‘not used’
Data variable after reading the current config:
Data variable while MpAxisBasicConfig is writing, after the digital inputs have been changed to ‘not used’ for some reason?
Digital input sources are not supported in V5.27.x but will be in V5.28.
Here is the entry fom the Version information:
MpAxisBasicConfig: Extended support for section “Digital inputs”
Section “DigitalInputs” of structure MpAxisBasicConfigType has been extended and now supports the configuration and parameterization of the digital input source and all associated properties.
Ok thank you. But the weird part is I do not change anything regarding the Digital Inputs while using ‘MpAxisBasicConfig’, and yet it overwrites the initial settings in the config file.