BCS-NX3010

BCS Nexto - NX30x0 CPU Firmware 1.10.8.0 (current version)

BCS-NX3010 / BCS-NX3020 / BCS-NX3030 = 1.10.8.0

1.10.8.0 (BCS-NX3010 / BCS-NX3020 / BCS-NX3030)

- Support for BCS Tools 3.40.

- Fixed wrong “Factory Missing” log message

Note! New format of firmware update file. This update requires the controller running on firmware version 1.8.13.0/1.9.29.0 or greater.

URL to transition version 1.8.13.0/1.9.29.0

https://www.beijerelectronics.com/en/support/Help___online?docId=69185

URL to the revision history document for all BCS products.

https://www.beijerelectronics.com/en/support/Help___online?docId=66769

Nexto BCS-NX30x0 v1.10.8.0.zip

BCS Nexto - Cpu Firmware 1.8.13.0/1.9.29.0 (transition version)

BCS-NX3003 / BCS-NX3004 / BCS-NX3005 = 1.9.29.0
BCS-NX3010 / BCS-NX3020 / BCS-NX3030 = 1.8.13.0

Note! New format of firmware update file. This is the transition version.

1.9.29.0

- Changed firmware update mechanism to include support for the new file format that will be introduced on upcoming versions.

- Improvements in “one touch diag” feature.

- Included support for PROFINET Controller.

1.8.13.0

- Changed firmware update mechanism to include support for the new file format that will be introduced on upcoming versions.

- Included fixed DNS server settings (8.8.8.8 and 8.8.4.4).

- Improved NIC Teaming performance.

Link to the revision history document for all BCS products.

https://www.beijerelectronics.com/en/support/Help___online?docId=66769

Nexto modular v1.8.13.0_v1.9.29.0.zip

BCS NX3010/3020/3030 - Installation Guide

GI888820.pdf

BCS-NX3010 - User Manual

MU214613_rev_B.pdf

BCS Nexto modular/Nexto Xpress - PID advanced library

BCS Tools - User Manual

Doc. code: MU299609
MU299609 Rev. I 03/2023

MU299609_rev_I.pdf

BCS Tools - Programming Manual

Doc. code: MP399609
Rev. BE_B 11/2013

MP399609_BE ver B.pdf

BCS Tools - Datasheet

CE103705 Rev. K

CE103705_rev_K.pdf

BCS NX940x - User's manual (Connectors of Nexto Series)

NX9401, NX9402, NX9403 and NX9404 constitute a series of connectors used in Nexto Series of Programmable Controlers

BCS-NX940x (CE114818).pdf

BCS NX92xx - User's manual (RJ45-RJ45 Cables)

RJ45-RJ45 Cables

NX9202 RJ45-RJ45 2m cable

NX9205 RJ45-RJ45 5m cable

NX9210 RJ45-RJ45 10m cable

BCS-NX92XX (CE114800).pdf

BCS Nexto Series - User Manual

MU214600.pdf

BCS Tools Nexto - Firstscan bit

The attached is a programexample of how to create a FirstScan bit.

Structured text (ST)

Function block diagram (FBD)

ProgramExample_FirstScan_BCS140.projectarchive

BCS Tools Nexto -Programming path setup (KI00345B)

BCS Tools Nexto – Programming path setup (KI00345B).pdf

BCS Tools Nexto - Program example datalogging function

This programexample requires a SD card mounted in the cpu.

This is an example of a datalogg using the four different log categories. (INFO, WARN, ERROR, DEBUG)

Programexample_NX3010_Datalogging_BCS140.projectarchive

BCS Tools Nexto - Connecting Nexto and iX with Modbus TCP (KI00360)

BCS Tools Nexto - Compile and Project transfer (KI00346)

BCS ToolsNexto – Compile and Project transfer (KI00346B).pdf

BCS Tools Nexto - Program example read write real time clock

This is a programexample of how to read and write the real time clock in Nexto.

ProgramExample_NX3010_RealTimeClock_BCS205.projectarchive

BCS Tools Nexto - Program example read write IP address information with functionblock

This is an example of how to use the FB:s for reading and sriting IP address information in Nexto.

ProgramExample_ReadWrite_IPAddress_BCS140.projectarchive

BCS Tools Nexto - Program example read task and application information

Created in BCS Tools 1.40

ProgramExample_NX3010_ReadTaskInformation BCS140.projectarchive

BCS Tools Nexto - Program example PID functionblock

