BCS-NX9000
BCS-NX9001
BCS-NX9002
BCS-NX9003
BCS-NX9020
BCS-NX9102
Facts
General description
| Article number | 66.014.724-5 |
| Warranty | Up to 2 years |
Mechanical
| Certificates | CE, ROHS, UL, DNV |
| Module dimensions (W x H x D) | 163.70 x 119.00 x 18.58 mm |
| Net weight | 220 g |
Resources
Manuals
Program examples/Start-up
Brochures
Knowledge
Software
Certificates
| File name | Date | |
|---|---|---|
| BCS Nexto Modular - CE EMC/LVD Declaration | 2023-07-06 11:17:07 | |
| BCS Nexto modular - DNV approval | 2023-05-29 16:03:11 | |
| BCS Nexto Modular - UKCA Declaration | 2023-07-06 11:19:24 | |
| BCS Nexto/Nexto Xpress - UL/cUL certificate | 2022-10-03 10:39:08 |
Drawings
Information document
Configuration files
| File name | Date | |
|---|---|---|
| BCS Nexto - MiB files for SNMP monitoring | 2022-10-20 12:32:33 | |
| Configuration file Profinet (xml) for BFI-H3 and BFI-P2 | 2024-08-01 14:55:34 |
Firmware
Data sheets
| File name | Date | |
|---|---|---|
| BCS Nexto Series - Datasheet | 2024-01-30 11:03:50 | |
| BCS-NX90xx - Datasheet | 2024-06-24 09:19:04 |
BCS Nexto modular/Nexto Xpress - PID advanced library
Manual: Solution Ethernet IP communication Nexto PLC with BFI-P2 BFI-H3
Manual: Solution Profinet communication Nexto PLC with BFI-P2 BFI-H3
Manual: Solution EtherCAT communication Nexto PLC/X2control with BFI-P2 BFI-H3
Manual: Solution Modbus RTU communication Nexto PLC/X2control/PIO with BFI-P2 BFI-H3 BFI-E3
Manual: Solution CanOpen communication Nexto PLC with BFI-P2 BFI-E3
Manual: Solution Modbus TCP communication Nexto/X2control/PIO PLC with BFI-E3
Manual: Solution Modbus TCP communication Nexto/X2control/PIO PLC with BFI-P2 BFI-H3
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 NX92xx - User's manual (RJ45-RJ45 Cables)
RJ45-RJ45 Cables
Program example BCS Tools and iX: EtherCAT communication between Nexto PLC/X2control and BFI-P2 BFI-H3
This program examples can be Auto configurated in BCS Tools 3.62. The Auto configuration for EtherCAT is turned ON/OFF in BCS Tools, Tools/Options/Device Configuration.
This program example is also to be found as Smart Engineering object, SER0017. Either download the manual further down for SER0017 or the complete Smart Engineering here. If using this program example make sure that Device Configuration is turned OFF.
Program example is intended for a Nexto, X2-control/Marine/Extreme communicating by EtherCat with 2 pieces of BFI-P2 and BFI-H3.
Version of Library file for BFIEtherCat functionblock is 2.0.0.0.
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, communication type, Input voltage, Power, Frame size, Firmware and serialnumber
One PLC-program example is intended for Nexto Xpress XP300 and any X2 HMI.
One PLC-program example is intended for X2 control and it's built-in X2 HMI.
One iX-project to monitor/control BFI through the PLC.
Another PLC-program example is intended for Nexto Xpress XP340 with Webvisu.
Used softwares are BCS Tools 3.62 and iX Developer 2.50.
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: Modbus TCP communication between Nexto/X2control/PIO PLC and BFI-P2 BFI-H3
This program examples can be Auto configurated in BCS Tools 3.62.
They are also available as Smart Engineering, SER0014. Either download the manual below or the complete Smart Enginnering here.
PLC-program example is intended for a Nexto, X2-control/Marine/Extreme or PIO PLC communicating by Modbus TCP with 2 pieces of BFI-P2 and BFI-H3. Version of Library file for BFIP2H3ModbusTCP functionblock is 1.0.0.2.
There is also an iX-project supporting all Beijer PLC:s, all communication buses and and all BFI.
Program example support:
- Works only towards BFI Frequency inverters
- Activate/Deactivate communication
- 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 all parameters and data available in the inverter
- Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber
One PLC-program example is intended for Nexto Xpress XP300 and any X2 HMI.
One PLC-program example is intended for X2 control and it's built-in X2 HMI.
One PLC-program example is intended for PIO, GN-9373, and any X2 HMI.
One iX-project made for any X2 to monitor/control BFI.
Another PLC-program example is for Nexto Xpress XP340 with Webvisu.
Used softwares are BCS Tools 3.62 and iX Developer 2.50.
Program example BCS Tools and iX: Modbus RTU communication between Nexto/X2control/PIO PLC and BFI-P2 BFI-H3 BFI-E3
|
Program example BCS Tools and iX: Ethernet IP communication between Nexto PLC and BFI-P2 BFI-H3
This program examples can be Auto configurated in BCS Tools 3.62.
They are also available as Smart Engineering, SER0040. Either download the manual below or the complete Smart Enginnering here.
PLC-program example is intended for a Nexto, XP300 PLC, communicating by EtherNet IP with 2 pieces of BFI-P2 and BFI-H3. Version of Library file for BFIP2H3EtherNetIP functionblock is 1.0.0.0.
There is also an iX-project supporting all Beijer PLC:s, all communication buses and and all BFI.
Program example support:
- Works only towards BFI Frequency inverters
- Activate/Deactivate communication
- 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 all parameters and data available in the inverter
- Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber
One PLC-program example is intended for Nexto Xpress XP300 and any X2 HMI.
One iX-project made for any X2 to monitor/control BFI.
Used softwares are BCS Tools 3.62 and iX Developer 2.50.
Program example BCS Tools and iX: Profinet communication between Nexto PLC and BFI-P2 and BFI-H3
This program example can also be Auto configurated in BCS Tools 3.62. If using this programexample make sure that Device Configuration for Profinet is turned OFF in BCS Tools, Tools/Options/Device Configuration.
This program example is to be found as Smart Engineering, SER0077. Either download the manual further down for SER0077 or the complete Smart Engineering here.
Program example is intended for a Nexto PLC XP300 communicating by Profinet with 2 pieces of BFI-P2 and BFI-H3.
Program example support:
- Works only towards BFI Frequency inverters
- Activate/Deactivate communication
- 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 all parameters and data available in the inverter
- Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber
One PLC-program example is intended for Nexto Xpress XP300 and any X2 HMI.
One iX-project made for any X2 to monitor/control BFI.
Used softwares are BCS Tools 3.62 and iX Developer 2.50.
Program example iX Developer: Project for PLC-program generated in BCS Tools or Smart Engineering for PLC communicating with BFI by bus.
The iX project can be used for Beijer PLC communicating with BFI. It supports PLC-programs generated in BCS Tools 3.62 or Smart enginnering objects SER 0014, 0015, 0017, 0020, 0039, 0040 and 0077. Project created in iX-version 2.50.
PLC can be X2(control/Marine/Extreme), Nexto Xpress, Nexto Modular or PIO.
Buses can be one of or a mix of EtherCat, Modbus TCP, Modbus RTU, CANopen, Profinet, EtherNet IP.
Frequency inverters can be BFI-E3, BFI-P2 or BFI-H3.
BCS / Codesys and Dynamic IP on modbus slave
29.10.2024
BCS tools 3.63 \ Codesys
Works on all targets nexto Xpress X2 control etc.
Project is made for xpress340
To be able to change the slave IP from plc code, on need to use the standard codesys modbus slave. The native nexto / Beijer variant do not support this.
To be able to access the codesysmodbus libraries on nexto targets (In BCS tools), one need to add an ethernet interface to the NET1:
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
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)
Program example BCS Tools and iX: CanOpen communication between Nexto PLC and BFI-P2 BFI-E3
This program examples can be Auto configurated in BCS Tools 3.62.
They are also available as Smart Engineering, SER0039. Either download the manual below or the complete Smart Enginnering here.
Program examples are intended for Nexto PLC NX-30xx or XP3xx communicating by CanOpen with BFI-E3 BFI-P2 . Version of Library file for BFICanOpen functionblock is 1.0.0.0.
Program example support:
- Works only towards BFI Frequency inverters
- Activate/Deactivate communication
- 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 all parameters and data available in the inverter
- Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber
One PLC-program example is intended for Nexto Xpress XP300 and any X2 HMI.
One iX-project made for any X2 to monitor/control BFI.
One PLC-program example is intended for Nexto Xpress XP340 with Webvisu.
Used softwares are BCS Tools 3.62 and iX Developer 2.50.
Get started with Nexto Xpress - IEC60870-5-104
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
Program example BCS Tools and iX: Modbus TCP communication between Nexto/X2control/PIO PLC and BFI-E3
This program example can be Auto configurated in BCS Tools 3.62.
They are also available as Smart Engineering, SER0020. Either download the manual below or the complete Smart Enginnering here.
Program examples are intended for a Nexto PLC NX-30xxx or XP3xx, X2-control/Marine/Extreme or PIO communicating by Modbus TCP with 2 pieces of BFI-E3 Version of Library file for BFICanOpen functionblock is 1.0.0.1.
Program example support:
- Works only towards BFI Frequency inverters BFI-E3-xxx-MTP
- Activate/Deactivate communication
- 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 all parameters and data available in the inverter
- Read of Drive type, Input voltage, Power, Frame size, Firmware and serialnumber
One PLC-program example is intended for Nexto Xpress XP300 and any X2 HMI.
One PLC-program example is intended for X2 control and it's built-in X2 HMI.
One PLC-program example is intended for PIO, GN-9373, and any X2 HMI.
One iX-project made for any X2 to monitor/control BFI.
One PLC-program example is intended for Nexto Xpress XP340 with Webvisu.
Used softwares are BCS Tools 3.62 and iX Developer 2.50
Program example Px (X2/BoX2 control/Nexto Xpress/Modular - BSD v3.38
This program example contains everything you need in order to get your X2/BoX2/Nexto control solution with BCS Tools and BSD products up and running using basic servo functionality.
Programming environment needed for this example:
- iX Developer v2.51
- BCS Tools v3.63
The startup example contains:
- BCS363_Px_v338.projectarchive : BCS Tools project for X2 control 7 (powerfail) and 8 servo axis.
- BCS363_Px_v338_NX3008.projectarchive : BCS Tools project for BCS-NX3008 and 8 servo axis.
- iX251_X2_Pro_7_BSD_CSx_Px_v505 : iX project version 5.05 for X2 control 7"
Note!
- iX project iX251_X2_Pro_7_BSD_CSx_Px_v505 must be used in combination with BCS Tools project BCS363_Px_v338.projectarchive due to name changes of variables.
- Name change SC -> CSx_Px, CS = Cyclic Synchronous, P = profile mode, x = generic term for either position (P), velocity (V) or torque (T)
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/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.
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 - 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 DA 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:
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
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
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.
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
Download BCS Tools from SmartStore
To download the current and older versions of BCS Tools please visit Smart Store: https://smartstore.beijerelectronics.com/
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 - 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
- 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
- NX3003_20200904.dwg.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
- NX9020_20241202.dwg.zip
- NX9020_20241202.step.zip
- NX9102_20130611.step.zip
- NX9102_20130709.dwg.zip
- Readme.txt
Configuration file Profinet (xml) for BFI-H3 and BFI-P2
Also .bmp included in the package.
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.
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.
BCS Nexto Series - Datasheet
Nexto Series Programmable Logic Controller
- Complete list of modules
