:

CONV232/485 and CONV232/422

Serial Data Converters

FEATURES

  • Balanced-mode, long-distance RS-485 and RS-422 communication with no internal installation
  • External power not needed for small networks
  • Nothing to configure; automatically detects baud rate and format
CONV232/485 and CONV232/422 convert between RS-232 communications (as used by the COM1 and COM2 ports standard on most motherboards) and balanced-mode, long distance RS-485 and RS-422 communications. CONV232/485 was designed for use with our REMOTE ACCES line when there is no RS-485 port on your PC, but may also be used in other, similar applications.

CONV232/485 supports two-wire RS-485 communications, which is half-duplex (only one may transmit at a time) but allows up to 32 participants on a "party line" network. CONV232/422 supports four-wire RS-485 and RS-422 communications, which only allows two peer participants (or one master and multiple slaves) but is full-duplex (both peers, or the master and one slave, may talk at the same time.) CONV232/422 can also support two-wire RS-485 if the transmit and receive pins are tied together, but in this configuration it echoes on the RS-232 side.

Internally, TD and RD are converted to balanced lines and the RD line is automatically disabled when data is being transmitted to the RS-485 network. The converters can transmit and receive transparently at whatever speed the data is flowing, up to 460K baud for the CONV232/485 and 230K baud for the CONV232/422. CONV232/485 (and CONV232/422 in a two-wire RS-485 configuration) can support up to 31 other RS-485 devices (with the optional external power). CONV232/422 in a master-slave configuration can support up to 31 slave devices.

The converters plug into your RS-232 port, and all you need to do is hook up the RS-485 wires via a DB9 Male connector. Optional external power is required when communicating with more than two REMOTE ACCES Pods, or over long transmission lines; if external power is not provided, power drawn from the DTR and RTS lines on the RS-232 port is sufficient where the communication cable is short and there are few nodes.

Drivers and Downloads

List of available Downloads: Software Packages, Drivers, Manuals, and other documents


Custom Software

ACCES also offers Custom Software Services for our products. Our prices are unbelievably low, often as inexpensive as free! If you need something tweaked to support your needs, or an entire enterprise application developed from scratch, it is definitely worth your time to inquire with us, first.

Available Datasheets


Further information about available ACCES Software:

Redistributing Windows Drivers
A list of ACCES drivers and the files that compose them under different versions of Windows, so you can easily redistribute ACCES cards and drivers.

Specifications

CONV232/485

  • Optional External Power: When communicating with more than two REMOTE ACCES Pods or over long transmission lines, connect +5.5VDC to +16VDC @ 50 mA to J2 pin 8 with return via J2 pin 5.
  • Data rate: Up to 460.8K baud.
  • Serial format: any.
  • Configurations: RS-232 to two-wire RS-485.
  • Operating Temperature: 0-70°C, added-cost option, -40 to +85°C. Add -XT to part number.

CONV232/422

  • Optional External Power: When communicating with more than two REMOTE ACCES Pods or over long transmission lines, connect +5.5VDC to +16VDC @ 40 mA to J2 pin 8 with return via J2 pin 5.
  • Data rate: Up to 230.4K baud.
  • Serial format: any.
  • Configurations: RS-232 to four-wire RS-485 / RS-422, RS-232 to two-wire RS-485 (with echo on the RS-232 side).
  • Operating Temperature: 0-70°C, added-cost option, -40 to +85°C. Add -XT to part number.

Regulatory Compliance

  • This product is in full compliance with CE requirements.

 
ModelPrice (USD)
CONV232/48549.00
CONV232/42249.00



Acquisition, Control, Communication: Engineering and Systems

olark('api.rules.defineRule', { id: 'delayed_response', description: 'Will send a response to the visitor after an operator doesn't respond.', condition: function(pass) { olark('api.visitor.getDetails', function(details) { var delay = 60 / details.messageCountForThisVisit; if (details.isConversing && details.secondsSinceLastMessageToOperator >= delay && !details.secondsSinceLastMessageToVisitor) { pass(); } }); }, action: function() { olark('api.chat.sendMessageToVisitor', { body: 'Sorry about the delay. We'll get back with you as soon as possible ... but it might be via e-mail, especially if it is currently 2am Pacific.' }); olark('api.chat.sendNotificationToOperator', { body: 'Automated delay message has been sent to visitor.' }); }, perVisitor: true });