ProgramExample_PID_FB_BCS140.projectarchive

Quick start guide - Connect X2 HMI with Nexto PLC, SUEN00414

How to connect any X2 HMI with Nexto Xpress/modular PLC using Codesys ARTI or

OPC UA

Connect X2 with Nexto SUEN00414.pdf

Program example BCS Tools and iX: Nexto communication with BFI by EtherCAT

This program example contains one BCS-Tools project and one iX project. The projects are meant to be used for quick start of applications and contains most of the basic functionality needed as well as some extended functions.

Program example is intended for Nexto communicating by EtherCat with BFI-P2 or BFI-H3.

Program example support:

Works only towards BFI Frequency inverters
Start and stop
Change Setfrequency
Normal-, fast- or coasting-stop
Inverter Alarm Reset
Constant overview of Drive Outputs-, Alarm-, Safety-, Running Hours status.
Read and Write of parameters
Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber

Contain 3 files, one iX-project, one BCS-Tools and one pdf.

Programs are written in BCS-Tools 3.20 and iX Developer 2.40 SP4.

BCS Tools/Nexto - Modbus TCP and Crevis I/O, init ST-3702

Program example:
How to init a ST-3702 for Pt1000 (default value are Pt100)

Project1: Node with one ST-3702, “Modbus_ex_Nexto_ST3702_20171004.projectarchive”
Project2: Node with two ST-3702, “Modbus_ex_Nexto_2pcs_ST3702_20171004.projectarchive”

Program example BCS Tools and iX: Nexto Xpress communication with BFI by Modbus RTU.

This is to be found in Smart Engineering, SER0040. Manual describing SER0040 is to be downloaded here

Program example is intended for Nexto Xpress communicating by Modbus RTU with BFI-E3, BFI-P2 or BFI-H3.

Program example support:

Works only towards BFI Frequency inverters
Start and stop
Change Setfrequency
Normal-, fast- or coasting-stop
Inverter Alarm Reset
Constant overview of Drive Outputs-, Alarm-, Safety-, Running Hours status
Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber

Contain 3 files, one iX-project, one BCS-Tools and one pdf.

Programs are written in BCS-Tools 3.31 and iX Developer 2.40 SP5.

SER0040_QS_NextoXpress_BFI_ModbusRTU_V1.0.0-EN.pdf

Kom i gang med Nexto XPress - Grunnleggende (Norwegian)

Dette dokumentet beskriver grunnleggende funksjoner i Nexto XPress serien.

Nexto XPress er en kraftig kompakt programmerbar logisk styring (PLS). Den er en del av Nexto serien fra Beijer Electronics. Nexto XPress baserer seg på Codesys 3.5 og leverer høy ytelse med I/O inkludert i et kompakt format. .

Nexto XPress passer i små applikasjoner og som remote I/O. Det har opp til 43 I/O om bord og er enkelt utbyggbart via innebygde porter, som ethernet, CAN og RS-485.

Vedlagt eksempel prosjektet som beskrives i dokumentet

Get Started with Nexto Xpress - MQTT communication

The Nexto XPress series from Beijer Electronics includes a library (LibMQTT) for communication via ‘Message Queuing Telemetry Transport’ (MQTT).

MQTT is a lightweight protocol that requires little bandwidth. It can also be encrypted and is therefore well suited for communications against cloud services (IIOT).

Communication takes place between a client (eg Nexto XP325) and a server service (Broker). Once a client has published data to Broker, other clients can subscribe to it.

Attached example project as described in the document

Get Started with Nexto Xpress - The Basics

Nexto Xpress is a powerful compact programmable logic controller (PLC). It is a part of the Nexto family from Beijer Electronics. Nexto Xpress delivers high performance in a compact format.

Nexto Xpress fits in small applications and as remote I/O. It has up to 43 on board I/O and is easily expandable via built-in ports, such as Ethernet, CAN and RS-485.

Attached example project as described in the document

Get Started with Nexto Xpress - High speed datalogging

This document describes high-speed data logger in Nexto XPress.

The Nexto XPress series from Beijer Electronics includes a library (LibDatalogger) for logging high-speed data to local files in CSV format. The files are stored in persistent memory for later analysis in a spreadsheet (eg Excel®). The minimum logging frequency is 10ms in triggered mode and 100ms in continuous mode.

The generated CSV files can be stored as follows:

• Internal FLASH memory (retrieved with BCS Tools)

• USB memory

Attached example project as described in the document

BCS Tools, MODBUS Symbol Server/Client

