USB Connection - Rev 20150923
USB Connection - Rev 20150923
Equipment
23/09/2015 1
Contents
1. Forewords............................................................................................................................................ 3
23/09/2015 2
1. Forewords
As per USB 3.0 specifications, it is not required that the relevant interfaces are compatible with USB
interfaces following USB 1.0 and 1.1 specifications (“It should be noted that USB 3.0 devices are not
required to be backward compatible with USB 1.1 host ports although supporting full-speed and low-speed
modes are allowed”) whilst USB 2.0 native interfaces require backward compatibility to USB 1.x
specifications. Therefore it cannot be assured that every single USB interface is compatible with the USB1.1
standard.
For further references, please refer to the relevant section of usb.org website
(http://www.usb.org/developers/docs/)
SIAE MW ALS Family IDUs provide USB connectivity compliant to the USB 1.1 specifications.
Therefore, from the USB connectivity point of view, the connection with a device trough a USB2.0 native
port shall work.
2. Tools needed
Please note that any of the above mentioned procedures or workaround shall be applied only after the
correct installation of the proper software to connect to the Equipment (SCT – Subnetwork Craft Terminal),
which is distributed under license agreement from SIAE only.
For further reference please refer to the manuals provided together with the SCT SW.
Provided that the IT evolution is quickly going towards USB3.0 compliant interfaces and, therefore, that all
the recent/new laptops are equipped with such type of interfaces, some workarounds can be found to try
to establish the, not granted, connection between a USB1.X compliant device and a USB3.0 compliant
device. Since the direct connection USB3.0-USB1.X is not foreseen by the USB standard, the below listed
workarounds cannot be guaranteed to work for 100% of the cases.
23/09/2015 4
In certain cases the incompatibility lies in the HW interface itself, therefore any operation done at
software/firmware level are worthless.
Provided that i) the USB2.0 standard requires the backwards compatibility between interfaces following
USB1.X specifications and ii) the USB3.0 standard requires the backwards compatibility between interfaces
following USB2.0 specifications, the utilization of a hub with USB2.0 interfaces can be a further
workaround.
Please note that, being the type of integrated circuit used inside the hub itself (even within the same
Producer and with same part number) not under control of the final user, it can happen that same hub
types can have different results in terms of connection.
23/09/2015 5
4. Connect using LAN interface
Using the LAN interface of the equipment is independent from backward compatibilities and offers the
highest bandwidth when high data volumes (e.g. SW upgrade) need to be downloaded. Therefore this
should be the method of choice to connect to the SIAE equipment.
Prerequisite: Knowledge of the IP address and Subnet Mask of the equipment LAN port. Installation of
SIAE SCT. For ALS IDUs, standard IP address when the controller is delivered straight from the factory is
1.0.0.1, Subnet Mask 255.0.0.0).
a) Ethernet Configuration
23/09/2015 6
Configure Your Ethernet adapter with a free IP address and the correct subnet mask so Your PC is
using the same network as the equipment interface.
23/09/2015 7
b) SCT configuration
In the SCT go to Options and set the connection typ to Connect using local area network followed
by selecting Setting… and picking the previously configured IP address.
23/09/2015 8
5. Connect using RS232 (serial) interface
Using the RS232 interface of the equipment is independent from backward compatibilities and no
special information from the controller unit (e.g. IP address) is needed. Related to the other options the
maximum data rate is pretty low therefore this connection should only be used for configuration or to
check the Ethernet configuration.
To connect to the serial RS232 interface a simple null modem cable without handshaking is needed. As
this cable configuration is hardly / not to buy on the market one has to build it by oneself.
Most of the null modem cables available on the market will have all nine pins connected. For the RS232
interface these cables will not work.
No other than pin 2, 3 and 5 must be connected!
Pin-Layout:
PC ALS IDU
Pin 2 Pin 3
Pin 3 Pin 2
Pin 5 Pin 5
23/09/2015 9
b) Check HW installation.
Check that the serial Interface / USB-to-serial converter is properly installed in the device manager.
23/09/2015 10
c) Check HW installation.
Switch to the Modem tab and push Add to create a new modem.
23/09/2015 11
…and set the path to the folder …/sct/DRV on Your computer.
Select the COM port of your serial interface OR Your plugged USB-to-serial converter. Proceed…
23/09/2015 12
Now a new modem named PPP – Direct connection to equipment is available. Choose Properties.
23/09/2015 13
In the Modem tab set the Maximum Port Speed to 38400.
23/09/2015 14
Set Flow Control to None. Switch to the Advanced tab.
Confirm all windows until You are back at the Control Panel.
23/09/2015 15
d) Configure the Remote Access Connection
Check that the Connect using field is set to PPP-Direct connection to equipment.
Verify that three digits are set to the Phone Number. Otherwise type three digits as You like into
the field.
Choose Configure.
23/09/2015 16
Move to the Network tab and deactivate any items except Internet Protocol version 4 (TCP/IPv4).
Select the TCP/IPv4 protocol and choose Properties.
23/09/2015 17
In the SCT go to Options and set the connection typ to Connect using direct serial cable followed by
selecting Setting… and picking the previously configured Modem – PPP – Direct connection to
equipment.
23/09/2015 18
6. Summary: Meeting ZTE – SIAE 23.09.2015 at SIAE GmbH in Düsseldorf
Participants:
Target: SIAE to show a 100% solution to connect to the ALS IDU used in the TEF network
even when the USB interface is not usable for HW compatibility reasons (backward
compatibility of the USB controller inside the notebook) and the local IP of the
Ethernet interface is not known (e.g. after swap of the controller card).
Optional target: The solution to work also on the “Oracle Virtual Box” used at ZTE /
NFS.
Result: During the meeting the connection via the RS232 interface (as described in chapter
5) was successfully tested on all possible notebook types currently in use at ZTE and
NFS. Where available the fixed serial port of the pc was tested and also the
connection with different types of USB-to-serial converters. All variations on every
single machine could be established without any restriction.
There were no additional steps necessary to get the connection running inside the
“Oracle Virtual Box”.
23/09/2015 19