Note: Your user name is not your email address.
Your account is locked out! Please click
here to unlock your account.
Your account is not activated yet. Please check your email and click on the activation link that was sent to you when you registered to our site.
Did not received the activation email? Please click here to contact us.
Login failed, username or password is incorrect.
If you have a GX Series device with an I/O X-Card installed, you can also configure this feature on the I/O X-Card serial port.
Receive payload data over serial;
create and send out packets
Figure 1: TCP and UDP Auto Answer
To configure the AirLink device for TCP/UDP auto answer, sending IP packets, or both:
1. In the ACEmanager, navigate to Serial > Port Configuration. If you are configuring an I/O X-Card, navigate to Serial > I/O X-Card Serial Port.
2. Use Table 3 and the instructions following the table to configure the desired options for this feature.
Table 3: Quick Guide to Configuring IP to Serial with Auto Answer and Serial to IP
To receive packets and send data payload out over serial
To receive data payloads over serial and send out packets
Both (to receive packets - send out data payload AND receive data payload and send out packets)
Startup Mode Default
See Step 3
UDP or TCP
Configure Serial Port
See Step 4
See Step 5
See Step 6
54321 for I/O X-Card
See Step 7
See Step 8
3. Startup Default Mode—When the Startup Mode is set to UDP or TCP, the AirLink device takes any data sent to its serial port from a connected device and encapsulates it into a TCP/IP or UDP/IP packet.
4. Configure Serial Port—Set the baud rate of the serial port on the AirLink device so that it matches the baud rate of the serial port on the connected device. (The default baud rate is 115200 bps.) You can also use this field to set the framing characteristics for the serial port communication on those rare occasions when the default value of 8N1 does not apply.
5. Flow Control—This field can usually be left at the default value (None) as most serial devices use only a three-wire connection (Tx, RX, and Gnd). However, if the serial device uses the RTS and CTS pins on the serial connection to control data flow between the two devices, set this field to Hardware.
6. Device Port—Data received on a TCP/IP or UDP/IP connection to the configured Device Port is sent out the serial port. The default value for the port is:
7. Destination Port—The AirLink device uses the port value specified in this field to determine which port it sends the IP packet containing the data payload to. The AirLink device enters the value in the Destination Port field in the header of the IP packet it creates.
8. Destination Address—The AirLink device uses the IP address specified in this field to determine the IP address to send the packet it creates to. The AirLink device enters this IP address in the header of the IP packet it creates.
9. If you are configuring the AirLink device to:
For Receiving TCP/IP Packets:
For Receiving UDP/IP Packets:
For information on the other parameters, refer to the ALEOS Software Configurations User Guide.
10. Click Apply.
11. Click Reboot (in the upper right of the screen). Once the reboot is complete, this feature is enabled.
If the packet contents are not being sent to the connected device:
1. Try polling the device connected to the AirLink device’s serial port. If you do not receive a response, confirm that the fields described in Table 3 are set correctly.
2. In ACEmanager, navigate to Status > Serial and check the Serial bytes sent field to confirm that packets are reaching the AirLink device from the mobile network and the packet contents are being sent out the AirLink device’s serial port.
Figure 3-3: ACEmanager Status > Serial
When you poll the AirLink device/connected device:
The IP packet has not made it across the mobile network to the AirLink device.
The destination port for the TCP/IP or UDP/IP connection does not match the configured Device Port on the ACEmanager Serial tab.
3. Once you have confirmed that the Serial bytes sent counter is increasing, check the Serial bytes received counter (also on the Status > Serial screen).
4. If you have confirmed that both the Serial bytes sent and Serial bytes received counters are increasing when you send a poll to the connected device, but you are still not receiving the response back on your original sending application, the most common reason is that the incoming packets from the AirLink device to your application are being blocked by a firewall on your network. The firewall may be blocking all traffic except packets destined for particular ports or arriving from particular ports.
Check with your firewall administrator. Ask the administrator to monitor the firewall when you poll the AirLink/connected device to see if any return packets from the AirLink device hit the firewall.