Example with one Server (NX3020) and one Client (NX3010)
- 3 Register (Holding) to Send
- 3 Register (Holding) to Read
- 1 bit (Coil) to Send
- 1 bit (Coil) to Read

Setup in Server

Setup in Client

Tags TO / FROM server

Modbus Communication to "IP-address" (To the Server)

NEXTO_ModbusSymbol_Client_Server_BCSTools_206.zip

Get started with Nexto Xpress - IEC60870-5-104

The Nexto Xpress series from Beijer Electronics include a driver for communication via the IEC protocol IEC60870-5-104.

IEC60870-5-104 was originally a protocol developed for the energy sector, but is also widely used in infrastructure projects for roads and railways.

To test the communication, a small test-project in the Scada-system zenon from Copadata is used. Zenon has certified IEC drivers and a widely used Scada system in the energy sector.

Attached PLC-project, library and SCADA-application as described in the document.

The document is in English and Norwegian language.

Get Started with Nexto Xpress - Database communication

This document describes how to communicate with Nexto Xpress/Modular and Microsoft SQL server.

Nexto Xpress and Nexto Modular includes a library, LibSQLClient, to enable the ability to communicate directly with a Microsoft SQL server by using the TDS 4.2 protocol. There is no need for any intermediate software.

Supported database:

Microsoft SQL with TDS 4.2 protocol

Supported commands:

SELECT
INSERT INTO
UPDATE
DELETE FROM

BCS Tools Nexto - Task priority and scheduling

In Nexto there are two schedulers, the Realtime scheduler and the Normal scheduler.

The realtime tasks are mapped to priority 0-15 i BCS Tools and tasks with priority 16-31 are mapped to the normal scheduler.

What is the difference between a task mapped to the realtime scheduler vs normal scheduler?

The realtime tasks, Prio 0-15, are deterministic, this means that these tasks will execute independently of communication (Modbus, etc....)
The normal tasks, Prio 16-31, are not deterministic, this means that depending on the system load the execution time willl be affected.

How are tasks interrupting each other?

Tasks within the range 0-15 will interrupt each other and they will interrupt the 16-31 tasks (normal), the lower number will interrupt the higher number, and will execute until it finishes (unless another lower number realtime tasks interrupts it).

Tasks within the range 16-31 (normal) will not interrupt tasks within the range 0-15 (realtime). They will interrupt each other and will be interrupted by system tasks and also by the realtime tasks (0-15)

The task named MainTask is by default set to Priority 13 = realtime task -> deterministic execution

BCS Tools Nexto -After compilation Memory 0 - 6 are presented, what do these mean?

Size of generated code = is the space used on the application from the program area.
Size of global data = is the space used on the application from the symbolic variable memory

Memory 0 contains Data = Symbolic variables memory
Memory 1 contains Retain Data = Retain Symbolic variables memory
Memory 2 contains Persistent Data = Persistent Symbolic variables memory
Memory 3 contains Input = Addressable input variables memory (%I)
Memory 4 contains Output = Total addressable output variables memory (%Q)
Memory 5 contains Memory = Addressable variable memory (%M)
Memory 6 contains Code = Program memory

BCS Tools Nexto - Diagnostic variables with IP address information

IP address information is available via the diagnostic variables or by using the function blocks.
The information is available as string and byte.

For example using the function blocks refer to related links.

Clarification about the force function in CODESYS

Background
Force Variables is a feature created in PLCs originally to force inputs, the purpose of this is to test the application without the field signals.

Function
In all CODESYS based PLCs the force feature works as a table of values to write to certain variables every PLC cycle. Different from the write command that happens once, the write of force happens every cycle. When it comes to internal variables that a written to in PLC code the force function will not be effective.

In CODESYS based PLCs (for example SoftControl, SoftMotion, Nexto, Xtorm and others) the force function is executed twice in a cycle, once after read inputs and once before write outputs according to the following picture.

Example of force of internal variable where the user program will have prescendence.

BCS Tools Nexto - Task information and I/O update synchronization

When using the Basic project profile in BCS Tools 3 tasks are created.
MainTask
ExternInterruptTask00
TimeInterrruptTask00

Since the priority is within the range 0-15 all tasks are handled as realtime tasks. (For more details regarding Task priority and scheduling see related links.)

What is not seen in the project is that there is an additional task called ConfigurationTask, this task handles services in the backplane like "Read module diagnostics", "Send module parameters", "Communication with NX5000 module", etc.....
This task has Priority 4 and executes cyclic with an interval of 4 - 30ms depending on the amount of I/O modules installed -> it will interrupt the MainTask.

