Resurser

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

Resurser

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

Resurser

Question:
When will the Persistent and Retain variables be saved in Nexto?

Answer:
The Persistent and Retain variables are saved at power off.

X = value is kept

Resurser

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.

Resurser

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.

Resurser

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

Resurser

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

Resurser

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:

Resurser

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

Resurser

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.

Resurser

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.

Resurser

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

Resurser

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.

Resurser

TxA-/TxB-Softcontroller: Fractions of seconds are not possible to read. The blocks used are avaliable, but the RTC does not return the last 3 digits for fractions of a second.

Nexto: Yes, requires functions blocks to read. See related links for which function blocks to use.

Nexto 3020 supports SNTP.

Resurser

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.

Resurser

NX3010
NET1 = 192.168.15.1
Subnet = 255.255.255.0
Gateway = 192.168.15.253

NX3020/NX3030
NET1 = 192.168.15.1
Subnet = 255.255.255.0
Gateway = 192.168.15.253

NET2 = 192.168.16.1
Subnet = 255.255.255.0
Gateway = 192.168.16.253

For more details refer to the Startup document.

Resurser

Resurser

Product Features of Nexto CPUs NX3010, NX3020 or NX3030

More details in the manual of the CPUs.

Resurser

Resurser

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

Resurser

Resurser

Resurser

• BCS140_ModbusRtuOverTcpGateway.projectarchive
• JP5601_export.conf

Resurser

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

Resurser

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.

Resurser

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

Resurser

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

Resurser

Resurser

Resurser

Resurser

Resurser

Resurser

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.

Resurser

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.

Resurser

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

Resurser

Resurser

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:

Resurser

​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

Resurser

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

• Nexto_ModbusTCP_Client_via_PLC_code.projectarchive
• TxB_SC_ModbusTCP_Client_via_PLC_code.projectarchive

Resurser

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

Resurser

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

Resurser

• ProgramExample_PID_FB_BCS140.projectarchive

Resurser

Created in BCS Tools 1.40

• ProgramExample_NX3010_ReadTaskInformation BCS140.projectarchive

Resurser

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

Resurser

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

• ProgramExample_NX3010_RealTimeClock_BCS205.projectarchive

Resurser

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

Resurser

• BCS ToolsNexto – Connecting Nexto and iX with Modbus TCP (KI00360).pdf
• NextoImport_v10.xls

Resurser

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

Resurser

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

Structured text (ST)

Function block diagram (FBD)

• ProgramExample_FirstScan_BCS140.projectarchive

Resurser

• BCS Tools Nexto - Digital IO modules NX1001 NX1005 NX2001 NX2020 KI00348B.pdf
• ProgramExample_Digital_IO_BCS140.projectarchive

Resurser

• BCS Tools Nexto – Analog IO NX6000, NX6100 (KI00347B).pdf
• ProgramExample_Analog_IO_BCS140.projectarchive

Resurser

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

• LG_Ni1000.compiled-library

Resurser

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

• ProgramExample_NX3010_ModbusTCP_EventBasedCommunication_BCS131.projectarchive

Resurser

Simple test project that shows setup an addressing.

• ProgramExample_NX3010_FnIO_NA-9173_BCS201.projectarchive

Resurser

• BCS Tools Nexto - Modbus TCP and Crevis IO (KI00350).pdf
• ProgramExample_NX3010_ModbusTCP_Crevis_BCS131.projectarchive

Resurser

• BCS Tools Nexto - Profibus DP and Crevis IO (KI00349B).pdf
• ProgramExample_NX3010_ProfibusDP_Crevis_BCS140.projectarchive

Resurser

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

• BCSTools_NextoXpress_BFI_ModbusRTU_v100.projectarchive
• HelpNextoXpressBFIModbusRTU.pdf
• iX_NextoExpress_BFI_Modbus_v100.zip

Resurser

​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”

