The table below is a complete list of NLP error codes, what they mean, and how to resolve.
Click here for a simplified list of the most common NLP error codes.
Click here for a list of NG Error Detail codes. NG decoders give these Error Details to provide additional context behind the standard "3000" Station Error.
Error Code | Decoder Types | Description | Possible causes | What to do? |
---|---|---|---|---|
400 | Bad Request | The interface/controller cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). | Try again. If problem persists, contact Tucor NLP support. | |
401 | Unauthorized | Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. | Try again. If problem persists, contact Tucor NLP support. | |
403 | Forbidden | The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). | Try again. If problem persists, contact Tucor NLP support. | |
404 | Unknown Request | The requested resource could not be found. | Try again. If problem persists, contact Tucor NLP support. | |
408 | Request Timeout | The interface/controller timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time." | Try again. If problem persists, contact Tucor NLP support. | |
500 | Server Error | A generic error message, given when an unexpected condition was encountered, and no more specific message is suitable. | Try again. If problem persists, contact Tucor NLP support. | |
1000 | ALL | 2-Wire Timeout | A command was sent on the 2-Wire, but the decoder didn’t respond. | Locate the decoder. Place controller in short finding mode & check the decoder draw current. If problem persists, check for broken cable. |
1001 | ALL | 2-Wire Communication Error | Communication with a decoder is disturbed. | Check integrity of the 2WP by checking the current draw is as-expected in short finding mode. |
1002 | ALL | 2-Wire Not Operational | A command was sent to a decoder when the 2-Wire was not operational. | Check 2-Wire status. |
1003 | ALL | 2-Wire Load Too High | Too many active decoders. Partial short of the 2-wire path. Faulty Decoder. | Turn off several decoders if too many are active. Check integrity of the 2WP. Locate the decoder. |
2000 | ALL | Object Not Found | An object doesn’t exist. It could be a station with a reference to a decoder, which has been deleted. | Check that the station, decoder, and IO are configured correctly. |
2001 | ALL | Object Exists | Trying to create a duplicate object. | Check for duplicates. |
2002 | Object Duplicate Key | Trying to create a duplicate key. | ||
2003 | Object Storage Full | Creating more objects than a certain object type accepts. | ||
2004 | Object Incomplete | Creating an object with an incomplete JSON format. | ||
2005 | Object Wrong Type | Creating an object with a wrong type. Patching an object with a wrong type. | ||
2006 | Object In Use | Deleting an object which is in use, e.g. an ioCfg which is used by a decoder. | ||
2007 | Object Active | Deleting an object which in use, e.g. a station which is running. | ||
2050 | Sub Object Not Found | Accessing a sub-object which doesn’t exist, e.g. a non-existing output index on a decoder. | ||
2051 | Sub Object Wrong Type | Creating a sub-object with a wrong type. Patching a sub-object with a wrong type. | ||
2100 | Data Parse Error | The data structure of the JSON object is incorrect. Could be because of FW version incompatibility. | ||
2101 | Data Type Error | Wrong data type is used, e.g. mismatch of strings and numbers. | ||
2102 | Data Constraint Error | Data outside range or invalid. | ||
2103 | Data Field Not Found | JSON object has wrong data fields. | ||
3000 | RK & LD | Line unit (decoder) failure detected | The verification of a command indicates an error. | Try again. If problem persists, check decoder and 2WP connections. |
NG | Line unit (decoder) error | The verification of a command indicates an error. The error is followed by additional information. | See NG Error Detail table. If problem persists, check decoder and 2WP connections. | |
3001 | ALL | Line unit (decoder) non acknowledge | The command to a decoder was not accepted. E.g. an ON command to an output decoder already ON. | Try again. Perform the opposite action & try again. Disable ‘verify’ and/or enable ‘force’. |
4000 | File Deletion Failed | Deletion of file during FW upgrade | Perform a Factory Reset. | |
4001 | File Write Error | File write error during FW upgrade | Perform a Factory Reset. | |
5000 | ALL | IO Config Not Found | An IO config doesn’t exist. It could be a decoder with a reference to an IO config, which has been deleted or changed. | Check that the IO config exists. Try reapplying the IO config to the decoder. |
5001 | Flow Capacity Too Low | A part of the hydraulic system has too low capacity compared to the expected flow requested by a station start. | Check station flow rate, pipe capacity, and flow sensor config. | |
6001 | ALL | Value Too Big | The diagnostic value was not measured in the decoder. Could be due to issues activating a solenoid. | Check solenoid & decoder. If problem persists, replace solenoid and/or decoder. |
7000 | Value Not Measured | Didn’t manage to find a stable flow within the stable count and stable max minutes. | Check flow rule config. Try later when flow is more stable. | |
7001 | Flow Learn Timeout | Didn’t manage to find a stable flow within the stable count and stable max minutes. | Check flow rule config. Try later when flow is more stable. | |
7002 | Flow too low | Flow is less than expected minus “Max low deviation (%)” after the start delay and change delay respectively. | Check station flow rate, pipe capacity, and flow config. Check for clogs. | |
7003 | Flow too high | Flow is more than expected plus “Max high deviation (%)” after the start delay and change delay respectively. | Check station flow rate, pipe capacity, and flow config. Check for leaks. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article