Neutron Modbus RTU/TCP — integration manual
Neutron Modbus RTU/TCP reference for PLC, SCADA and HMI integration: connection, addressing, registers, calibration and automatic checkweigher control.
NEUTRON · COMMUNICATION PROTOCOL
CSCP command reference for Neutron: message structure, weighing, configuration, counting, checkweighing and digital I/O.

Commands for CSCP are composed of ASCII characters. Commands are composed of parameters and values.
| Symbol represent space. |
|---|---|
| Triangle brackets indicate that this is mandatory command parameter. |
| Square brackets indicate that this is optional parameter and can be omitted. |
| Each command sent must have string terminator CR – carriage return (ASCII 13) and LF – line feed (ASCII 10). |
| Data sent to scale. |
| Data received from scale. |
Please note that commands and parameters value are case sensitive.
General command structure:
Command | | | | |
|---|---|---|---|---|
1-n characters | — | 0-n characters | — | — |
Examples:
Command without parameters:
| | Request stable weight. |
|---|---|---|
| | Scale response with stable weight of 100 g |
Command with parameters:
| | Set tare value to 100 g. |
|---|---|---|
| | Scale response with settled tare value. |
Scale always respond to command with answer which can be:
Response with weight value
Response without weight value
Error message
Note: Weight values are always returned as 10 characters with leading spaces.
General response with weight value:
Command ID | | Status | | Weight value | | Unit | | |
|---|---|---|---|---|---|---|---|---|
1-n characters | — | 1 character | — | 10 characters | — | 1-n characters | — | — |
Example:
| | Request stable weight. |
|---|---|---|
| | Scale response with stable weight of 100 g |
General response without weight value:
Command ID | | Status | | Parameters | | |
|---|---|---|---|---|---|---|
1-n characters | — | 1 character | — | 0-n characters | — | — |
Example:
| | Request scale serial number. |
|---|---|---|
| I4 A "ABC2KL" | Scale response with serial number in "" |
In general error message has the following structure:
Command ID | | Status | | |
|---|---|---|---|---|
1-n characters | — | 1 character | — | — |
Status | Description |
|---|---|
| Scale gross value or parameter value exceed scale maximum range (scale maximum + 9 divisions). |
| Scale gross value or parameter value is under scale zero range (more than 20 divisions in minus). |
| Internal error – scale executing another command, command timeout etc. |
| Logical error – for example tare value exceed scale maximum. |
Example:
| | Request stable weight. |
|---|---|---|
| | Scale did not stabilise in defined timeout window (default 5 seconds). |
| | Request weight immediately. |
| | Scale gross value exceed scale maximum. |
In case you send to scale non-existing command to scale you will receive ES response.
| | Non-existing command |
|---|---|---|
| | Syntax error or non-existing command received. |
In this chapter you will find detailed description of each command together with examples.
Command | Description |
|---|---|
| Terminates current command execution |
| Get current ADC points |
| Cancel all commands |
| Calibrate point. |
| Clear counter value |
| Get tolerance status and weighing data in check weighing mode |
| Write text to display |
| Delete calibration point. |
| Get counter input value |
| Switch to weight |
| Status of error and description if any |
| Enabled/disable high resolution filter |
| Set filter value |
| Get calibration data. |
| List of implemented commands |
| Level information and versions |
| Scale model and capacity |
| Hardware and software version |
| Serial number |
| Firmware checksum |
| Initialize scale |
| Initialize digital inputs and outputs |
| Get list of available applications |
| Get or set application |
| Get number of pieces |
| Get number of pieces and weighing data |
| Set target and tolerance in counting application |
| Get target and tolerances |
| Set target and tolerances in check weighing mode |
| Query all scale information |
| Read scale data – get all parameters |
| Calculate average piece weight |
| Reset scale |
| Get stable weight |
| Get weight immediately regardless of stability |
| Set counter input value |
| Get or set input configuration parameters |
| Get input status |
| Start continuous transmission of net weight regardless of stability status |
| Get current stable gross, net and tare |
| Get current gross, net and tare value immediately |
| Get current gross, net and tare value immediately and repeat (continuous transmission) |
| Get all weighing data stability, gross, net, tare, range etc. with one command |
| Get or set current scale (channel) |
| Get or set output function |
| Get or set output state |
| Set scale data - parameters |
| Tare the scale |
| Query or set preset tare value |
| Clear tare weight value |
| Tare scale immediately regardless of stability |
| Zero the scale |
| Zero the scale immediately regardless of stability status |
Command | |
|---|---|
| Command cancel current command on scale. |
Responses | |
| Cancelling current command execution has been started. |
Command | |
|---|---|
| Request for current ADC value. |
Responses | |
| Current ADC value is 866585 |
Command | |
|---|---|
| Command cancel current command on scale. |
Responses | |
| Cancelling current command execution has been started. |
Command | |
|---|---|
| Display Text on the scale display. |
Responses | |
| Command executed successfully. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
| Command received but not executable (syntax error or scale without display). |
Command | |
|---|---|
| Switch main display to show weight. |
Responses | |
| Command executed successfully. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Command | |
|---|---|
| Query current scale state. |
Responses | |
| Current error code and description. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Error code | Description |
|---|---|
| No error |
| No calibration. |
| No metrological data (max1 and d1 are not set). |
| ADC error (no load cell, sense error, etc.). |
| Sense error – reference lines error detected (not connected, short cut, etc.). |
Command | |
|---|---|
| Query all available commands. |
Responses | |
| List of all available commands in format |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Parameters | Description |
|---|---|
| 0 – basic commands without parameters |
| CSCP command |
Command | |
|---|---|
| Query of CSCP levels. |
Responses | |
| Available levels and corresponding versions. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Examples of responses | |
| Level 0-2 are implemented and corresponding versions are provided. |
Parameters | Description |
|---|---|
| 0 – basic commands without parameters |
| CSCP corresponding versions. |
Command | |
|---|---|
| Query of model name and capacity. |
Responses | |
| Device mode, capacity and unit returned. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Examples of responses | |
| Model name CS-NEUTRON, capacity 1000 g. |
Command | |
|---|---|
| Query hardware and software versions. |
Responses | |
| Hardware versions represent PCB version. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Examples of responses | |
| Hardware version 1, Firmware 1.0.0., CSCP version 1.0.0. |
Command | |
|---|---|
| Query scale serial number. |
Responses | |
| Serial number of scale. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Examples of responses | |
| Response with the device serial number. |
Command | |
|---|---|
| Query firmware check sum. |
Responses | |
| Firmware checksum. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
Examples of responses | |
I5 A "357940E…F723" | Firmware checksum is 357940E…F723 |
This command will execute scale taring as soon as next stable weight is detected.
Command | |
|---|---|
| Set current gross as tare value when weight is stable. |
Responses | |
| Tare executed successfully. Command returns tare value. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command, or timeout occurred as scale did not reach stability in specified command window). |
| Tare value exceeds the maximum capacity. |
| Tare value is less thane 0. |
Examples of responses | |
| Scale response with stable tare value 100 g |
This command will get currently set tare value or set tare value.
Command | ||
|---|---|---|
| Query current tare value. | |
| Preset tare value. | |
Responses | ||
| Tare executed successfully with stable scale. | |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command, or timeout occurred as scale did not reach stability in specified command window). | |
| Command received but not executable (syntax error or tare value over max or less than 0, wrong unit etc.) | |
Examples | ||
| | Query current tare value |
| | Current tare value is 100 g |
| | Set tare value to 150.11 g |
| | Response from scale that tare value is set to 150.11 g |
Note:
Tare value will be automatically rounded to range division. For instance, if scale has division of 0.5 g and you send TA˽A˽˽˽˽˽150.11˽g it will set 150 g as tare value which will be given in response. If you send TA˽A˽˽˽˽˽150.75˽g it will set 151 g.
This command will delete current tare value regardless of tare type.
Command | |
|---|---|
| Clear tare value |
Responses | |
| Tare value has been cleared (set to 0). |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command). |
This command will execute scale taring regardless of scale stability.
Command | |
|---|---|
| Set current gross as tare value regardless of stability. |
Responses | |
| Tare executed successfully with stable scale. |
| Tare executed successfully with unstable scale. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command, or timeout occurred as scale did not reach stability in specified command window). |
| Tare value exceeds the maximum capacity. |
| Tare value is less thane 0. |
Examples of responses | |
| Scale response with stable tare value 100 g |
Returns the current net weight only when the scale is stable.
If the scale is not stable when the command is received, the scale waits until stability is achieved or until the command timeout expires.
If stability is not reached within the configured command timeout window, a timeout error is returned.
Command | |
|---|---|
| Returns the net weight only when stable; waits for stability up to the command timeout. |
Responses | |
| Scale responded with stable net weight value. |
| Command received but cannot be executed at this time or timeout occurred (the scale is busy processing another task or command, or timeout occurred as scale did not reach stability in specified command window). |
| Scale is overloaded (weight exceeds the maximum capacity). |
| Scale is underloaded (weight is below the minimum measurable range). |
Examples of responses | |
| Scale response with stable net weight 100 g |
SI command returns the current net weight immediately, without waiting for scale stability.
The response reflects the scale status at the moment the command is processed.
Command | |
|---|---|
| Commands returns current net weight regardless of scale stability status. This means that weight is returned immediately. |
Responses | |
| Scale responded with stable net weight value. |
| Scale responded with unstable net weight value. |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). |
| Scale is overloaded (weight exceeds the maximum capacity). |
| Scale is underloaded (weight is below the minimum measurable range). |
Examples of responses | |
| Scale response with stable net weight 100 g |
SIR command returns the current net weight immediately, without waiting for scale stability. As soon as next weight is processed scale sends new weighing data.
Command | ||
|---|---|---|
| Command to start continuous transmission of stability indicator and net weight. | |
Responses | ||
| Scale data with stable net weight value. | |
| Scale data with unstable net weight value. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Scale is overloaded (weight exceeds the maximum capacity). | |
| Scale is underloaded (weight is below the minimum measurable range). | |
Example of continuous transmission | ||
| | |
| | |
| | |
| | |
| | |
| | |
Note:
To cancel continuous transmission send command @, C, SI, S.
SIX1 command returns the all current weighing data such as stability, tare type, gross weight, net weight, tare value immediately, without waiting for scale stability.
Command | ||
|---|---|---|
| Query all current scale data | |
Responses | ||
| Scale data with stable net weight value. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
Example communication | ||
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
Parameters | Description |
|---|---|
| S – stable weight |
| Z – if gross +/- ¼ d |
| 1…3 range in which current gross value is |
| N – no tare |
| Gross weight |
| Net weight |
| Tare |
| Unit |
SX command returns the current weighing data - stability gross weight, net weight, tare value when weight is stable.
Command | ||
|---|---|---|
| Query current scale data | |
Responses | ||
| Scale data with stable net weight value. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Scale is overloaded (weight exceeds the maximum capacity). | |
| Scale is underloaded (weight is below the minimum measurable range). | |
Example communication | ||
| | |
| | |
| | |
| | |
SXI is simplified SIX1 command that returns the current weighing data - stability gross weight, net weight, tare value immediately, without waiting for scale stability.
Command | ||
|---|---|---|
| Query current scale data | |
Responses | ||
| Scale data with stable net weight value. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Scale is overloaded (weight exceeds the maximum capacity). | |
| Scale is underloaded (weight is below the minimum measurable range). | |
Example communication | ||
| | |
| | |
| | |
| | |
SXIR will enable continuous sending of SXI command. To disable continuous sending of SXI command send C or @ command.
Command | ||
|---|---|---|
| Query current scale data | |
Responses | ||
| Scale data with stable net weight value. | |
Example communication | ||
| | |
| | |
| | |
Command | ||
|---|---|---|
| Command to get or set active channel/scale. If scale parameter is omitted then you will receive in response current channel otherwise you will receive success status of changing active scale. | |
Responses | ||
| Current scale (channel) is 1. | |
| Scale change has been successful. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Command received but not executable (syntax error or wrong channel – it must be in range 1-4). | |
Example of continuous transmission | ||
| | |
| | |
| | |
| | |
UPD command is used to set delay between transmissions in commands like SIR, SXIR that activate continuous mode.
Note: this is the delay between sending data after they have been processed. Since data are sent to the scale communication interface this means that there will be additional delay especially if using wireless connection like WIFI or Bluetooth. Same delay is guaranteed only on CPU level and therefore data will not come always with the same delay depending on interface used. Wired interfaces tend to have more constant delay then wireless ones.
Command | ||
|---|---|---|
UPD | Get current delay between transmissions. | |
Responses | ||
| Current scale (channel) is 1. | |
Example of continuous transmission | ||
| | |
| | |
| | |
| | |
QASI1 command reads all the current scale data such as channel, range, stability, gross weight, net weight, tare value, high resolution, adc point, millivolst etc. immediately, without waiting for scale stability.
NOTE: QASI1C uses comma (,) as data separator instead of space (˽) everything else is the same.
Command | ||
|---|---|---|
| Query all scale information | |
Responses | ||
| Scale data with stable net weight value. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
Example communication | ||
| | |
| | |
| | |
| | |
Parameters | Description |
|---|---|
| 1 – no error for others see list of error codes |
| Current scale channel 1-4 |
| 1…3 range in which current gross value is |
| S – stable weight |
| Gross weight |
| Net weight |
| Tare |
| High resolution gross weigh with two additional decimals |
| Signal from load cell expressed in points |
| Signal from load cell expressed in millivolts |
| Unit |
FT command is used to get or set filter on currently active scale. If you want to set filter for different scale either switch to different scale by using SNS command or use SSD command and parameter nFT.
Command | |
|---|---|
| Query current filter value. |
Responses | |
| Response with filter value |
FC command is used to enable/disable high resolution filter on currently active scale. If you want to set filter for different scale either switch to different scale by using SNS command or use SSD command and parameter nFC.
Command | |
|---|---|
| Query current high resolution filter value. |
Responses | |
| Response with high resolution filter value. |
Command | |
|---|---|
| Reset scale. |
Responses | |
| Response confirming the restart command. |
Command RSD and SSD give you possibility to read all scale and applications parameters.
Each parameter has unique name and to which a corresponding value can be set. List of all available parameters are listed below in table with description, default value and range value.
Parameters are always in key=value pairs. For example 1D1=0.1 where 1D1 is parameter and 0.1 is it’s value. Parameters are separated with semicolon (;).
Single-channel and multi-channel operation
By default, the scale operates in single-channel mode (SAM=0). In this mode, each of the four ADC channels can be connected to a separate weighing platform. Each channel is treated as an independent scale and may have its own metrological parameters, including capacity, scale division, calibration, filter settings, zero settings, and weighing unit.
Single-channel mode should be used when:
each ADC channel is connected to a separate weighing platform;
every platform requires its own calibration and metrological settings;
only one load-cell signal is required for each scale;
compatibility with the standard acquisition and calibration procedure is required.
In multi-channel mode (SAM=1), two, three, or four ADC channels are combined into one logical scale. The number of active channels is selected with the SAC parameter. Each active channel is sampled continuously, and its individual raw ADC value and signal in millivolts can be read using the QASIX or ADCX command.
The active channel signals are summed to obtain one composite ADC value. This composite value is used for the normal whole-scale calibration and mass calculation. Therefore, only one metrological configuration and one standard scale calibration are required for the complete platform.
Multi-channel mode is especially useful when several load cells support the same platform, tank, hopper, or silo.
Advantages of multi-channel operation
No external junction box is required.
Each load cell can be connected directly to a separate ADC channel.
Individual load-cell monitoring.
The ADC value and millivolt signal of every load cell can be monitored separately.
Simplified fault detection.
A damaged, disconnected, overloaded, or drifting load cell can be identified more easily because its signal is available independently.
Better installation diagnostics.
Individual channel readings can reveal uneven loading, mechanical obstruction, incorrect wiring, or poor load distribution.
One calibration for the complete platform.
Although every load-cell signal is measured separately, their combined signal is calibrated as one weighing system.
Optional eccentricity correction.
Differences between load cells and position-dependent weighing errors can be compensated using individual channel correction factors.
Flexible channel count.
The same system can be configured for platforms using two, three, or four load cells. Using fewer channels also reduces the time required to acquire a complete measurement frame.
Typical applications
Multi-channel mode is recommended for:
four-load-cell platform scales;
three- or four-point silo and hopper weighing;
tank weighing systems;
systems where individual load-cell diagnostics are required;
installations where an external analogue junction box should be avoided;
platforms requiring electronic eccentricity or corner-error correction.
The main difference is that single-channel mode provides up to four independent scales, while multi-channel mode combines up to four individually monitored load-cell signals into one calibrated scale.
Get all scale and applications parameters. This is very usefully not just to get current values but also you can store them as backup of your scale configuration. To restore values you just simple replace first character R with S and send it to scale.
Command | ||
|---|---|---|
| Query all parameters. | |
Response | ||
| All parameters. | |
Example | — | |
| | |
| | |
If you need to retrieve only one parameter value you can use this command.
Command | |
|---|---|
<parameter>=? | Query parameter value. |
Response | |
| Parameter and it’s value. |
Example | |
| 1D1=? |
| 1D1=0.1 |
This command is used to set scale and applications parameters. Please note that after changing parameter values in storage they are not applied immediately. To apply new values you must either reboot scale or execute command IS to apply new settings.
Command | |
|---|---|
| Set on or multiple parameters values. |
Response | |
| Successfully set application parameter(s). |
Command | |
|---|---|
| Initialize scale with new parameters |
Response | |
| Scale initialization finished. |
Command | |
|---|---|
| Get calibration data of selected scale. If <scaleNo> parameter is set to 0 you will receive calibration data of all scales. |
Response | |
| Calibration parameters: |
Command | ||
|---|---|---|
| Calibrate selected point with selected value. | |
Response | ||
| Calibration response; see the Status parameter below. | |
Example of calibrations | ||
| | |
| | |
| | |
| | |
Parameters | Description |
|---|---|
| Calibration point number 0-8 (0 is zero calibration). |
| Weight that is placed on the scale load receptor. In case point is zero load must be 0. |
| By default stable weight during calibration process is mandatory otherwise calibration will not finish and error will be returned. |
| Status represent current status of calibration with @ followed by status character which can be: |
| Channel represent scale on which calibration is being executed – 1-4. |
| Calibration requires stable weight therefore there will be up to 10 repetitions. If stability is not reached in 10 repetitions calibration will fail unless require stable parameter was set to 0. |
| Signal from load cell expressed in points |
| Factor that was calculated for this point and provided load. |
Command | |
|---|---|
| Delete calibration point 0-8. |
Response | |
| Calibration point deleted successfully. |
By default scale works as single channel which means each channel can be connected to different platform and have different metrological data such as capacity, readout, filter etc.. Scale has four channels. In multi channel you can connect up to for load cells or platforms and get from every load cell ADC points and mV which is especially useful if you do not want to use junction boxes and monitor each load cell separately/platform while having only one calibration.
Metrological and calibration data are stored in parameters described in the table below.
Note: you can manually send any parameter to scale via any connection interface to which you set scale. Important is that you follow proper structure and start the command with SSD. See example below the table.
Parameters | Descriptions | Default | Data | Example |
|---|---|---|---|---|
sN | Channel/scale name – max 8 characters | — | char | — |
sDx | Division – D1-D3 | — | Float | — |
sMx | Maximum – M1-M3 | — | Float | — |
sRx | No. of ranges – 1-3 | — | Uint8 | — |
sxA | Point x ADC points | — | Uint32 | — |
sxW | Point x weight | — | Float | — |
sxF | Point x factor | — | Float | — |
sU | Unit | kg | Char[2] | — |
sFT | Filter: 1-1023 (1- no filter, 1023 max) | | Uint16 | — |
sFC | High resolution filter: 0-disabled, 1-enabled | | Uint8 | — |
sDS | Division for test stability | | Uint8 | — |
sZT | Zero tracking – 0-99 (0 disabled) | | Uint8 | — |
sZR | Zero range in percentage - 0 means zeroing is disabled | | Uint8 | — |
sOZ | On zero -executed zeroing in range – percentage 0-50% - 0 means on zero is disabled | | Uint8 | — |
sCW | Command timeout window – value how long to wait for stability in zeroing, taring, getting stable weight etc. in seconds 1,2,3,… | | Uint16 | — |
0SW | Stability window – how long the weight must be stable in order to set status to stable - in milliseconds | | Uint16 | |
s – means scale number 1-4
x – is consecutive number 1-n
Example:
SSD;1D1=1;1M1=1000;1U=kg
Will set up scale parameters of scale 1 with division of first range to 1 kg and capacity of first range to 1000 kg. Unit will be set to kg.
Applications have specific functionalities and parameters related to them. They are described in the following chapters.
Application common commands are:
M25 – query available applications
M26 – query current application or set specific application
Command | |
|---|---|
| Command to get request available applications. |
Response | |
| List of available applications. |
Command | |
|---|---|
| Query currently active application |
| Set application 1 – Counting. |
Response | |
| Current active application is 1 - Counting |
| Successfully set application. |
| Command received but not executable (syntax error or wrong or non-existing application number). |
PMI command can be used in counting and check weighing applications.
Command | ||
|---|---|---|
| Command to get checkweighing parameters. | |
Responses | ||
| Command executed successfully. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Command received but not executable (syntax error or wrong parameter value). | |
Examples | ||
| | |
| | |
| | |
| | |
Parameters | Description |
|---|---|
| W – weighing |
| ABS – high and low limit |
| Unit |
| Target if TolMode=REL/PER; low limit if TolMode=ABS |
| Tolerance minus if TolMode=REL/PER; high limit if TolMode=ABS |
| Tolerance plus if TolMode=REL/PER |
| Tare value |
| Average piece weight |
| Article id |
| Article description |
Parameter | Description | Default value | Range |
|---|---|---|---|
nLT | LT represent lock/unlocked tare. By default tare is locked which means that also after scale is unloaded tare will stayed stored in scale memory. If you set LT=0 tare will be automatically cleared once you unload the scale (return in zero range is required). | | |
* n represents number of scale 1-4
Counting application is calculating no. of pieces based on the provided or referenced Average Piece Weight (APW).
Parameters related to counting application are:
Parameter | Description | Default value | Range |
|---|---|---|---|
nACD | Counting decimals – when calculating number of pieces you can set to use also decimal values not just integer values. Counting decimals are used also in check mode. | | |
nACAD | APW decimals – set on how many decimals APW is calculated. | No. of decimals in first division + 2 | |
* n represents number of scale 1-4
To change or get counting application parameters you must use SAP and GAP command.
Command | |
|---|---|
| Command to get or set piece weight value. If apw and unit param’s are omitted then current piece weight value is returned. |
Responses | |
| Command executed successfully. Response includes also average piece weight value. |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). |
| Command received but not executable (syntax error or wrong parameter value). |
Examples | |
| |
| |
| |
| |
Command | |
|---|---|
| Command to execute calculation of APW. You must provide no. of pieces currently placed on the scale load receptor. |
Responses | |
| Command executed successfully. Response includes also average piece weight value. |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). |
| Command received but not executable (syntax error or wrong parameter value, net weight is zero, unstable conditions – could not perform reference). |
Examples | |
| |
| |
Command | |
|---|---|
| Command to get current number of pieces. |
Responses | |
| Response with current number of pieces and scale status. |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). |
Parameters | Description |
|---|---|
| S – stable weight |
| Current number of pieces. |
Command | |
|---|---|
| Command to get current number of pieces and weighing data. |
Responses | |
| Response with current number of pieces, scale and tolerance status and all weighing data. |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). |
Examples | |
| |
| |
| |
| |
Parameters | Description |
|---|---|
| S – stable weight |
| NA – not applicable – target/tolerances are not set |
| Gross weight |
| Net weight |
| Tare |
| Current average piece weight |
| Unit |
With PMC command you can activate check program where you can set target and tolerances (relative mode) or lower and higher limit (absolute mode) to get tolerance status based on the number of present pieces on scale. To get current values use PMI command.
Negative check counting
You can use negative check counting in relative mode where you set target in minus. In that case please note that upper and lower limit will be swapped in order to correctly determine tolerance status.
Command | ||
|---|---|---|
| Command to set checkweighing parameters. There are two modes available: | |
Responses | ||
| Command executed successfully. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Command received but not executable (syntax error, wrong parameter value or counting application not activated – see command M25/M26). | |
Examples | ||
| | Lower limit=10 pcs |
| | — |
| | Target=10 pcs |
| | — |
Parameters | Description |
|---|---|
| Target used in relative mode. If no. of pieces is equal or higher than lower limit and lower or equal than upper limit tolerance status is OK. |
| Tolerance minus is used to set lower limit and is calculated as <Target>-<TolMinus>. When no. of pieces is lower than low limit tolerance status is LO. |
| Tolerance plus is used to set upper limit and is calculated as <Target>+<TolPlus>. When no. of pieces is higher than upper limit tolerance status is HI. |
| <LowLimit> Lower limit in absolute mode. If number of pieces is lower than tolerance status is LO. |
| Unit |
| Average piece weight – value used to calculate no. of pieces. |
| Preset tare value |
| Article ID – to be used to determine which article is being counted when using PCSX command. |
| Article description |
With PMW command you can activate check weighing program where you can set target and tolerances (relative mode) or lower and higher limit (absolute mode) or provide tolerance in percentage related to target value in unit of measure. To get current values use PMI command.
Negative check weighing
You can use negative check weighing in relative mode where you set target in minus. In that case please note that upper and lower limit will be swapped in order to correctly determine tolerance status.
Command | ||
|---|---|---|
| Command to set checkweighing parameters. There are three modes available: | |
Responses | ||
| Command executed successfully. | |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). | |
| Command received but not executable (syntax error, wrong parameter value or checkweighing application not activated – see command M25/M26). | |
Examples | ||
| | Target=16.3 lb |
| | — |
| | Lower limit=10.2 kg (under) |
| | — |
| | Target=100 kg |
| | — |
| | Target=100 kg |
| | — |
Parameters | Description |
|---|---|
| Target used in relative mode. If no. of pieces is equal or higher than lower limit and lower or equal than upper limit tolerance status is OK. |
| Tolerance minus is used to set lower limit and is calculated as <Target>-<TolMinus>. When no. of net is lower than low limit tolerance status is LO. |
| Tolerance plus is used to set upper limit and is calculated as <Target>+<TolPlus>. When net is higher than upper limit tolerance status is HI. |
| <LowLimit> Lower limit in absolute mode. If net weight is lower than tolerance status is LO. |
| Unit |
| Preset tare value |
| Article ID – to be used to determine which article is being checkweighed when using CWX command. |
| Article description - to be used to get article description when using CWX command. |
Command | |
|---|---|
| Command to get current check weighing status and weighing dat. |
Responses | |
| Response with tolerance status and all weighing data. |
| Command received but cannot be executed at this time (the scale is busy processing another task or command). |
Examples | |
| |
| |
| |
| |
Parameters | Description |
|---|---|
| S – stable weight |
| NA – not applicable – target/tolerances are not set |
| Gross weight |
| Net weight |
| Tare |
| Unit |
In order to use digital inputs you must first configure them as by default all inputs are disabled.
Each digital input has two modes:
On/off
Counter
In on/off mode digital input acts as switch. If function is set it will also trigger function execution (e.g. zero scale, tare scale, etc) otherwise you can use it as you wish by monitoring it’s status.
In counter mode digital input will increase counter value each time the state of input is high. Counter value is also stored so even after module reboot it is still available. Off-course you have possibilities to set and reset counter value.
SIF command is used to setup input mode which can be on/off (classic input mode) or counter.
Command | |
|---|---|
| Command to get configuration of selected input. |
Responses | |
| Configuration of one input |
| Configuration of all inputs. |
Examples | |
| |
| |
| |
| |
Parameters | Description |
|---|---|
| Input number. Depending on the CloudScale you are using it is value from 1…n depending on the number of available inputs. |
| Digital input mode: |
| Filters switch bounce. Input must stay stable for this time before the state is accepted. To be used only when input mode is on/off. Typical value: 5-100 ms. |
| Ignores short electrical noise pulses. Pulses shorter than this time are not counted. To be used only when input mode is counter. Typical value: 1-20 µs. |
| Digital input function (only available in on/off mode): |
To use digital input you have to set it’s function first to on/off mode.
Command | |
|---|---|
| Command to get status of input. |
Responses | |
| <iS> can be 0 (input not activated) or 1 (input activated. |
| If <inputNo> is 00 response includes status of all inputs in ordered by input number from 1 to n. |
Examples | |
| |
| |
| |
| |
Command | |
|---|---|
| Command to get current counter value at selected input. |
Responses | |
| <iS> can be 0 (input not activated) or 1 (input activated. |
| If <inputNo> is 00 response includes values of all counters in ordered by input number from 1 to n. |
Examples | |
| |
| |
Command | |
|---|---|
| Command to set selected counter value. |
Responses | |
| — |
Examples | |
| |
| |
Command | |
|---|---|
| Command to clear selected counter value. |
Responses | |
| — |
Examples | |
| |
| |
| |
| |
Digital outputs enables you to control external peripherals such as lights, buzzers, relays, etc.. You can manually control outputs via commands, or you can set function and it will set output automatically according to selected function.
Command | |
|---|---|
| Command to get or set output state related to <oS> parameter: |
Responses | |
| Response for one output. |
Examples | |
| |
| |
| |
| |
| |
| |
| |
| |
Parameters | Description |
|---|---|
| Output number. Depending on the CloudScale you are using it is value from 1…n depending on the number of available outputs. |
| Output state: |
Command | |
|---|---|
| Command to get or set output function related to <oF> parameter: |
Responses | |
| Response for one output. |
Examples | |
| |
| |
| |
| |
| |
| |
| |
| |
Parameters | Description |
|---|---|
| Output number. Depending on the CloudScale you are using it is value from 1…n depending on the number of available outputs. |
| Output function: |
Command | |
|---|---|
| After changing inputs and outputs you must perform initialization or scale restart to apply changes. |
Responses | |
| — |
CSCP can be used through the device interfaces configured for the protocol. The same command structure is used; match the connection settings before exchanging commands.
Read the parameters with RSD and save the response. To restore them, replace its initial R with S to form SSD. Apply the stored settings with IS or restart the scale.
PMC sets limits for the number of pieces; PMW sets limits for weight. Read counting data with PCSX and checkweighing data with CWX. PMI reads the current target and tolerance settings.
SOT reads or changes output states. SOF reads or changes the assigned output functions. SOT,00=99 reads all states; SOF,00=99 reads all functions.
Neutron Modbus RTU/TCP reference for PLC, SCADA and HMI integration: connection, addressing, registers, calibration and automatic checkweigher control.
OPC UA integration for Neutron: secure connections, live weighing data, stable capture and PLC/SCADA integration.