• Modbus_ex_Nexto_2pcs_ST3702_20171004.zip
• Modbus_ex_Nexto_ST3702_20171004.zip
• Nexto_modbus_crevis_init_ST3702.pdf

Resurser

​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

Resurser

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

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

• BCSTools_Nexto_BFI_ModbusTCP_v100.projectarchive
• HelpNextoBFIModbusTCP.pdf
• iX_Nexto_BFI_Modbus_v100.zip

Resurser

​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

Resurser

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

• BCSTools_Nexto_BFI_ETC_v100.projectarchive
• HelpNextoBFIEtherCat.pdf
• iX_NextoCANopenEtherCat_BFI_v100.zip

Resurser

​

• KIN00103A.pdf

Resurser

​

• KIN00102B.pdf

Resurser

​

• KIN00101B.pdf

Resurser

​

• KIN00100C.pdf

Resurser

​BCS-NX3003 / BCS-NX3004 / BCS-NX3005 = 1.8.11.0
BCS-NX3010 / BCS-NX3020 / BCS-NX3030 = 1.8.3.0

1.8.11.0

- Included support for MQTT Client Function Block (requires BCS Tools 3.19 or greater).
- Included support for the latest version of LibSQLClient library.
- Included support for Ethernet/IP Adapter and Scanner. (BCS-NX3003 and BCS-NX3004)
- Fixed an error that could occur when performing a specific sequence of modification of the size of Retain/Persistent %Q area.
- Fixed EasyConnection behavior, where the application was not being erased after applying the new IP adress, resulting on returning to the IP address set by the application.
- Fixed maximum number of ARTI/OPC DA connections from 4 to 8. (BCS-NX3003 and BCS-NX3004)
- General fixes on User Rights Management, which was not working properly on version 1.7.x.x
- Included support for visualization of the integrated I/O by LCD (menu Hardware). (BCS-NX3003)
- Improvements in the performance of integrated fast I/O (BCS-NX3003)

1.8.3.0

- Included support for MQTT Client Function Block (requires BCS Tools 3.19 or greater).
- Included support for the latest version of LibSQLClient library.
- General fixes on User Rights Management, which was not working properly on version 1.7.x.x

Firmware update procedure
https://www.beijerelectronics.com/en/support/Help___online?docId=47791

• Nexto modular v1.8.3.0_1.8.11.0.zip

Resurser

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

Resurser

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

• CE114100_Datasheet_Nexto_modular.pdf
• nx30xx__user_manual_.pdf

Resurser

• GI888820.pdf

Resurser

• GI888830.pdf

Resurser

Must be used together with a redundant CPU.

• GI888831.pdf

Resurser

• GI888821.pdf

Resurser

• GI888821.pdf

Resurser

• BCS-NX8000 (CE114200).pdf

Resurser

• nx90xx__racks_.pdf

Resurser

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

• BCS-NX910x (CE114810).pdf

Resurser

• GI888823.pdf

Resurser

• BCS-NX1001 (CE114301).pdf

Resurser

16 DI Module 24 Vdc

• BCS-NJ1001 (CE114306).pdf

Resurser

• GI888822.pdf

Resurser

• CE114300.pdf

Resurser

• GI888822.pdf

Resurser

​Mixed Module 8 DO Transistor / 8 DI, 24 Vdc

• BCS-NJ1005 (CE114311).pdf

Resurser

• CE114401.pdf

Resurser

• GI888826.pdf

Resurser

• GI888825.pdf

Resurser

• BCS-NX2020 (CE114402).pdf

Resurser

​Transistor Module 16 DO, 24 Vdc

• BCS-NJ2001 (CE114405).pdf

Resurser

• BCS-NX6000 (CE114302).pdf

Resurser

• GI888824.pdf

Resurser

​8 AI Voltage/Current Module

• BCS-NJ6000 (CE114307).pdf

Resurser

• GI888827.pdf

Resurser

