Whenever you change something in the .qdb file in the System Manager, the arrow for sending data to the controller will turn red. This means that you need to send the changes to the controller. If you forget this, when you close the System Manager you will receive a message that you have not sent all the changes to the controller. You can then submit the changes or ignore the changes made.
Remark: After adding modules or programming changes, ALWAYS send the information to the controller so that any changes or additions are actually implemented.
Once the components and I/O’s have been entered, you must also send all data to the controller, otherwise no test can be performed for the I/O’s.
Always make sure that you are connected to the CTD via the Ethernet or USB port when sending data to the controller.
When you click the upload arrow, the following screen appears.
Select "All data" whenever you want to send a completely new .qdb file to the controller (e.g. when you first configure your system or when you want to send a new .qdb file to a new SD bank). After that first time, it is possible to only send “All unsent changes” after you have changed settings in your program.
With a CTD10 or CTD40 it is not possible to send data if you want to configure more modules than allowed. Following message will appear:
Expanding the CTD10 and CTD40 were explained in this link
Sending and verifying data takes place in various phases: When you click on “More detail” you can follow these steps nicely.
A first step is synchronizing the clock of the CTD with the time of the PC.
As mentioned above, you can send up to 10 configurations to different SD banks (e.g.a winter program, a summer program, a holiday program, an "early shift" program, a "late shift" program, etc.). Before pressing the "Send" button, make sure you choose the correct SD bank from the drop-down list in the window above.
After clicking the "Send" button, the data will be sent to the controller, together with the module data it will be saved to the selected SD bank and then all modules will be programmed.
If you receive error messages, this may mean that a module was not found: possibly because the concerned module is not correctly connected to the bus or the serial number has been entered incorrectly. Try using Utilities/Communication Test to see if that module is communicating perfectly. If it still gives an error, check the connection between the module and the bus.