New HIDS Drum Scales!
Click Here to Learn More!The sample programs that are available on our web site are just examples of running various commands. Each routine in the program is for a different command. You may or may not need to run these commands, depending on your application. The end-user is responsible for writing the PLC code for their specific application. We only offer these sample codes to our customers as a guide to the programming necessary for running each of the different commands. The end-user is responsible for their programming. Many end-users hire a System Integrator to perform this programming.
We offer samples as samples and are not responsible for ensuring the code would work for the users application.
At the very minimum, you should have the ability in your program to:
1. Write the parameters.
2. Do a calibration on the module. This may be a C2® cal or a hard cal. The hard cal uses both the cal low command and the cal high command.
3. The save (write to non-volatile).
To operate the various commands in the samples, you would latch on the bit in the Main Routine to enable the subroutine you are trying to run. This will enable the subroutine and let it run through. The subroutine is designed to turn off the starting bit once completed.
If there is any other data required for the particular command being run, it would be the users' responsibility to have that data entered prior to starting the command. The comments for each of the routines describes the command and any required data or special handling for the command to run. They also describe all aspects of the command including any return data and the locations to find such.
Sometimes, it is possible the user can copy the sample code and paste it into their program without any issues. The copied code may need modification to account for the modules being in different slots or addresses, as well as possible changes in data locations or tags used. The user would be responsible for making any modifications if they choose to copy the code.