This is an example of why the communication processing of the NX5000(ethernet) module is handled by the ConfigurationTask. Imagine that the application executed by the MainTask takes approx 100ms to execute.
To maintain a good communication performance the ConfigurationTask keeps interrupting the MainTask to ensure a good communication bandwitdh with the NX5000 modules.

How is the I/O update synchronized with the user program?

The I/O update is synchronized with the MainTask and it is divided into three parts.

1. Read Inputs, CPU sends an EtherCAT frame to get the inputs from the mounted modules
2. Execute the POU:s associated with the MainTask.
3. Write Outputs, CPU sends an EtherCAT frame to set the outputs to the mounted modules

When using additional tasks like a time interrupt task the I/O update is not performed, if an I/O update is required in tasks you have to use the REFRESH_INPUT/REFRESH_OUTPUT instructions located in the NextoStandard library.

NX5001, Profibus DP Master.

The NX5001 works like a regular I/O module, however in this case the I/O image is much bigger (while a regular module can have a few bytes of I/O, NX5001 can handle up to 3584 bytes for inputs and 3584 bytes for outputs.
In the begining of the MainTask (before running the user code), the CPU reads the input image from NX5001, the same thing happens in the end of MainTask (after running the user code) for the output image.
The Profibus DP scan is carried out in a asynchronous mode totally indpendent of CPU<->NX5001 local bus scan. NX5001 scans all Profibus DP slaves and store the input/output image into a triple buffer scheme (internal to NX5001),
meaning that CPU can access this data anytime without any need of waiting (data is always ready).

Consistency issues?

Since PROFIBUS has no support for 32-bit, the only way to achieve this is mapping the information into two standard 16-bit channels.
This is a standard practice found on several slaves. Regarding the consistency, theoretically you would only have problems if these two 16-bit parts could be accessed separately and asynchronously.
However this is impossible.

- Data update on PROFIBUS Slave: the servo ensures that these 2 16-bit parts will be updated on PROFIBUS Slave chip memory at the same moment.
- NX5001 reads the inputs from the servo: all the inputs from that slave will come in one same PROFIBUS telegram. (no way to read each 16-bit part individually)
- CPU reads the inputs from NX5001: all the inputs (from all slaves) are read in the same moment on MainTask before the execution of user program.

MODBUS Master/Slave, DNP3

These protocols (MODBUS, DNP3 and any other future similar protocols) runs on low priority ("normal" scheduler, non-real time). It means that they only run when MainTask is not running.
They will only update data (%I, %Q or Symbolic Data) when MainTask is not running, because they can not "wake up" and execute during the execution of MainTask.
However, there is a special case: MainTask can start to execute exactly when MODBUS is updating data (because it is real time and can interrupt the MODBUS task).
The consequence is that if MODBUS Master (for example) is performing a read command of 125 Holding Registers, the MainTask can interrupt it in the middle of this update so it may see some Holding Registers with value of previous polling and some withe the value of the latest polling.
In this special case there is an interlock implemented to lock MainTask execution when MODBUS is updating a mapping data. Each mapping can have maximum of 250 bytes, in practice it will take a few microseconds to copy this data.

MODBUS data is never updated in the middle of MainTask execution (cycle time).

BCS Tools Nexto - Download Boot Application during RUN

The 'Boot Application' is the program code the cpu will load and execute after powering on or resetting the system. see, chapter 7.3 in KI00346. When a download is the made with the Nexto CPU in STOP mode the downloaded project will be registered as a Boot application.

NOTE! Online changes doesn’t update the Boot Application. this need to be updated manually from the BCS Tool when logged in to the Nexto system. The 'Create boot applcaition can be performed with the CPU in RUN mode.

BCS Tools - Using the library NextoPID and Util at the same time causes a naming conflict for the PID instruction

Using the library NextoPID and Util at the same time causes a naming conflict for the PID instruction when compiling.

To distinguish between different instructions with the same name but located in different libraries use the following syntax,
"libraryname.instruction", NextoPID.PID.

BCS Tools Nexto - Add PID Loops online

Is it possible to add PID loops online without stopping control of the cpu?

In Nexto PID loops can be used together with a premade faceplate or only as FB. Regardless of type they can both be added online without stopping control.

Faceplate version

FB without faceplate

BCS NX3010/3020/3030 - Support of Flood attacks on local and external Ethernet ports

Both the internal Ethenet ports (NET1 / NET2) of the CPU's and the Ethenet module NX5000
has support protection against 'flood attacks'.

BCS NX3010/3020/3030 - Real Time Clock (backup time)

Real Time Clock (RTC): The retention time, time that the real time clock will continue to update the date and time after a CPU power down, is 15 days for operation at 25 ºC. At the maximum product temperature, the retention time is reduced to 10 days.

BCS Nexto modular/Nexto Xpress - Firmware update procedure

Valid for Nexto Xpress BCS-XP300, BCS-XP315, BCS-XP325
and Nexto modular PLC BCS-NX3003, BCS-NX3004, BCS-NX3005, BCS-NX3010, BCS-NX3020, BCS-NX3030.

Use a webbrowser and type in the IP address of the CPU (NET1), in this case ip 192.168.15.1.

The CPU must be in STOP mode to upgrade firmware.

Firmware Update:

1. Select tab "Firmware Update" and Login to CPU with admin / admin.
Note, select "Change password" to change login.

2. Select file and start Firmware Update (note option to Erase Application):

3. Update in progress, latest firmware is being sent to the CPU...

4. CPU is updating firmware...

5. CPU will restart...

6. Firmware update finished successfully...

7. In the CPU Overview you can see actual firmware version and CPU status...

Change login password:

CODESYS/BCS Tools - Support of REAL (32-bit) and LREAL (64-bit)

They are required to represent rational numbers, and according to IEC-standard and documentation of CODESYS the floating point values can be both REAL (32 bits) and LREAL (64 bits).
Value range for REAL: 1.175494351e-38 to 3.402823466e+38
Value range for LREAL: 2.2250738585072014e-308 to 1.7976931348623158e+308

Test in BCS NEXTO-series and NX3010 (same in NX3020, and NX3030.
REAL (32-bit) and LREAL (64-bit)

64-bit REAL is fully supported in both Nexto modular and Xpress.

NOTE (from CODESYS online help):
- The support of data type LREAL depends on the target device. Please see in the corresponding
documentation whether the 64 bit type LREAL gets converted to REAL during compilation
(possibly with a loss of information) or persists.

- If a REAL or LREAL is converted to SINT, USINT, INT, UINT, DINT, UDINT, LINT or ULINT
and the value of the real number is out of the value range of that integer, the result will be undefined
and will depend on the target system. Even an exception is possible in this case! In order to get
target-independent code, handle any range exceedance by the application. If the REAL/LREAL number is
within the integer value range, the conversion will work on all systems in the same way.

BCS Nexto - How to update firmware in a Nexto CPU in RUN mode

The CPU has to be in STOP to update the firmware. If you cannot access the CPU from BCS Tools use the following procedure:

You cannot change the CPU state via web since it is a security issue.

What you can do is to power up the CPU with the top button pressed during the initialization period. After the boot-up time, the CPU will show "APP NOT LOADED" message and will not read the application from internal memory and run. It will remain in STOP mode.

Then you can easily update the firmware via the web interface.

Nexto serial pinout for COM ports

Nexto - Reserved ports

Reserved TCP-/UDP-ports:
The following ports of the Ethernet interfaces, both local and remote, are used by CPUs services,
so they are reserved and cannot be used by the user: 80, 8080, 1217, 1740, 1741, 1742,1743 and 11740.

BCS-Nexto/Nexto Xpress - Number of supported ARTI connections

BCS-NX3010/3020/3030 = 8 ARTI connections (from firmware 1.5.0.10)

BCS-NX3003/3004/3005 = 8 ARTI connections (from firmware 1.7.49.0)

BCS-XP300/315/325/340 = 8 ARTI connections ( from firmware 1.7.46.0)

ARTI connections include iX connection with ARTI driver, BCS Tools connection and Codesys OPC DA server connection.

BCS Tools - The address %QBxxxxx not defined in any device

What does this comiler warning mean?
"The address %QB41653 is not defined in any device. Perhaps address is not used"

Answer
The address %QB41653 is connected to the diagnostics variables for the Profibus DP master, might be another address based on the hardware configuration and cpu parameters.
The reason for this message lays in the compiler, CODESYS was developed to use the %I and %Q as IO mappings and the diagnostics in NEXTO are not IO mappings. When using the diagnostics in the user application the compiler thinks that the usage of the address is wrong since not being mappep as a IO mapping.
It is not possible to disable this warning.

BCS Tools - OPC connection to the CPU or the simulator in BCS Tools.

When installing BCS Tools the OPC server from CoDeSys is installed in the background.

To configure the OPC server to connect to the simulation mode in BCS Tools do the following:
(When connecting to the cpu this step can be ignored)

Set the project to simulation mode

Create the Symbol Configuration object and select the variables to be exposed.

Call the configuration screen for the OPC server.

Use these settings to connect to the simulator in BCS Tools.
Local host addr: 127.0.0.1
Device Port: 11739

Use these settings to connect to the CPU.
Local host addr: IP address to the cpu
Device Port: 11740

Screenshot of Matrikon OPC Explorer connected to the OPC server in BCS Tools.

Nexto Modular/Nexto Xpress - TLS support

Nexto Xpress with firmware 1.9.9.0 or later supports TLS 1.0, 1.1 and 1.2.

Nexto modular NX3003/NX3004/NX3005 with firmware 1.9.8.0 or later supports TLS 1.0, 1.1 and 1.2.

Nexto modular NX3010/NX3020/NX3030 all firmware versions only supports TLS 1.0.

Nexto modular/Nexto Xpress - MQTT TLS certificate validity check

At connection handshake when using certificates for TLS there is a validation check against the validity period of the certificate and the actual time set in the RTC.

Very important to make sure that the RTC is set with the current time otherwise the connection establishment will fail if the RTC is outside the validity period of the certificate.

How to download Free software packages from SmartStore

This document provides guidelines for customers when downloading free software and firmware packages from SmartStore. The following chapter describes the procedures of:

• Setting up free user account in SmartStore

• Purchase process (Free item only)

• Download Software / Firmware packages

How to download Free software packages from SmartStore - EXTERNAL_2023.08.08.pdf

BCS Nexto - ARTI/OPC communication

From BCS Tools 2.0 and cpu firmware 1.4.0.33 ARTII/OPC communication is supported.

- Keep in mind that this only works with the built-in ports and NOT the NX5000.

For example iX panels (TxA/ TxB / TxC) with CODESYS ARTI driver can communicate with BCS-Nexto system.

Example of a Modbus/TCP client via PLC code using the Oscat library

In the example Modbus Function Code 3 and 16 (read multiple holding registers and write multiple holding registers) are used to read and write 100 holding registers every 100 ms.

Example for Nexto (3010 CPU) is created with BCS Tools 2.03

Example for TxB-SoftControl (hardware with firmware 3.5.7.10) is created with CoDeSys 3.5 SP7 Patch 3

BCS Nexto Xpress/Modular - MQTT version

The current MQTT stack implemented in Nexto Xpress and Nexto Modular supports;
- MQTT v3.1.1
- MQTT v3.1

LTB Life Cycle Notification BCS-NX940x spareparts

04--LTB_beijer_electronics_life_cycle_notification--BCS-NX940x--2021-03-03.pdf

BCS Nexto/Nexto Xpress - MQTT certificate support

When using encypted MQTT communication with TLS, communication is established by using X.509 certificates. These certificates can have different encoding schemes where one being the PEM(Base64 ASCII) or DER (binary).

Normally PEM files uses the extension *.crt, *.pem, *.cer and *.key and DER files normally uses *.der or *.cer.

With the current firmware:
Nexto Xpress XP3xx/Nexto modular NX3008 1.12.24.0
Nexto modular NX300x 1.12.23.0 and
Nexto modular NX30x0 1.10.8.0
in combination with LibMQTT 1.0.0.8 only Base64 ASCII encoded certificates can be used.

DER encoding scheme is no supported.

The manual states using certificated with *.crt extension, it is confirmed that also *.pem works fine as long as the enconding scheme is supported.

More details about encoding schemes and extension can for example be found here:
https://www.ssl.com/guide/pem-der-crt-and-cer-x-509-encodings-and-conversions/#ftoc-heading-2

Nexto I/O update with EtherCat master

The EtherCAT Master for Nexto have 2 "modes" of I/O update:

1) Update all the I/O in one task only (bus cycle task)

2) Update the I/O in the context of each task

