ETH-BIT

ETH-BIT

ELZET80's Ethernet-to BITBUS gateways are available as IP65 ruggedized surface box, in two rail mount versions and in a 19 inch rack version. All can work as masters or slaves. When working as a master, the TCP/IP BAPI server listens on port 8044 for BITBUS messages encapsulated in a simple TCP/IP message following BEUG recommendation BAPI/TCP, unwraps them and passes them to the BITBUS. Answers are sent back in the same TCP/IP wrapped form.

Up to 16 different applications can simultaneously connect to one ETH-BITx, even from different machines. They are differentiated by their automatically assigned source task field. Moving from BITBUS-add-on cards to Ethernet is transparent to your application: The BAPI-DLL for Windows® that ships with ETH-BIT is compatible to our DLLs for the PC add-on-boards IPC-BITxxx and the USB-BIT USB-Gateway.

 

  • RS485 BITBUS- interface (62,5 kBit/s to 1,5 MBit/s)
  • Full BITBUS message length
  • 10 and 100 MBit Ethernet node
  • Master or Slave-operation
  • No application software changes necessary from IPC-BITxx
  • Direct access to TCP/IP server from non-Windows® OS
  • ETH-BIT wall mount box
    • IP65 ruggedized for industrial/outdoor use -40..+50°C ambient
    • IP65 surface mount in electrician friendly size (130x94mm)
    • PoE option: No need for local power supply
    • Spring cage terminals for BITBUS and i/o accept a wide range of solid an stranded wire
    • CAT5 LSA terminal for ETHERNET takes solid installation cable as well as patch cable
  • ETH-BIT/R DIN rail mount version
    • Isolated BITBUS RS485-connection
    •  RJ45-plug as well as DB9-plug and -socket for BITBUS
    • relay for universal application
  • ETH-BIT E/F 19" rack and flat rail versions
    • Isolated BITBUS RS485-connection with Repeater lines (RTS)
  • Prices
  • Details
  • OEM-Modules
  • Installation
"Rail mount version of the Ethernet-to-Bitbus-converter"

449.- € *

ETH-BITR

Rail mount version of the Ethernet-to-Bitbus-converter, operating voltage 24V. (Not available with PoE, please use ETH-BIT<POE for your PoE application)

"Flat rail mount version of the Ethernet to BITBUS converter"

449.- € *

ETH-BITF

Flat rail mount version of the Ethernet to BITBUS converter (width 93mm). Operating voltage 24V (no PoE). With screw terminal plugs and Sub-D 9 for BITBUS. RTS signal (suitable for slave use in repeater networks)

"Ethernet to BITBUS converter as 19 inch 3U board"

479.- € *

ETH-BITE

Ethernet to BITBUS converter, 19 inch version 3U, Depth 111mm (+ RS232 Service connector if right angle). Operating voltage 24V (no PoE). Sub-D 9 for BITBUS. RTS signal (suitable for slave use in repeater networks)

"Wall mount box with Ethernet, BITBUS and one RS232 port"

499.- € *

ETH-BIT

Wall mount box with Ethernet, BITBUS and one RS232 port. Local 24V DC supply required (apply to internal spring clamp terminals). Includes BAPI server software and remote BAPI-DLLs for all modern Windows® operating systems.

538.- € *

ETH-BIT<POE

As above, but with isolated "Power-over-Ethernet" supply (IEEE802.3af) through the Ethernet cable. Provides 200mA* at 24V for external devices.
*) current derating with high temperatures

"OEM version of the Ethernet-to-BITBUS gateway, integrated 24V supply"

399.- € *

ETH-BITM

OEM version of the Ethernet-to-BITBUS gateway, board only. Custom assembly of header connectors or Sub-D/RJ45 (straight/right angle) per your requirements. Comes with 24V supply but can be supplied by 3.3V alternatively. RS485 and CMOS level signals. RTS for use in repeater networks.

"OEM version of the Ethernet-to-BITBUS gateway"

369.- € *

ETH-BITS

OEM version of the Ethernet-to-BITBUS gateway, board only. Needs 5V supply from 24VDC converter (NET-PS5 at 39€) or PoE supply (NET-PoE24/5 at 78€).

For your i/o requirements near the gateway:

"Ethernet/BITBUS-Gateway with 4 optoisolated 24V digital inputs and 4 relays"

539.- € *

ETH-BIT4I4R

Ethernet/BITBUS-Gateway with 4 optoisolated 24V digital inputs and 4 relays (2 make, 2 c/o). Needs 24V local supply.

* all prices in EUR ex works (+VAT/MwSt inside Germany)

BITBUS-OEM-Modul

To make the Ethernet transition transparent to the application software, there`s a BAPITCP.dll for Windows® that does the TCP wrapping and communication with the ETH-BIT's BAPI/TCP server - or, to be more precise, with up to 6 servers to fully simulate a local BAPInt.dll. If you rename this BAPITCP.dll to BAPInt.dll, your applications won't even notice the exchange of the transport layer and continue to work over Ethernet as they did through the built-in board. A tool (bapitcpcfg.exe) is provided to assign a specific server hardware IP to a logical board name like "BBUS0" as required by the BAPI protocol.

You got Linux, QNX, iRMX or another operating system? Here's your chance to get on the BITBUS easily: As a stand-alone server ETH-BIT offers you BITBUS access using standard TCP/IP messages. Hence, if you are able to send TCP/IP socket messages from your operating system, you are able to do BITBUS. Please see the BEUG recommendation we implemented on ETH/BIT and our ELZET80 implementation notes.

Under Windows, the BAPI/TCP server on ETH-BIT can be accessed directly via TCP/IP or through the BAPIxx.dll. Find an ETH-BIT in your subnet using the free tool ELZET80 Network Device Discovery.

lässt sich direkt oder über die BAPI.dll von Windows aus ansprechen. Sie finden eine ETH-BIT im eigenen Netz mit dem ELZET80 Network Device Discovery Dienstprogramm.

BITBUS-OEM-Modul

Especially in a slave situation you might want to integrate BITBUS into your own hardware and access it via Ethernet. Two boards available for these applications:  ETH-BITM and ETH-BITS. We suggest ETH-BITM as it allows more options of connector modification, has CMOS-level signals taken out and supports RTS transmit line control for repeater slaves. You still need ETH-BITS if you require the unit to be remote supplied by PoE (Power over Ethernet). ETH-BITM's encapsulated versions are ETH-BITE and ETH-BITF, which might give you an idea of the flexibility of connector arrangement.

Click on the picture to see some detail of the overlayed connector options together with the naming of the header connectors. Signal details can be found under the installation tab of this page.

The firmware is like with the other ETH-BIT variants and can be accessed conveniently through our Windows® drivers. From other operating systems, there's the option of direct TCP/IP access to the BAPI/TCP server task running on ETH-BIT (see BITBUS basics), the access specifications can be found below the "downloads" tab there.

 

BITBUS-OEM-Modul

If you need to remote supply your OEM master or slave using PoE, you have to resort to the slightly less flexible ETH-BITS, which is the module version of ETH-BIT (without RTS repeater signal). Supply is from 5V, plug in the 24V standard supply or the PoE supply. Header connectors can be assembled (instead of the BITBUS and ETH standard connectors) from both sides), even for small quantity orders.

Installation manual for ETH-BIT

Installation manual for ETH-BITR

Installation manual for ETH-BITF

Dimensions and header pin assignments for ETH-BITM OEM module.