It appears that Kep Direct doesn't support the Do More PLC. What OPC server is typically used with the Do More?
We recommend using Modbus (either Modbus/TCP or Modbus/RTU) - this would access the Modbus Server/Slave memory areas in a Do-more (i.e. NOT X/Y/C/V, but MI (Modbus (Discrete) Input), MC (Modbus Coil), MIR (Modbus Image Register), MHR (Modbus Holding Register)).
So, from a Modbus Master, you would want a field tied to reading Modbus Holding Register 40001. The 4 is more of a "type", and 1 is the "offset". So from Kep Direct's Modbus driver, Holding Register 40001 would access Do-more register MHR1 (not MHR40001), so write your Do-more PLC ladder logic to put the value for 40001 into MHR1. If Kep Direct was reading Modbus Input Register 30001, it would address MIR1 (not MHR1) register in Do-more.
If you are familiar with the DirectLOGIC (DL) K-Sequence driver for KepDirect, you could use THAT driver (either Serial or Ethernet). This DL implementation also uses similar "guest protocol" memory for reading X/Y/C/V, in that they will NOT access directly the Do-more X/Y/C/V data-blocks (for one, DL is OCTAL, Do-more X/Y/C/V are DECIMAL). Use the DLX, DLY, DLC, and DLV data-blocks in Do-more (these are similar to the MI, MC, MHR, MIR for Modbus mentioned above). So, in your Kep Server, if you wanted to read X10 (yes, octal 10), you would be reading DLX10 in a Do-more. If you wrote to a K-Sequence tag tied to V2000, you would be writing to DLV2000 in the Do-more.
Unless you really like K-Sequence and octal, I recommend sticking with Modbus.