Looks like the DA10D doesn't support data logging. Pick a DA30D.
The basic Crimson workflow is to follow the order of the items in the lower left pane. On Communications, set up a protocol by picking the Modbus TCP/IP Master driver. A single device will be created for you called PLC1. Click on it and set up any required details for communication. You can rename it at any time if you want a different name.
Next create some crimson tags assigned to that device pointing at the addresses you want. If your tags are all of the same data type and in a contiguous block, you could make that tag an array and set the array size as needed.
Next, you can jump down to the Data Logger section, add a new Log file and populate the contents tab. If you use array tags, you can pick individual elements of the array by right clicking on the tag (in the resource pane on the right) and select "Toggle Array". If you want all of them (ie. 100 tags named Tag[0] through Tag[99], you have to toggle the array to expose them all, select them all (shift key is your friend) then drag them onto the Log Contents
Set up the log details:
Update rate 1.0 seconds
Each File Holds 86400 samples
Retain at most 200 files
That would give you a new file every day for 200 days (Crimson wont let you pick more than 200, and I always set it to the max...never have filled up a memory card even with lots of log files).
I would recommend just setting up one tag at first, then create virtual HMI page to display that tag, dump it into the unit and test it to ensure you have good communication and all the right data formatting and addressing before you finish the application. It is also a good idea to make a flag tag something like "CommsOkay" and set its data source to IsDeviceOnline(PLC1). This tag will give you a "1" when comms are good and a "0" when comms are not good. With modbus, this function is dependent on the Ping Holding Register set up for the device on the Communications settings.
Stick that tag on the virtual HMI page too. You can monitor the virtual HMI with any web browser, but Chrome works better than IE. IE sometimes messes with the pointer location...you push one button and a different one operates!