Your comments

The Activating object group of the MEM must first be evaluated to False. If it evaluates to True the first cycle, it won't see a change from False to True. 

Using an IDC that becomes true the second cycle as the condition for the MEM activating group is one way to solve it. 

Another method is to use Qreplace. 

Here is a small example to illustrate this, it doesn't do anything useful: MEM at startup.idsx

For anyone else reading this post, the problem with the Axis P7214 encoder is solved in version 5.06

In a MEM channel using object list, the value is updated when the activating object group changes from False to True. 

If you use Qcode on the MEM channel, you can get it to react on level instead. Qreplace and the other functions are all acting on level. 

The settings memory is stored in a non-volatile memory, all IQAN masters are designed to keep settings when the module is off. 

What master module was this on? 

For a general overview of what would clear settings, see the section "Settings kept during software update" in the Adjust groups chapter in the IQANdesign user manual. 

The module cannot generate every frequency, it is limited to a fixed set of frequencies. 

When typing in 120 Hz as PWM frequency on an MC4x, the expected result is not actually 120 Hz, you should be seeing it clamped to 125 Hz. 

If you were to type in 126 Hz, then the resulting frequency would be 166 Hz. 

If the J1939 or generic CAN module is connected only to one of the applications in a multi master system, it is possible to select a channel  from that same application as Enable. 

But if the J1939 or generic CAN module is connected to more than one application (has channels from more than one application) the enable property cannot be controlled by a channel. 

The problem is that only the application containing the channel used for enable has access to it, but when multiple applications have channels on this module, all of them needs to look at the Enable property. 

For a channel to enable the GT, that channel just needs to be located on the headmaster (master with address 0 controls the gateway).

There is no method for automatically creating a message that duplicates what is being written to the system log or an event log. 

If the purpose is to send information to be able to log remotely, then using a GT module and adding telematics with on-trigger signal collection could be a way. 

Another more general method is to use the DM1 out. Any channel that gets placed in the DM1 out will be send when its status is changed from OK to a warning or error. You'd just need to define SPN numbers for these, the FMI is automatic based on channel status. 

This will work, as long as it is only a J1939 or a Generic bus you connect. 

Make sure to keep the Diagnostics buses separate. 

If you were to connect the Diagnostics buses of two masters of the same type with the same IdTag, IQANdesign and IQANrun will give you an error message about Duplicate module address found

The properties of the GPIN/GPOUT has looked like this since the introduction in IQANdesign 3.00 in 2012

Before this, in versions 1 and 2, there was one set of channel types, PIN and POUT, used for both J1939 and Generic. The properties of that channel were identical to those of the JPIN/JPOUT (when old applications were updated it was automatically converted to JPIN/JPOUT). 

With GPIN/GPOUT supporting signed values it seemed strange to also have a separate offset property to deal with the sign. 

But resolution still makes sense when the value type is integer or unsigned integer.