C50 and C80 has different REGMEM sizes

Ask Questions
1

This is more of an observation than a question. Maybe it helps someone. This information is not available in AS Help. The C50 has atleast 1214 bytes (Exact size is unknown) REGmem and C80 only has 900 bytes. The implication is that the entire IT setup (IP, Hostname, Subnet, Gateway, DNS) cant be set as non-volatile during runtime using AsARCfg on C80. A error is caused when attempting this. This can be done on C50. An image of our use case is attached below. Calling DNS as volatile on each restart is an option I consider as workaround. Any ideas on workarounds?

IT_Setup
IT_Setup1527×916 89.7 KB

The exact error the C80 produces.

image
image1059×391 7.91 KB

Logger error indication the 900 bytes
image

2

Hello,

I saw this before, but I think this has been solved with some hardware upgrade.
The mentioned information (IP,Hostname, etc.) should not be an issue. Using the mechanism at some projects I can not confirm your observations.

Please contact you local support to clarify.
BR Fabian

3

In stead of CfgSetHostName() you could also use CfgSetHostNameIf(), which changes the hostname for one specific interface.
CfgSetHostName() sets the hostname for all interfaces.
These function blocks could also be used volatile.
If the interface already has a DHCP-server assigned IP-address the CfgSetEthConfigMode() must be called twice.
See following information from AS-Help:
To update the DNS without rebooting the CPU the function block CfgSetEthConfigMode can be used. By changing the configuration to cfgCONFIGMODE_MANUALLY and then changing it back to cfgCONFIGMODE_DHCPCLIENT, the new host name is propagated. Depending on the DCHP server the CPU can be reached via its new host name after a few seconds or minutes.t

4

This issue is unfortunately unfixable even if they release new HW version. A workaround is needed or a move away for AsArCfg. MpIO or ASIOMMan are possible workarounds I have not tested yet.

Feedback from B&R HQ 1

image
image638×114 4.12 KB

Feedback from B&R HQ 2

image
image638×415 10.9 KB

5

Thank you for the advice. I will try this and give feedback. Maybe CfgSetHostName() uses more REGMEM than CfgSetHostNameIf(). That would be ideal! I will keep you updated.

6

Hello,

thanks for sharing this information. I am not aware of this and tbh it does not make sense to me.
MpIO and AsIomMan can help but seem a bit to much at least with the current provided set of information.
You can check if @corne.geerts proposal works for you.

What you might think of is a recipe to store these settings in a file and on startup read the file and set the parameters accordingly (also possible volatile) since the non volatile part is handled by the recipe. With this, you can transfer the settings also to replacement CPUs with ease.

BR Fabian