The selection of this "mode" is made by the following setting:

When this setting is checked, you are on "mode" 2. Otherwise, "mode" 1. The bus cycle task ("mode" 1) is selected here:

For "mode" 1, by default the bus cycle task is assigned to MainTask, but you can assign to some other task if you want. For example, you can assign it for a TimeInterrupt task. In this case, Nexto I/O modules will be updated on MainTask, and EtherCAT I/O will be updated on TimeInterrupt (preempting the MainTask).

For "mode" 2, the EtherCAT Master will perform the I/O update on the context of each task which uses some EtherCAT I/O on some POU. So, it means that the bus activities can be spread into several tasks.

The local bus I/O also have these two "modes", and you can select it on the CPU configuration window:

Please note that these "modes" are not an official terminology...it is just a way to help on the explanation.

Regarding the REFRESH_INPUT/REFRESH_OUTPUT function, they are very specific and must be used only on MainTask and only for local Nexto I/O modules. If you want I/O update on other task than MainTask, you should use the "update/messages per task" options described above.

Now, finally, lets take a look at the moment that the I/O update is performed on each of these scenarios:

Nexto - Persistent variables loose their value if the name of the application changes

In the current and older versions of BCS Tools (2.05) and cpu firmware (1.5.1.3) if the application name is changed from "Application" to something else the persistent variables will loose their values every power off/on.

