BCS-NX9000

Resources

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

ProgramExample_NX3010_RealTimeClock_BCS205.projectarchive

Resources

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

Resources

Created in BCS Tools 1.40

ProgramExample_NX3010_ReadTaskInformation BCS140.projectarchive

Resources

ProgramExample_PID_FB_BCS140.projectarchive

Resources

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

Resources

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

Resources

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

Structured text (ST)

Function block diagram (FBD)

ProgramExample_FirstScan_BCS140.projectarchive

Resources

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

Resources

By default the NX6020 doesn't support the sensortype NI1000LG (quite common in building automation) Currently the way to support this senortype is to use the FB in the attached library. Use NI1000 in the hx configuration of the NX6020 module.

2016-10-10 08-44-35.png

LG_Ni1000.compiled-library

Resources

The attached program is an example of how to create an event/trigger based Modbus TCP communication.

ProgramExample_NX3010_ModbusTCP_EventBasedCommunication_BCS131.projectarchive

Resources

Simple test project that shows setup an addressing.

ProgramExample_NX3010_FnIO_NA-9173_BCS201.projectarchive

Resources

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”

Resources

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.

Resources

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

Resources

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 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.20 and iX Developer 2.40 SP4.

Resources

Program example is intended for Nexto CPU BCS-NX3020 communicating by Modbus TCP with BFI-P2 or BFI-H3. BCS-NX3020 can easily be exchange to any CPU model from BCS-NX3003 to BCS-NX3030.

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 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.

Resources

Program example to demonstrate how to connect i4SCADA to Nexto Xpress and Nexto modular.

Requirements
i4SCADA 3.8.3 or newer
BCS Tools 3.10 or newer
Nexto Xpress firmware 1.7.0.12 or newer
Nexto modular firmware 1.7.0.3 or newer

Xpress_OPCUA_Test.zip

Resources

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

Resources

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

Resources

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 boardand is easily expandable via build-in ports, such as Ethernet, CAN and RS-485.

Attached example project as described in the document

Resources

This document describes how we can log high speed data 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

Resources

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).

Resources

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

Resources

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

Resources

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.

Resources

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), it works!

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.

Resources

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.

Resources

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.

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:

Resources

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.

Resources

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

Resources

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.

Resources

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

Resources

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.

Resources

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.

Resources

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.

Resources

The inputs of BCS-NX6000 is of differential type. This means that the 0V (common) of each input is not internally connected.

The same thing applies for HX6000 for Xtorm.

Resources

Requirements
When the OpenLoop alarm variable is set to TRUE by the module the input value should report the last valid value (freeze). The timing of the alarm and behaviour of the value is:

1. Analog input is set to either 0, Min or Max value depending of the setting made in the BCS-NX6000 module.
2. The variable OpenLoop alarm is set to TRUE.

Solution
This function is not available to achieve by the available parameters. As an alternative is possible to achieve this with code.

Settings in BCS-NX6000
- Type = Current 4 – 20 mA
- Digital Filter = Disabled
- Open Loop Value = 0

Code example
VAR
                iInput_LastValue: INT;
                Analog_Output : INT;
END_VAR

//Analog_Input = Input Channel of NX6000
//Analog Output = Last Valid Value of NX6000

IF (Analog_Input <> 0) THEN

                Analog_Output := Analog_Input;
                iInput_LastValue := Analog_Input;
ELSE
                Analog_Output := iInput_LastValue;
END_IF

Resources

This is an example of when using Nexto as Modbus Master to RS-485 slaves by using a the Ethernet to RS-485 gateway, JetPort 5601.

Configuration

Nexto Modbus RTU over TCP --- TCP/IP --- JetPort 5601 --- RS485 --- NA-9173 --- NA-9173.

For each slave configured in Nexto a seperate TCP session is established, therefore it is important that the Gateway supports multiple sessions. (This is valid for the Modbus Symbol Client driver, by using the IEC address based Modbus Client driver one TCP session can be created for several slaves. Another option when using the Symbol driver is to make a sequence and disconnect the slave after each polling))

In this case the JetPort 5601 supports 5 sessions (clients) at the same time.

