RFSG Attribute Values are named different in gRPC than documented

[yardov]

It causes confusion that many of the parameters are named different in gRPC than what's currently documented. This is not unique to RFSG but it seems to have many of them different. Here is an example: https://github.com/ni/grpc-device/wiki/NI-RFSG-Generation-Configuration#nirfsg_exportsignal The input signal has the following differences in C and gRPC: C vs gRPC NIRFSG_VAL_START_TRIGGER vs ROUTED_SIGNAL_START_TRIGGER NIRFSG_VAL_SCRIPT_TRIGGER vs ROUTED_SIGNAL_SCRIPT_TRIGGER NIRFSG_VAL_MARKER_EVENT vs ROUTED_SIGNAL_MARKER_EVENT etc

This is the same for the input signalIdentifier and outputTerminal which were a lot harder to figure out the mapping and many of them are valid values but incorrect mapping. TIP: Use IO Trace to see if you programmed what you intended.

This is a MUST to fix for any gRPC adoption.

AB#2147304