Currently you should use the default name "Application".

This issue has been addressed and will be solved in a future version of BCS Tools.

Always use the default name "Application"

Workaround

By using BCS Tools 2.06 and firmware 1.5.1.7 you can change name of the application and the persistent function will still work. This is valid for a single system. Do not change the Application name in a redundant setup.

Nexto - Check operating status of I/O modules

The attached document contains a "best practice" method to monitor the operational state of rack mounted I/O modules. This method is the recommended to use when creating interlock and alarms from the I/O modules.

NAP15900.pdf

BCS Tools - Edit CSV files with Excel 2013 or newer might destroy and make the csv files unusable for BCS Tools

When editing exported csv files with Excel 2013 or newer Excel might detroy the format of the csv files after saving it.

As a workaround OpenOffice Calc can be used instead of Excel.

https://www.openoffice.org/download/index.html

BCS Tools Nexto - Program example Clockpulses

Program example of how to make clockpulses for Nexto system (NX3010 cpu).

The example include 1 minute, 1 second and 100ms puls

Attached projectarchive file, created in BSC Tools 2.00.

Programexample_NX3010_Clockpulse_BCS200.projectarchive

BCS Nexto Series CPU - Datasheet

BCS-NX30xx - Datasheet
Datasheet BCS-NX3003, BCS-NX3004, BCS-NX3005, BCS-NX3010, BCS-NX3020, BCS-NX3030