(A startup problem has been detected with the 1.06 FW in JetPort 5601. By disabling one connection communication starts and then the other can enabled again.)

Resources

Gratuitous ARP:
NET1 Ethernet interface of NX5000 module sends spontaneously ARP type packets in broadcast, informing its IP and MAC address for all devices interconnected to the network. These packets are sent during the download of a new application by the BCS Tools software and in the startup of a NX5000 interface. 5 ARP commands are sent, with an initial interval of 200 ms, doubling the interval between every new triggered command, totalizing 3 s. Example: First trigger occurs at time 0, the second one at 200 ms, the third one at 600 ms and so forth until the fifth trigger occurs at time 3 s.

Resources

Bus Expansion module (NX4000)
- Each expansion rack can be located up to 100 m far from each other, using standard shielded CAT5 Ethernet cables

Redundancy link modules (NX4010)
- Up to 100 m distance from each redundant systems using standard shielded CAT5 Ethernet cables

Note!
By using the JetCon Media Converter 1300 Series (JetCon 1301) the distance between each Rack I/O module or betweeen redundant systems can be improved very much. For example JetCon 1301-sw (artno. 70125) a Industrial Ethernet to Single Mode Fiber Converter, -40~80°C, SC, Single-mode/30 km.

More info in attached datasheet and http://korenix. com/jetcon-media-converter-1300-series.htm

JetCon 1301: Slim-sized Fast Ethernet to Fiber Media Converter
- One 10/100 TX port to One 100FX port media converter
- Dual Forwarding modes- Switching and Pure converter
- Supports Auto MDI/MDI-X, Auto Negotiation
- Supports Multi-mode 2KM, Single-mode 30KM
- Auto Link Loss Forwarding for fault detection
- Extreme Low Data Forwarding Latency- 1.6 x 10-6 Sec
- Wide range of AC18-27V/DC18-32V power inputs with DC polarity protection
- Aluminum case with IP31 grade protection
- Supports 1.5KV Hi-PoT isolation protection
- Supports single fiber transmission – WDM
- Operating temperature -10~70°C (-40~80°C wide operating temperature model available by request)

JetCon1301-48V-low.pdf

Resources

In BCS Tools there is a setting that will affect the Modbus protocol for the Client driver.

Modbus TCP should be used when communicating to other Modbus TCP units. A TCP session will be established with every slave and requests will be sent in parallel to all configured slaves.

Modbus RTU over TCP should be used when communicating to other Modbus RTU slaves connected on a serial line like RS-485/RS-232 through a ethernet to serial gateway. Some gateways are strictly media converters and some can act as Modbus gateways. When using a non Modbus gateway Modbus RTU over TCP should used in Nexto and if the gateway can act as a Modbus gateway Modbus TCP should be used.
A TCP session will be established for every configured slave but the requests for all configured will be sent in a sequence.

Resources

The projectarchive file contains all GSD information of the slaves being used in the project.

Resources

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 = 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.

Resources

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

Resources

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:

Resources

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.

Resources

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

Resources

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.

Resources

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

Resources

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.

Resources

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.

Resources

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

Resources

Must be used together with a redundant CPU.

GI888831.pdf

Resources

GI888830.pdf

Resources

GI888820.pdf

Resources

CPU User's manual
BCS-NX3003
BCS-NX3004
BCS-NX3005
BCS-NX3010
BCS-NX3020
BCS-NX3030

Resources

BCS-NX8000 (CE114200).pdf

Resources

GI888821.pdf

Resources

GI888821.pdf

Resources

Backplane Rack Accessories
NX9100 and NX9102 were developed to provide superior protection for Nexto Series backplane racks.

BCS-NX910x (CE114810).pdf

Resources

nx90xx__racks_.pdf

Resources

16 DI Module 24 Vdc

BCS-NJ1001 (CE114306).pdf

Resources

BCS-NX1001 (CE114301).pdf

Resources

GI888823.pdf

Resources

Mixed Module 8 DO Transistor / 8 DI, 24 Vdc

BCS-NJ1005 (CE114311).pdf

