C1000
The name provided was not found:
1) Check your spelling, check for typos.
2) If you are not specifying the connection, make sure the default connection is correct.
C1001
The channel name provided was not found:
1) Check your spelling, check for typos.
2) If you are not specifying the connection, make sure the default connection is correct.
C1002
The name provided was not found:
Check your spelling, check for typos.
C1004
An error occurred while trying to set the value. This is a general catch all error for something unexpected and may be due to hardware failure or system instability. You should probably save your work just in case and proceed with caution.
C1005
The variable name specified was not found and the data cannot be retrieved. Check your spelling, check for typos. Is the variable declared?
More info on variables is in section 5.10.
C1006
A conversion was specified for a channel that does not exist. Most likely, the conversion was deleted without updating the channels to which it applied. Check your channels for deleted conversions. More info on Conversions is in section 6.11.
C1007
A problem occurred trying to connect to your email server. The error varies and is provided at the end of the message. Check your email server setting, and your internet connection. Also make sure your username and password are correct and that you've selected the correct authentication method. More info on receiving emails is in section 12.4.
C1008
A problem occurred trying to send the email message. The response from the server is provided. The action to fix this error depends on the response, but typically is either related to the settings (username / password / authentication method) or a problem with the server. More info on sending emails is in section 12.3.
C1009
Most of the System. functions that display windows can only be called from the main application thread. The main application thread is the thread that the DAQFactory user interface runs in. Sequences started with Begin Sequence run in their own thread and cannot open any windows. Events for channels and PID loops also usually run in their own threads and cannot open windows. The only reliable place to call the System. functions that open windows is from a component event, especially the OnLButtonDown. More info on system functions is in section 5.27.
C1010
There was a problem trying to open the data source for ODBC data logging. The most common mistake is to provide the file name of your database for the data source and not the ODBC data source name defined in the Windows ODBC manager. More info on ODBC data logging starts in section 9.4.
C1011
A problem occurred trying to create the table for data logging in your ODBC database. The possible causes are database specific. The most common is that the database is opened exclusive in another application and DAQFactory cannot open it for modification.
C1012
A problem occurred trying to access the table for data logging in your ODBC database. The possible causes are database specific. The most common is that the database is opened exclusive in another application and DAQFactory cannot open it for modification.
C1013
An error occurred while trying to log. The exact error message is also provided. Common problems include trying to log to a file that is open exclusively in another application, logging to a ODBC table that already exists with the wrong field names, or the disk being full.
C1014
An error occurred trying to start up the thread used for the PID loop. This is usually caused by lack of memory or resources and is a good sign that you are overdriving your system. Try running DAQFactory with fewer other applications running.
C1015
Most of the System. variables that affect the display of windows can only be called from the main application thread. The main application thread is the thread that the DAQFactory user interface runs in. Sequences started with Begin Sequence run in their own thread and cannot open any windows. Events for channels and PID loops also usually run in their own threads and cannot open windows. The only reliable place to call the System. variables that affect the display of windows is from the Quick Sequence action of a component. More info on system functions is in section 5.27.
C1016
The System.MessageBox function requires one of the following types: “Help”, “AbortRetryIgnore”, “OKCancel”, “RetryCancel”,”YesNo”, or “YesNoCancel” These types are case sensitive. More info on System.Message box is in section 5.27.
C1017
There was insufficient resources to display the message box. Try running DAQFactory with fewer other applications running.
C1018
Must be either NoLogin, AuthLogin, or LoginPlain. The specified authentication type for the email server must be one of the three options listed. More info on email starts in section 12.3.
C1019
An internal error occurred that was caught by DAQFactory. Unfortunately, what the error was cannot be determined, but it must be something rare or another message would be displayed. You should save your work under a different file name just in case the file is corrupted and restart DAQFactory.
C1020
Alarm logging will not occur. There was a problem trying to open the data source for ODBC alarm logging. The most common mistake is to provide the file name of your database for the data source and not the ODBC data source name defined in the Windows ODBC manager. More info on ODBC logging starts in section 9.4.
C1021
A problem occurred trying to create the table for alarm logging in your ODBC database. The possible causes are database specific. The most common is that the database is opened exclusive in another application and DAQFactory cannot open it for modification.
C1022
A problem occurred trying to access the table for alarm logging in your ODBC database. The possible causes are database specific. The most common is that the database is opened exclusive in another application and DAQFactory cannot open it for modification.
C1023
An error occurred while trying to open the alarm log file. The exact error message is also provided. Common problems include trying to log to a file that is open exclusively in another application, logging to a ODBC table that already exists with the wrong field names, or the disk being full.
C1024
This is a generic error that occurs when DAQFactory is unable to broadcast a command over the network. This can be caused by network failure or by internal errors. If the message persists, check you network connection, then save and restart DAQFactory.
C1025
An error occurred in the thread that sends commands over the network. The thread will be restarted but this may fail. If you find that commands are not being received remotely, you should restart DAQFactory. You may want to consider restarting anywhere.
C1026
(does not affect proper running of DAQFactory, but may indicate a further problem)
The heartbeat thread simply sends a small packet over the network so remote copies of DAQFactory can tell that the connection is still established. There was an error in the thread that runs the heartbeat and the heartbeat had to be stopped. Remote copies of DAQFactory will probably still receive data. This probably won't affect anything, but may be an indication of other problems, such as lack of memory, resources, or network problems.
C1027
The was a problem averaging channel data. Most likely this comes from an invalid data point, such as infinity that can't be averaged. Your data at this point in time is invalid. You should check you device and make sure it is working properly.
C1028
The license you have purchased only supports a single device driver at a time. Check your channel table and make sure the Device Type column lists only one device for all your channels.
C1029
The license you have purchased does not support the particular channel parameters you specified. Check your channel table.
C1030
There was a problem with a particular device driver file. Try downloading the latest version of the device driver and reinstalling.
C1031
The license you purchased only supports certain devices. At least one of your channels specifies a device that is not supported. Check your channel table and any sequences that may reference devices.
C1032
Device drivers are made up of two files, one with a .dll extension and one with a .dds. DAQFactory generates this error if you have different versions of these two files. This usually does not cause any problems, but if you find expected features missing you should download and install the device driver again.
C1033
This occurs in one of three situations:
1) You loaded a document from another computer that references devices that are not installed on this system.
2) The .dds file for the device driver exists, but the .dll file is missing.
3) Dependency .dll files are missing. This usually occurs when you install the DAQFactory device driver but have forgotten to install the manufacturers drivers. DAQFactory relies on these drivers and therefore requires them. We cannot distribute them with DAQFactory because of copyright issues as well as for version control.
C1034
With any out of memory error, you should try running DAQFactory with less applications running. You can also try lowering the resolution and/or color depth of your screen and restarting DAQFactory. Shortening your channel's history lengths will also free up memory.
C1035
Sequences typically run in their own thread. For some reason DAQFactory was unable to start a thread for a sequence. This is typically caused by lack of memory or resources. Try running DAQFactory with fewer other applications running. You can also try lowering the resolution and/or color depth of your screen and restarting DAQFactory. Shortening your channel's history lengths will also free up memory.
C1036
This is a generic catch-all error for any error that may occur in a sequence that does not have its own error. This is most likely caused by problems with the device or device driver, but could be caused by lack of memory or resources.
C1037
Please save work under a different name and restart DAQFactory.
If this error occurs, something very unusual occurred and rather than crashing, DAQFactory has caught the error and generated this message. You should save your work under a different name just in case there is file corruption and restart DAQFactory. Rebooting probably is not a bad idea either.
C1038
If you specify Timing parameters for your channels that are too small and your computer cannot keep up, DAQFactory will detect the backlog and reset. If this just occurs once, then there was probably just a temporary increase in CPU usage caused by starting another application or something similar. In this case you are near the limit, but not over it. If this recurs at a relatively constant interval then the device you are communicating with cannot maintain the data rate specified. For example, the LabJack U12 takes about 16ms to acquire a data point. If you specify a timing interval of 0.01 for a LabJack channel, you will receive this error every 10 seconds or so. You should adjust your Timing values accordingly.
C1039
An unknown error occurred while trying to access and subset channel data. Check your subsetting.
C1040
The channel that you have requested data from does not have any values yet. This typically occurs in sequences that start when the document loads and reference input channels. The sequence starts before data has been acquired on the referenced channels and the sequence throws this error. To fix this, try adding a little delay to the beginning of the sequence to ensure acquisition has time to start, or use the IsEmpty() function to check for valid data before actually trying to use it.
C1041
If this error occurs while loading a new document, or starting a new document then things may simply not have shut down properly. You may want to restart just in case, but this is probably not required. If this error occurs during normal operation of your document, then there is a memory issue with your system. Unfortunately your document is probably corrupted and you will have to revert to a saved document when you restart. This is an indication of a fundamental operating system problem.
C1042
Some sort of uncaught error occurred while trying to compile your sequence. This is probably an uncaught problem with the compiler. You should email support@azeotech.com with a copy of the sequence you were trying to compile and we will determine the problem rapidly.
C1043
In your sequence an extra endwhile was found without a matching while() statement.
C1044
In your sequence a while() was found without a matching endwhile.
C1045
In your sequence an extra endfor was found without a matching for()
C1046
In your sequence, a for() statement was found without a matching endfor
C1047
In your sequence, an endif was found without a matching if() statement.
C1048
In your sequence, an if() statement was found without a matching endif.
C1049
In switch / case constructs, you must list all your case statements first before listing the default.
C1050
In the switch construct, you can have many case statements, but you can only have one default statement.
C1051
An endcase statement was found without a matching switch statement.
C1052
In your sequence, a switch statement was found without a matching endcase.
C1053
In your sequence, an endcatch statement was found without a matching catch statement.
C1054
In your sequence a catch statement was found without a matching endcatch.
C1055
There was a problem with the formatting of a line in your sequence.
C1056
A statement or function was found without the expected open parenthesis. Function()
C1057
A comment ("//") was found in the middle of a parenthesis, subset, or array notation.
C1058
An open parenthesis was found without the matching close parenthesis.
C1059
An open quote was found without the matching close quotes.
C1060
Most statements require a certain number of paremeters.
C1061
An open bracket was found without the matching close bracket.
C1062
This error occurs when a line in a sequence starts with something other than a letter. All statements start with a letter as do all channels and functions, so with the exception of a comment, all sequence lines must start with a letter.
C1063
An expression was found after a function call.
C1064
An expression was found after the decrement operator: For example: MyChannel-- + 3 is invalid
C1065
An expression was found after the increment operator: For example: MyChannel++ * 3 is invalid
C1066
An operator was specified that doesn't exist. For example MyChannel ^* 3
C1067
The expression parser was called with an empty expression. An empty expression is valid in many places, but not in all places.
C1068
'Value' can only be used in conversion or graph trace expressions. The term Value is a special term that is used in conversion where a channel should be substituted, or in graph trace expressions where the X value should be substituted. This error occurs when you try an use this term in other expressions.
C1069
You tried to subset an array with no values in it.
C1070
Some operators require one parameter, for example: MyChannel++. Others require two, for example: MyChannel + 3. This error occurs when the second parameter is missing: MyChannel + This can also occur with internal functions.
C1071
The given function was provided more parameters than it needs.
C1072
This occurs when the number of open { do not match the number of close }.
C1073
Example: MyChannel[3+(2*3))]
C1074
For example: MyChannel[3,5}]
C1075
For example: MyChannel[3+(2*5]
C1076
Example: MyChannel[3,{3,2]
C1077
Example: Sin(MyChannel[0]])
C1078
For example: Sin({2,5}})
C1079
For example: Sin(MyChannel[0)
C1080
For example: Sin({2,5)
C1081
For example: Var.x = MyChannel[3]]
C1082
For example: Var.x = 3 + (2 * 3))
C1085
For example: Var.x = MyFunction + 2 * 3
C1086
The proper number of parameters was provided, but one of the parameters had an empty value.
C1087
In older releases of DAQFactory you could subset relative to the current time by specifying negative subset values. This feature has been removed. Instead, use SysTime()-x. So before if you had MyChannel[-2,-5], replace this with MyChannel[SysTime()-2,SysTime()-5]
C1088
There was an error while performing a mathematical function.
C1089
An error occurred that does not fit into any other category. Check the syntax.
C1090
The ShiftTime() function requires an array that has time values to shift.
C1091
The FormatDateTime() function requires a numeric date/time in seconds since 1970 which is the DAQFactory standard way to store time.
C1092
You used the Remove() function on a string with nothing in it and therefore nothing to remove.
C1093
You cannot search an empty string.
C1094
Fill(Value, Array Size). The second parameter, which determines how many elements to create must be greater than 0.
C1095
For example you cannot Concat() an array with 5 rows and 10 columns to an array with 7 rows and 12 columns. The Concat() function combines arrays along the rows dimension. The total rows in each row can be different, but the column and depth count must be the same.
C1096
A generic error occurred while trying to calculate the temperature. Most likely an invalid voltage or CJC was provided.
C1097
Many functions require numbers. Most will take a string operator and convert it to a number if necessary. Other will generate this error instead.
C1098
This occurs when DAQFactory has an array with a different size from its reported size. If this persists, contact tech support with the actions taken.
C1099
The given operator or function does not exist.
C1100
AscA requires a valid string.
C1101
ChrA() requires an array of values
C1102
SortTime() sorts an array based on the time of each data point. This requires an array with time values.
C1103
The boxcar functions only work on numeric values. More info on Boxcar functions is in section 4.12.8.
C1104
The boxcar functions only work on single dimensional arrays, or an array with multiple rows, but only one column and one depth. Use subsetting and the Transpose() function to boxcar other dimensions. More info on Boxcar functions is in section 4.12.8.
C1105
More info on Boxcar functions is in section 4.12.8.
C1106
This is an internal error. BoxcarMinMax is a function used to optimize graphing and should only be called when values have time associated.
C1107
More info on Smooth() function is in section 4.12.8.
C1108
The Smooth() function only works on single dimensional arrays, or an array with multiple rows, but only one column and one depth. Use subsetting and the Transpose() function to Smooth other dimensions. More info on Smooth() function is in section 4.12.8.
C1109
More info on Smooth() function is in section 4.12.8.
C1110
More info on Histogram() function is in section 4.12.17.
C1111
More info on Histogram() function is in section 4.12.17.
C1112
GetTime() returns an array with the time associated with a value.
C1118
By the vary nature of the binary logging format, you cannot use it to log string data. You should use ASCII or ODBC database to log string data instead. More info on data logging is in section 9.2.
C1119
In Safe Mode, no acquisition, PID loops, logging or sequences will start. You must leave safe mode (File-Leave Safe Mode) before you can start any sequences, PID loops, or logging sets.
C1120
Logging will still continue.
There was an error trying to create the logging header file. This is most likely because the file is read-only, is open in another application, or the disk is full. More info on data logging is in section 9.2.
C1121
There was a generic error while performing the File.Move() function. More than likely the destination already exists, or the source file does not exist. More info on low level data logging is in section 9.9.
C1122
A generic error occurred while trying to do a File.Copy() function. More than likely, the source file does not exist. More info on low level data logging is in section 9.9.
C1123
There was a generic error trying to retrieve the disk space. Most likely you tried to retrieve the disk space on a removable disk that has been removed. More info on low level data logging is in section 9.9.
C1124
More than likely the directory still has files in it. More info on low level data logging is in section 9.9.
C1125
More than likely, the directory already exists. More info on low level data logging is in section 9.9.
C1126
The logarithm of a value <= 0 does not exist and therefore is invalid.