CE114100_revR.pdf

BCS Nexto Series - Datasheet

Nexto Series Programmable Logic Controller
- Complete list of modules

CE114000.pdf

Beijer Control system: Nexto Series catalog

Take control over your business with Nexto Series programmable controllers

Nexto Series is an advanced automation system capable of controlling, in a distributed and redundant way, complex industrial processes, machines and high performance production lines. Modern and fast, Nexto products are based on cutting edge technology in order to provide trustworthiness and connectivity, contributing to your business productive growth.

BCS-Nexto modular 2018-05-08 web.pdf

Download BCS Tools from SmartStore

To download the current and older versions of BCS Tools please visit Smart Store: https://smartstore.beijerelectronics.com/

Download latest BCS Tools version

BCS Nexto modular - DNV approval

TAA00001BU_10.pdf

BCS Nexto/Nexto Xpress - UL/cUL certificate

Please use these links to access the UL/cUL certified Nexto/Nexto Xpress products

UL
https://iq.ulprospector.com/en/profile?e=222921

cUL
https://iq.ulprospector.com/en/profile?e=246429

NOTE!
- BCS Nexto only has UL approval
- An account has to be created (for free) to access the certificates

BCS Nexto Modular - CE EMC/LVD Declaration

DC414001.pdf

BCS Nexto Modular - UKCA Declaration

DC414061.pdf

BCS Nexto modular - CAD symbols

NAMING OF FILES
Example: NX3010_20130529.dwg.zip

Where:
NX3010 : product name
20130529 : file date in the format "YYYYMMDD" (in this example: May, 29th 2013)
dwg : file format provided

FILE VERSION:
DWG - Autocad 2002 or higher
STEP - AP214

BCS Tools/BCS Nexto/BCS Nexto Xpress - Revision history

RevisionHistoryProductsBEIJER - 230905.pdf

BCS Nexto - MiB files for SNMP monitoring

MiB files for SNMP monitor function in Nexto. (BCS-NX3004, BCS-NX3010, BCS-NX3020, BCS-NX3030)