Resources

CE114300.pdf

Resources

GI888822.pdf

Resources

GI888822.pdf

Resources

Transistor Module 16 DO, 24 Vdc

BCS-NJ2001 (CE114405).pdf

Resources

GI888825.pdf

Resources

BCS-NX2020 (CE114402).pdf

Resources

GI888826.pdf

Resources

CE114401.pdf

Resources

8 AI Voltage/Current Module

BCS-NJ6000 (CE114307).pdf

Resources

BCS-NX6000 (CE114302).pdf

Resources

GI888824.pdf

Resources

4 AO Voltage/Current Module

BCS-NJ6100 (CE114406).pdf

Resources

BCS-NX6100 (CE114403).pdf

Resources

GI888827.pdf

Resources

8 AI Thermocouple Module

BCS-NJ6010 (CE114309).pdf

Resources

8 AI RTD Module
Support for different types of RTD sensors: Pt100, Pt200, Pt500, Pt1000, Ni100,
Ni120, Ni200, Ni500and Ni1000
Support for multiple resistance range: 0 to 400 Ω, 0 to 4000 Ω and 0 to 10000 Ω

BCS-NJ6020 (CE114308).pdf

Resources

BCS NX6010 supports 8 different types of thermocouple: J, K, B, E, T, R, S and N

GI888834 - NX6010.pdf

Resources

BCS-NX6020 (CE114304).pdf

Resources

BCS NX6020 supports different types of RTD sensors like Pt100, Pt1000, Ni100, Ni1000 etc.

GI888833 - NX6020.pdf

Resources

BCS-NX6010 (CE114303).pdf

Resources

GI888829.pdf

Resources

BCS-NX5000 (CE114903).pdf

Resources

MODBUS TCP Head

BCS-NX5100 (CE114909).pdf

Resources

PROFIBUS-DP Master

BCS-NJ5001 (CE114902).pdf

Resources

BCS-NX5210 (CE114908).pdf

Resources

MU214601.pdf

Resources

GI888828.pdf

Resources

Nexto Series Programmable Logic Controller
- Complete list of modules

BCS-Nexto series Tachnical characterstics (CE114000).pdf

Resources

MU214600.pdf

Resources

BCS-NX4010 (CE114900).pdf

Resources

BCS-NX4000 (CE114600).pdf

Resources

BCS NX3010/NX3020/NX3030 - Installation Guide

GI888820.pdf

Resources

RJ45-RJ45 Cables

BCS-NX92XX (CE114800).pdf

Resources

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

BCS-NX940x (CE114818).pdf

Resources

Doc. code: MU299609
Rev. BE_B 11/2013

MU299609.pdf

Resources

Doc. code: MP399609
Rev. BE_B 11/2013

MP399609_BE ver B.pdf

Resources

Doc. code: CE103705
Rev: BE_B 11/2013

BCS-Nexto series Tachnical characterstics (CE114000).pdf

Resources

BJE_5210.GSD

Resources

BJE_5110.GSD

Resources

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.

Resources

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

Resources

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

Resources

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

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

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

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

Resources

DC114120_190221.pdf

Resources

TAA00001BUr6.pdf

Resources

BCS Tools based on CODESYS V3.5 software, offers full customization, object-oriented graphics and user-friendly programming, with enhanced editing-control integrating application program, fieldbus and process networks into a single interface. Furthermore, BCS Tools enables online / offline simulation for pre-run evaluation and testing and enhanced functionalities guaranteeing optimum developing time productivity.

Note! To use all features in BCS Tools 3.11 make sure to use

BCS NEXTO CPU Firmware 1.7.0.5 for NX3004/NX3005, version 1.7.0.3 for NX3010/NX3020/NX3030 or 1.7.0.12 for XP300/XP315/XP325 or later.

Firmware versions older than 1.7.0.xx is not supported by BCS Tools 3.11.

Version 3.11

New Features

- Added I/O Simulator page.

- Added new hot swap mode “Hot Swap Disabled Without Startup Consistency” for following devices: NX3003, NX3004, NX3005, NX3010, NX3020, NX3030 and NX5100.