• BCS-NX6100 (CE114403).pdf

Resurser

​4 AO Voltage/Current Module

• BCS-NJ6100 (CE114406).pdf

Resurser

• GI888834 - NX6010.pdf

Resurser

• BCS-NX6010 (CE114303).pdf

Resurser

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

• GI888833 - NX6020.pdf

Resurser

• BCS-NX6020 (CE114304).pdf

Resurser

​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

Resurser

​8 AI Thermocouple Module

• BCS-NJ6010 (CE114309).pdf

Resurser

• BCS-NX5000 (CE114903).pdf

Resurser

• GI888829.pdf

Resurser

​MODBUS TCP Head

• BCS-NX5100 (CE114909).pdf

Resurser

• GI888828.pdf

Resurser

​PROFIBUS-DP Master

• BCS-NJ5001 (CE114902).pdf

Resurser

• MU214601.pdf

Resurser

• BCS-NX5210 (CE114908).pdf

Resurser

Doc. code: MP399609
Rev. BE_B 11/2013

• MP399609_BE ver B.pdf

Resurser

Doc. code: MU299609
Rev. BE_B 11/2013

• MU299609.pdf

Resurser

Doc. code: CE103705
Rev: BE_B 11/2013

• BCS-Nexto series Tachnical characterstics (CE114000).pdf

Resurser

​Nexto Series Programmable Logic Controller
- Complete list of modules

• BCS-Nexto series Tachnical characterstics (CE114000).pdf

Resurser

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

• BCS-NX940x (CE114818).pdf

Resurser

​RJ45-RJ45 Cables

• BCS-NX92XX (CE114800).pdf

Resurser

• MU214600.pdf

Resurser

BCS NX3010/NX3020/NX3030 - Installation Guide

• GI888820.pdf

Resurser

• BCS-NX4000 (CE114600).pdf

Resurser

• BCS-NX4010 (CE114900).pdf

Resurser

• BJE_5110.GSD

Resurser

• BJE_5210.GSD

Resurser

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.

• BEIJER-NEXTO-NX3004.mib
• BEIJER-NEXTO-NX3010.mib
• BEIJER-NEXTO-NX3020.mib
• BEIJER-NEXTO-NX3030.mib

Resurser

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

• NJ1001_20150928.dwg.zip
• NJ1001_20150928.step.zip
• NJ1005_20170714.dwg.zip
• NJ1005_20170714.step.zip
• NJ2001_20150928.dwg.zip
• NJ2001_20150928.step.zip
• NJ6000_20150928.dwg.zip
• NJ6000_20150928.step.zip
• NJ6001_20170714.dwg.zip
• NJ6001_20170714.step.zip
• NJ6005_20170714.dwg.zip
• NJ6005_20170714.step.zip
• NJ6010_20150928.dwg.zip
• NJ6010_20150928.step.zip
• NJ6011_20170714.dwg.zip
• NJ6011_20170714.step.zip
• NJ6020_20150928.dwg.zip
• NJ6020_20150928.step.zip
• NJ6100_20150928.dwg.zip
• NJ6100_20150928.step.zip
• NJ6101_20170714.dwg.zip
• NJ6101_20170714.step.zip
• NX1001_20121204.dwg.zip
• NX1001_20130820.step.zip
• NX1005_20121204.dwg.zip
• NX1005_20130820.step.zip
• NX2001_20121204.dwg.zip
• NX2001_20130820.step.zip
• NX2020_20121204.dwg.zip
• NX2020_20130711.step.zip
• NX3004_20150629.dwg.zip
• NX3004_20150629.step.zip
• NX3005_20160901.dwg.zip
• NX3005_20160901.step.zip
• NX3010_20130611.step.zip
• NX3010_20130709.dwg.zip
• NX3020_20130708.step.zip
• NX3020_20130709.dwg.zip
• NX3030_20130708.step.zip
• NX3030_20130709.dwg.zip
• NX4000_20121204.dwg.zip
• NX4000_20130708.step.zip
• NX4010_20121204.dwg.zip
• NX4010_20130711.step.zip
• NX5000_20121204.dwg.zip
• NX5000_20130711.step.zip
• NX5001_20121204.dwg.zip
• NX5001_20130711.step.zip
• NX5110_20160915.dwg.zip
• NX5110_20160915.step.zip
• NX5210_20160915.dwg.zip
• NX5210_20160915.step.zip
• NX6000_20121204.dwg.zip
• NX6000_20130820.step.zip
• NX6010_20130820.dwg.zip
• NX6010_20130820.step.zip
• NX6020_20140331.dwg.zip
• NX6020_20140331.step.zip
• NX6100_20121204.dwg.zip
• NX6100_20130820.step.zip
• NX8000_20130708.step.zip
• NX8000_20130709.dwg.zip
• NX9000_20150629.dwg.zip
• NX9000_20150629.step.zip
• NX9001_20121204.dwg.zip
• NX9001_20130610.step.zip
• NX9002_20130611.dwg.zip
• NX9002_20130611.step.zip
• NX9003_20121204.dwg.zip
• NX9003_20130611.step.zip
• NX9010_20150702.dwg.zip
• NX9010_20150702.step.zip
• NX9102_20130611.step.zip
• NX9102_20130709.dwg.zip
• Readme.txt