SNMP functionality requires cpu firmware 1.4.0.33 or later.

Article number	66.014.120-4
Warranty	2 year

Certificates	CE, ROHS, UL, DNV
Module dimensions (W x H x D)	36.00 x 114.63 x 115.30 mm
Net weight	350 g

Hot Swap	Yes
One Touch Diag (OTD)	Yes
Status and diagnostics indication	Yes
Redundancy	No
Maximum nbr of expansion racks	8
Maximum nbr of modules	128
Clock synchronization (SNTP)	SNTP
Network monitor (SNMP)	SNMPv1, SNMPv2c, SNMPv3
Program memory	4MB
Source code memory	40MB
User files memory	16MB

Communication protocols	Ethernet/IP Scanner/Adapter, ModbusTCP client/server, Modbus RTU master/slave, User defined protocol, OPC UA/DA server
Ethernet interface	1xRJ45 10/100 Mbps
Serial interface	1xRS-232, 1xRS422/485

Registration

Registration

You'll get more

New user?

Log in

Products

Control systems

Nexto modular PLC

High-speed CPU

Facts

General description

Mechanical

Power

System

Communication

Smart Engineering Resources

Resources

Firmware

Program examples/Start-up

Adverts

Catalogues

Certificates

Information document

Manuals

Knowledge

Data sheets

Software

Drawings

Configuration files

BCS Nexto - NX30x0 CPU Firmware 1.10.8.0 (current version)

BCS Nexto - Cpu Firmware 1.8.13.0/1.9.29.0 (transition version)

BCS NX3010/3020/3030 - Installation Guide

BCS-NX3010 - User Manual

BCS Nexto modular/Nexto Xpress - PID advanced library

BCS Tools - User Manual

BCS Tools - Programming Manual

BCS Tools - Datasheet

BCS NX940x - User's manual (Connectors of Nexto Series)

BCS NX92xx - User's manual (RJ45-RJ45 Cables)

BCS Nexto Series - User Manual

BCS Tools Nexto - Firstscan bit

BCS Tools Nexto -Programming path setup (KI00345B)

BCS Tools Nexto - Program example datalogging function

BCS Tools Nexto - Connecting Nexto and iX with Modbus TCP (KI00360)

BCS Tools Nexto - Compile and Project transfer (KI00346)

BCS Tools Nexto - Program example read write real time clock

BCS Tools Nexto - Program example read write IP address information with functionblock

BCS Tools Nexto - Program example read task and application information

BCS Tools Nexto - Program example PID functionblock

Quick start guide - Connect X2 HMI with Nexto PLC, SUEN00414

Program example BCS Tools and iX: Nexto communication with BFI by EtherCAT

BCS Tools/Nexto - Modbus TCP and Crevis I/O, init ST-3702

Program example BCS Tools and iX: Nexto Xpress communication with BFI by Modbus RTU.

Kom i gang med Nexto XPress - Grunnleggende (Norwegian)

Get Started with Nexto Xpress - MQTT communication

Get Started with Nexto Xpress - The Basics

Get Started with Nexto Xpress - High speed datalogging

BCS Tools, MODBUS Symbol Server/Client

Get started with Nexto Xpress - IEC60870-5-104

Get Started with Nexto Xpress - Database communication

BCS Tools Nexto - Task priority and scheduling

BCS Tools Nexto -After compilation Memory 0 - 6 are presented, what do these mean?

BCS Tools Nexto - Diagnostic variables with IP address information

Clarification about the force function in CODESYS

BCS Tools Nexto - Task information and I/O update synchronization

BCS Tools Nexto - Download Boot Application during RUN

BCS Tools - Using the library NextoPID and Util at the same time causes a naming conflict for the PID instruction

BCS Tools Nexto - Add PID Loops online

BCS NX3010/3020/3030 - Support of Flood attacks on local and external Ethernet ports

BCS NX3010/3020/3030 - Real Time Clock (backup time)

BCS Nexto modular/Nexto Xpress - Firmware update procedure

CODESYS/BCS Tools - Support of REAL (32-bit) and LREAL (64-bit)

BCS Nexto - How to update firmware in a Nexto CPU in RUN mode

Nexto serial pinout for COM ports

Nexto - Reserved ports

BCS-Nexto/Nexto Xpress - Number of supported ARTI connections

BCS Tools - The address %QBxxxxx not defined in any device

BCS Tools - OPC connection to the CPU or the simulator in BCS Tools.

Nexto Modular/Nexto Xpress - TLS support