- Updated help.

- Added encryption to OPC UA.

- Opens the declarations editors (GVL and POUS) in tabular mode.

Enhancements

- Added a message box to warning about changing values when user leaves a page.

- Fixed the error message when use a Basic license.

Version 3.10

New Features

- Added support to Nexto Xpress PLCs XP300, XP315 and XP325;

- Added support to NX3003 PLC;

- Added support to NX5101 MODBUS TCP Head;

- Added support to OPC UA configuration;

- Added EtherNet/IP Adapter;

- Added checkbox in the project wizard to create the directory to project’s files;

- Added Find in Project command in menu Edit;

- Added Replace in Project command in menu Edit;

- Added Browse Call Tree command in menu Edit > Browse;

- Added MasterTool IEC XE Perspective command in menu View > Choose Perspective;

- Added HMI Perspective command in menu View > Choose Perspective;

- Added Visualization command in menu View > HMI Views;

- Added HMI Features command in menu View > HMI Views;

- Added Programmings command in menu View > HMI Views;

- Added Datasources command in menu View > HMI Views;

- Added Commit Accepted Changes command in menu Project;

- Added Insert Execute Box command in menu FBD/LD/IL;

- Added Add to Recipe Definition command in context menu of the POUs and GVLs;

- Added Browse Call Tree command in context menu of the POUs;

- Added Export Library command in context menu of the Library Manager;

- Included Encryption tab in the Application object;

Enhancements

- The parameter “Minimum Error Before Clock Update” accepts a new range from 1 up to 65519 ms;

BCS Tools V311.zip

Resources

BCS Tools based on CODESYS V3.5 software, offers full customization, object-oriented graphics and user-friendly programming, with enhanced editing-control integrating application program, fieldbus and process networks into a single interface. Furthermore, BCS Tools enables online / offline simulation for pre-run evaluation and testing and enhanced functionalities guaranteeing optimum developing time productivity.

Note! To use all features in BCS Tools 3.12 make sure to use

BCS NEXTO CPU Firmware 1.7.17.0 for NX3004/NX3005, version 1.7.0.8 for NX3010/NX3020/NX3030 or 1.7.17.0 for XP300/XP315/XP325 or later.

Firmware versions older than 1.7.0.xx is not supported by BCS Tools 3.12.

Version 3.12

New Features

- Added CANopen for XP325.

- Added Fast Inputs Screen to XP300, XP315 and XP325 in Integrated I/O.

- Added Fast Output Screen to XP300, XP315 and XP325 in Integrated I/O.

- Added Interruption option and Counter Interrupts to NX3003 in Integrated I/O.

- Added Import and Export to NX3003, XP300, XP315 and XP325.

- Updated help with CANopen.

- Opens the declarations editors (GVL and POUS) in tabular mode.

Enhancements

- Automatically open the project update window for outdated projects.

Known issue(s)

- BCS Tools v3.12 is failing to install on Windows 8.1 64-bit. The workaround for this specific platform is to install version 3.11, and then version 3.12 over it.

Version 3.11

New Features

- Added I/O Simulator page.

- Added new hot swap mode “Hot Swap Disabled Without Startup Consistency” for following devices: NX3003, NX3004, NX3005, NX3010, NX3020, NX3030 and NX5100.

- Updated help.

- Added encryption to OPC UA.

- Opens the declarations editors (GVL and POUS) in tabular mode.

Enhancements

- Added a message box to warning about changing values when user leaves a page.

- Fixed the error message when use a Basic license.

BCS Tools 3.12.zip

Article number	66.014.723-7
Warranty	2 year

Certificates	CE, ROHS, UL, DNV
Module dimensions (W x H x D)	163.70 x 119.00 x 18.58 mm
Net weight	270 g

Registration

Registration

You'll get more

New user?

Log in

Products

Control systems

Modular PLC

Backplane rack 8-slots

Contact us

Facts

General description

Mechanical

Power

Resources

Program examples/Start-up

Adverts

Configuration files

Drawings

Software

Knowledge

Manuals

Catalogues

Certificates

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources

Resources