@CReese
My issue is simply tone, sir. I get that you are frustrated, that was clear from your first posting. I have already said we are adding variable support (MRX/MWX only...there are issues with DLRX/DLWX) and it will be in the imminent 1.1 release, which will likely be released next week. I don't know what else I can do to make it right.
@Controls Guy
Not really, no. Boxes like MRX are high level function blocks written in C++. The 'code' that DmD writes is just an opcode and 11 parameters that the associated function block reads and interprets. The function block has no provision for a variable target address.
One major reason we eliminated variables for target addresses is because as part of compiling for the controller, DmD does some pre-processing of the address. For Modbus, that is simply to subtract 1 from the register to convert from user address to the actual on-the-wire value. Very minor. For DLRX/DLWX we translate all of the possible data types to the appropriate CCM code...removing that translation from the controller made it more efficient, but eliminated the possibility of variables. It is simple for Modbus so we are adding it.