Resurser

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.

​

• BCS Tools V311.zip

Resurser

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.

• BCS Tools 3.12.zip

Resurser

The CODESYS Version 3 based software BCS Tools 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.

To use all features in BCS Tools 1.40 make sure to use cpu firmware version >= 1.3.0.21.

Version 1.40
- Changed the installer based in Microsoft InstallShield to installer based in Inno Setup. This change reduces the installation time.
- Added MODBUS devices with mappings of symbolic variables.
- Added Import/Export command to CSV files. This command imports or exports the project configurations.
- Added Import/Export support to the MODBUS Symbolic drivers.
- Added a new analog I/O module: NX6010 – 8 Ch. Thermocouple Input Module.
- Added one new library:
·    LibLogs: new function block to manage CSV files into the memory card;
 - Updated IoDrvNextoBus IODriver version to 1.0.0.48 with the following changes:
·    Improvements on internal configurations of some modules after performing a hot-swap;
·    Improvements on behaviour of channel timeout and changes the channel timeout to 2 seconds;
- Updated IoDrvNextoModbus IODriver version to 2.1.0.9 with the following changes:
·    Implementations to support MODBUS devices with mappings of symbolic variables;
·    Improvement to receive MODBUS serial frames before 3.5 characters silence;
·    Improvements in generation of mappings list;
- Updated IoDrvNexto5001 IODriver version to 1.1.0.29.
- Updated NX3010, NX3020 and NX3030 Device Description version to 1.2.1.30.
- Updated NX1001 Device Description version to 1.2.0.3 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX1005 Device Description version to 1.2.0.5 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX2001 Device Description version to1.2.0.4 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX2020 Device Description version to 1.2.0.4 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX4000 Device Description version to 1.1.0.6 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX4010 Device Description version to 1.0.1.5 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX5000 Device Description version to 1.0.1.4 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX5001 Device Description version to 1.1.1.4 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX6000 Device Description version to 1.2.0.5 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX6100 Device Description version to 1.2.0.3 with the following changes:
·    Improvements on internal configurations of module;
- Updated NX8000 Device Description version to 1.0.1.3 with the following changes:
·    Improvements on internal configurations of module;

• BCS Tools 1.40.zip
• Cpu Firmware v1.3.0.21.zip

Resurser

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

Resurser

• DC114120_190221.pdf

Resurser

• TAA000013D_2.pdf

Resurser

​Please use this link to access the UL certified Nexto prducts

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

An account has to be created (for free) to access the certificate