Howdy Fvalenzu,
Firstly, I would always recommend using the latest (stable) driver release for whatever hardware you're using.
Also, could you give some more detail about the "communication errors" -- error numbers would be great, or if there aren't any, then the exact message that gets displayed.
I also have a few ideas we could try:
If you dont mind reworking the LabVIEW code you've already got, the following could give you some insight into how you need to configure labview to work with your hardware.
Also, if you go into MAX and configure a task (or Global Channel) that you know talks to your hardware the right way by right-clicking Data Neighborhood and selecting Create New. You can then go into labview, create a DAQmx Task (or Channel) Constant onto your block diagram, select your task/channel from the drop-down list of that constant, then right-click the constant and select Generate Code>>Configuration and Example to create some LabVIEW code that creates essentially the exact same setup that MAX has. You can then double click the sub-vi that gets created and compare the configuration code in there to whatever configuration code you're using.
My other idea at the moment has to do with the "calibration format" complaint you got from your device when you copied the old calibration files. Without more detail, my guess would be that some setting inside those files was supported by model "A" and not supported by the upgraded model "D". There may be a new way of setting up that configuration or it may be a feature that's no longer supported, I don't know since it's not an NI product. But all of your troubles may be solveable by playing with those calibration files and making them stop throwing errors when you load them into the hardware.
