AcceedWiki - User contributions [en]

P588U

2013-03-28T16:32:22Z

Jan Keyling:

P588U card is eight RS232 serial port card.

== Cabling / Connectors ==

Generally you can have R804 cable to work with this UPCI card to support eight DB9 male connector. Or you can use R801 cable to support eight DB25 male connector.

== Options ==

For people need to support RS422 or RS485 interface to replace RS232 interface. They can use P8485U card to support eight RS422/RS485 serial ports in one card. Or they can use R803 cable to connect with RS4232-8 box. Then they can have eight ground isolated RS422/RS485 interface.

For SCO Openserver UNIX user P588U card is one of the cheapest way to add extra eight TTY device connection.

== User ==

For DOS and WIN95/98/Me/2000/NT/XP/2003 user P588U card is one of the cheapest way to add extra eight COM serial port.

== Driver ==

For Linux user P588U card can support RedHat , Slackware, Suse new 2.6.x kernel system.

There are two alternatives for using P588U on Linux systems without installing the supplied Rayon driver. Both methods use Linux standard tty driver (which is normally limited to 4 ports only):

Method A:

1. Modify /boot/grub/menu.lst to add one more boot parameter: 8250.nr_uarts=16

2. Linux systems can have for example ttyS4--ttyS11 on OPe958 card. "dmesg" will show the actual configuration for this card (depending on additional tty ports on the system).

Method B:

1. In /usr/src/linux the kernel sourcecodes can be found . Please run "make menuconfig" to modify the configuration.

2. Device Drivers----> Character devices -----> Serial driver -----> Number of 8250/16550 serial ports ====> In default condition it is 4. Please modify to 16.

3. Now run "make" "make install" to have the modified Linux system in next boot menu.

4. In next boot procedure, you can choose the modified Linux system and find the additional 8 serial ports of OPe958 card. "dmesg" will show the actual configuration for this card (depending on additional tty ports on the system).

== Differences ==

[http://www.acceed.com/p588u P588U] is the universal PCI or 3,3V variant of [http://www.acceed.com/p588 P588]

[[Category:Produkt]]

P588U

2013-03-28T16:32:00Z

Jan Keyling:

P588U card is eight RS232 serial port card.

== Cabling / Connectors ==

Generally you can have R804 cable to work with this UPCI card to support eight DB9 male connector. Or you can use R801 cable to support eight DB25 male connector.

== Options ==

For people need to support RS422 or RS485 interface to replace RS232 interface. They can use P8485U card to support eight RS422/RS485 serial ports in one card. Or they can use R803 cable to connect with RS4232-8 box. Then they can have eight ground isolated RS422/RS485 interface.

For SCO Openserver UNIX user P588U card is one of the cheapest way to add extra eight TTY device connection.

== User ==

For DOS and WIN95/98/Me/2000/NT/XP/2003 user P588U card is one of the cheapest way to add extra eight COM serial port.

== Driver ==

For Linux user P588U card can support RedHat , Slackware, Suse new 2.6.x kernel system.

There are two alternatives for using P588U on Linux systems without installing the supplied Rayon driver. Both methods use Linux standard tty driver (which is normally limited to 4 ports only):

Method A:

1. Modify /boot/grub/menu.lst to add one more boot parameter: 8250.nr_uarts=16
2. Linux systems can have for example ttyS4--ttyS11 on OPe958 card. "dmesg" will show the actual configuration for this card (depending on additional tty ports on the system).

Method B:

1. In /usr/src/linux the kernel sourcecodes can be found . Please run "make menuconfig" to modify the configuration.
2. Device Drivers----> Character devices -----> Serial driver -----> Number of 8250/16550 serial ports ====> In default condition it is 4. Please modify to 16.
3. Now run "make" "make install" to have the modified Linux system in next boot menu.
4. In next boot procedure, you can choose the modified Linux system and find the additional 8 serial ports of OPe958 card. "dmesg" will show the actual configuration for this card (depending on additional tty ports on the system).

== Differences ==

[http://www.acceed.com/p588u P588U] is the universal PCI or 3,3V variant of [http://www.acceed.com/p588 P588]

[[Category:Produkt]]

P588U

2013-03-28T16:31:46Z

Jan Keyling: /* Driver */

P588U card is eight RS232 serial port card.

== Cabling / Connectors ==

Generally you can have R804 cable to work with this UPCI card to support eight DB9 male connector. Or you can use R801 cable to support eight DB25 male connector.

== Options ==

For people need to support RS422 or RS485 interface to replace RS232 interface. They can use P8485U card to support eight RS422/RS485 serial ports in one card. Or they can use R803 cable to connect with RS4232-8 box. Then they can have eight ground isolated RS422/RS485 interface.

For SCO Openserver UNIX user P588U card is one of the cheapest way to add extra eight TTY device connection.

== User ==

For DOS and WIN95/98/Me/2000/NT/XP/2003 user P588U card is one of the cheapest way to add extra eight COM serial port.

== Driver ==

For Linux user P588U card can support RedHat , Slackware, Suse new 2.6.x kernel system.

There are two alternatives for using P588U on Linux systems without installing the supplied Rayon driver. Both methods use Linux standard tty driver (which is normally limited to 4 ports only):

Method A:

1. Modify /boot/grub/menu.lst to add one more boot parameter: 8250.nr_uarts=16
2. Linux systems can have for example ttyS4--ttyS11 on OPe958 card. "dmesg" will show the actual configuration for this card (depending on additional tty ports on the system).

Method B:

1. In /usr/src/linux the kernel sourcecodes can be found . Please run "make menuconfig" to modify the configuration.
2. Device Drivers----> Character devices -----> Serial driver -----> Number of 8250/16550 serial ports ====> In default condition it is 4. Please modify to 16.
3. Now run "make" "make install" to have the modified Linux system in next boot menu.

5. In next boot procedure, you can choose the modified Linux system and find the additional 8 serial ports of OPe958 card. "dmesg" will show the actual configuration for this card (depending on additional tty ports on the system).

== Differences ==

[http://www.acceed.com/p588u P588U] is the universal PCI or 3,3V variant of [http://www.acceed.com/p588 P588]

[[Category:Produkt]]

Modbus

2011-11-22T11:02:13Z

Jan Keyling:

Modbus description

== General hints ==

* Bla.

[[Category:Produkt|Modbus]]

Matrix-500

2011-01-25T11:58:14Z

Jan Keyling:

Matrix-500 is an embedded computer with 200MHz ARM9 RISC CPU manufactured by [http:///www.Artila.com Artila]. There are 4 high speed RS232 ports (1 port RS232/422/485 selectable), 2 USB host controller ports, 1 USB device controller port, 16 general purpose [http://en.wikipedia.org/wiki/Input/output digital IO port] (inside case connector). Matrix-500 uses [http://www.arm.linux.org.uk/ ARM-Linux], so it behaves like a standard Linux machine regarding the handling of USB, serial and Ethernet ports. Users can upload their own programs in order to customize Matrix-500 for their special purpose. SDK for both Linux and Windows host PCs is included.

Note that other Matrix-5xx products have different features. For example, the USB device controller is only available on the Matrix-500.

== Console Port ==

Matrix 500's console is disable as factory default setting. To enable the
console port, please find the information attached. Because the console
port (ttyS0) share the same pins with serial port P3 (ttyS3), user need to
prepare a special cable to connect ttyS0 via the RJ45 connector of Port 3.
To trigger the console port function, user need to press "@@@@" (Artila doc says "$$$$")
continuously right after power up and after the screen show "Starting Matrix 500......."
Remember to disable the console port before leaving the Loader program.
Regarding the special cable, it is different from the RJ45 to DB9 cable used on Port 1 to Port 4 ([http://www.acceed.info/manuals/artila/Matrix-500%20Enable%20Serial%20Console.pdf Details])

For iPAC-50xx series, which have a dedicated Console port, simply connect the provided CBL-F10M9-20 cable with the onboard 10pin Console header. Then use a standard PC null modem cable for connecting your host PCs serial port with the DB9 plug of CBL-F10M9-20. Open you host PCs COM port using your preferred terminal software (e.g. Hyperterminal). The connection settings are 115200bd, 8-N-1, ANSI mode. Restart iPAC-50xx and you will be able to log on to the device using Hyperterminal. This is especially helpful if you forgot the device´s IP address.

== Protocols ==

* SSL ([http://en.wikipedia.org/wiki/Transport_Layer_Security Secure Socket Layer])
* SSH ([http://en.wikipedia.org/wiki/Secure_Shell Secure Shell])
* TelNet ([http://en.wikipedia.org/wiki/TELNET TelNet]) (TELetype NETwork)
* and more
== USB Modem ==

USB Modem Support

USB modems (for plain old telephone service, ISDN or cable) are supposed to conform to the Communication Device Class (CDC) specification <http://www.usb.org/developers/data/devclass/usbcdc11.pdf>, and usually to the Abstract Control Model (ACM) sub-class. If your modem doesn't comply with the specification, it will not work with this driver.

You need to select the *USB Modem (CDC ACM) support* kernel option. If you build as modules, you need to install the acm.o option.

You need to set up the device node entries for the various modems. You can use up to 32 modems with this driver. Use the following commands to set up the first four:

*mknod /dev/usb/ttyACM0 c 166 0
*mknod /dev/usb/ttyACM1 c 166 1
*mknod /dev/usb/ttyACM2 c 166 2
*mknod /dev/usb/ttyACM3 c 166 3

You should now be able to use a terminal emulator program to attach to this device and connect to your modem or other terminal device.

== SD Card Slot ==

Matrix-500's internal SD card slot meets SD 1.0 standard. This means SD cards up to 2GB are supported. Caution: SDHC cards will not work in Matrix-500.

== WLAN ==

Please use "dmesg" to check if the kernel detect the wireless. If kernel detect the usb wireless lan. You can skip the "modprob command" just type
* ifconfig wlan0 up
* iwconfig wlan0 essid XXXX key YYYY mode MMMM

(where XXXX is the network name YYYY is the hardware key MMMM is managed for infrastructure mode and ad-hoc for ad-hoc mode)

To configure IP address
* dhcpcd wlan0 & ("&" means run in the background)
or
* ifconfig wlan0 xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx

New driver for Ralink RT2571 is available in Artila CD\Matrix 500\Wifi\rt73.ko

copy rt73.ko to Matrix 500\disk
cd \disk
insmod rt73.ko

to insert the driver module to Matrix 500

Artila has drivers for WLAN sticks with Ralink 2500/2501 chipsets. Ralink provides a list of these products made by different companies at http://ralink.rapla.net/

== Bluetooth ==

For Bluetooth stick, Artila provides drivers for Broadcom Blutonium (BCM2033) and Tektronix BPA 100/105 (Digianswer)

== Tools ==

* SDK for download [http://www.acceed.info/product.phtml?matrix-500-16 SDK]
* The ARM Linux Project : [http://www.arm.linux.org.uk/ Linux for all ARM based machines]

== Connectors ==

* [http://www.acceed.com/manuals/artila/Matrix%20500%20Internal%20Connector.pdf Connector layout]
* [http://www.acceed.com/manuals/artila/Matrix%20500%20Quick%20Installation%20Guide.pdf Board layout]
* A mini-USB connector for the USB Device Controller (UDC) is on the right side of the housing (not shown on above documents)

== Options ==

Standard [http://de.wikipedia.org/wiki/Flash-Speicher flash memory] option is with 16MB flash memory. On request 8MB or 32MB and 64MB are available.

== Watchdog ==

Matrix 500 has a watchdog device and it works as a standard watchdog device under Linux. The default setting of the watchdog timer is 5 seconds. Kernel will reset the watchdog timer before it time out. If for some unexpected reason, kernel fails to reset the watchdog timer, Matrix 500 will reset itself and system will reboot again. We do not recommend user to use watchdog timer in his application. To implement a software Watchdog process is a better way for application level watchdog

== Application Stories ==

Matrix-500 is a standalone embedded computer. Typical applications are in data collection and preparation in POS ([http://de.wikipedia.org/wiki/POS-Terminal Point Of Sale]), at a gas station to prepare and transmit accounting data or in advertisement systems with displays.

== Tech Spec ==

* 2*USB, 3*RS232, 1*RS232/422/485, 1*10/100 Ethernet
* Matrix 500 has a MMU. It is a MMU ready Linux Kernel and fork() is ok. It is not necessary to specify stack size at compile time.
* Matrix 500 uses Standard Linux with MMU Kernel version 2.6.14
* Root Filesystem uses ETX2 format. The Root Filesystem is extract and built on the RAMDISK of Matrix 500 during system startup. The system image uses about 4MB space of the Flash Memory
* User Flash disk uses JFFS2 format and space size is Flash memory size minus 4MB of image(e.g. 16MB Flash - 4MB Image = 12 MB [11764KB ] user flash disk )
* USB WLAN Adaptor Support List (RT2570): [http://rt2x00.serialmonkey.com/wiki/index.php?title=Hardware RT2570 Hardware]
* Boot from USB Disk and SD Card are not available at this moment. We will consider it in the future.

== Firmware Upgrade ==
In case you want to upgrade firmware: use an USB disk and load all files to be upgraded on it. Then
# copy the files "matrix500v2.alf", "m500kv2" and "m500rv2" to a USB flash disk
# Insert the USB disk to Matrix 500
# mount USB disk by " mount /mnt/sda1"
# change to the /mnt/sda1 directory
# type "update m500kv2"
# type "update m500rv2"
# type "update matrix500v2.alf"
# Reboot the Matrix 500

== Source ==

The new link is [ftp://ftp:ftp@ftp.artila.com/Matrix5xx ftp.artila.com/Matrix5xx] (login: ftp, password: ftp).

Python is available on request.

== Flash Recovery ==

1) Recovery from wrong boot image

Please use serial console and under loader screen ( type @@@@ right after reboot to enter loader screen), select format option (H) to format the user disk. After format, reset the system. Doing this will reload the factory setting at next system boot. But it will take about two minute for system to rebuild its /etc/rc.

2) Recovery from corrupt flash

After download newest firmware please perform following steps:

Find the flash corrupted Matrix 500
# Open metal case of Matrix 500
# Find JP1 near COM4 port connector
# Place JP1 to 1-2 position
# Connect the console cable on Port 3 of Matrix 500
# Open hyper terminal software and serial port setting as 115200, n,8,1
# Power on Matrix 500 again (or push reset button)
# You will see "CCCCC" pop up on the hyper terminal from console port
# upload file "loader.bin" with Xmodem protocol
# once done, "CCC" will show up again then
# upload "m500v2.bin" with xmodem
# once complete, loader screen will show up. Type "L" key to upload "matrix500v2.alf " with Kermit protocol
# once done, type "S" to upload "m500kv2" with Kermit
# once done, type "T" to upload "m500rv2" with Kermit

After all these steps are done, place the JP1 to 2-3 position and then reset Matrix 500. The new loader and kernel will boot up and you can perform the test again.

== Why to choose ARM9 with MMU ==

MMU (Memory Management Unit) is important unit for CPU which is operated on multi-task Operating System and software. If the CPU does not have MMU, it have to use uCLinux which is a special version Embedded Linux OS which is designed for non-MMU CPU. Special care must be taken into consideration if you want to port x86 Linux software to a non-MMU RISC-based Linux plaftform. To avoid this compatibility issue, it is better to choose ARM9 RISC with MMU

[[Category:Produkt]]

APortxxx

2010-11-03T11:05:19Z

Jan Keyling: /* IP Module In Serial Tunnel */

APortxxx are serial device servers for serial-over-ethernet communication. The 3-digit code "xxx" lists the number of RS232 - isolated RS232 - isolated RS422/485 ports. For example, APort400 has 4 RS232 ports, APort020 has 2 ground isolated RS232 ports and APort004 has four ground isolated RS422/485 ports.

== General hints ==

* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of APortxxx is 192.168.1.254 - so the host PC should have for example 192.168.1.1 or any other IP in the 192.168.1 subnet. This prevents problems due to network connectivity issues. When you have forgotten APortxxx´s IP, you can search it using aport_ap.exe management tool.
* APortxxx also features complete web interface for all settings - simply type in APortxxx`s IP address in your browser (192.168.1.254 on default).

== APortxxx special features ==

* Each port of a single APortxxx device can be assigned to an arbitrary host PC (Linux or Windows based) - e.g., Port 1 can be assigned to a Linux server as a remote TTY port, and Port 2 can be assigned to a Windows-based workstation as a virtual COM port. Basically, the multi-port models of APortxxx behave like independent single port serial device servers sharing one IP address.

== IP Module In Serial Tunnel ==

* In paired mode (or tunnel mode) you will need 2 APortxxx
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* Paired mode can be used for serial-over-ethernet transmission without installing a driver on the host PC.

[[Category:Produkt|APortxxx]]

APortxxx

2010-11-03T11:04:41Z

Jan Keyling:

APortxxx are serial device servers for serial-over-ethernet communication. The 3-digit code "xxx" lists the number of RS232 - isolated RS232 - isolated RS422/485 ports. For example, APort400 has 4 RS232 ports, APort020 has 2 ground isolated RS232 ports and APort004 has four ground isolated RS422/485 ports.

== General hints ==

* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of APortxxx is 192.168.1.254 - so the host PC should have for example 192.168.1.1 or any other IP in the 192.168.1 subnet. This prevents problems due to network connectivity issues. When you have forgotten APortxxx´s IP, you can search it using aport_ap.exe management tool.
* APortxxx also features complete web interface for all settings - simply type in APortxxx`s IP address in your browser (192.168.1.254 on default).

== APortxxx special features ==

* Each port of a single APortxxx device can be assigned to an arbitrary host PC (Linux or Windows based) - e.g., Port 1 can be assigned to a Linux server as a remote TTY port, and Port 2 can be assigned to a Windows-based workstation as a virtual COM port. Basically, the multi-port models of APortxxx behave like independent single port serial device servers sharing one IP address.

== IP Module In Serial Tunnel ==

* In paired mode (or tunnel mode) you will need 2 IDS-50xx
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* Paired mode can be used for serial-over-ethernet transmission without installing a driver on the host PC.

[[Category:Produkt|APortxxx]]

IDS-50XX

2010-07-01T12:58:13Z

Jan Keyling: IDS-50XX moved to IDS-50xx

#REDIRECT [[IDS-50xx]]

IDS-50xx

2010-07-01T12:58:13Z

Jan Keyling: IDS-50XX moved to IDS-50xx

IDS-50xx are serial device servers for either serial-over-ethernet and/or serial-over-WLAN communication (IDS-50xx-WG models). Several models (IDS-50x2) feature dual LAN ports for ethernet redundancy (recovery time <10ms). Also all models share redundant dual power inputs (12-48VDC). The supplied DS-Tools setup & administration software allows complete configuration of devices, and includes Wizard function for easy step-by-step setup of all connected devices.

== General hints ==

* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of IDS-50xx is 192.168.10.2 - so the host PC should have for example 192.168.10.1 or any other IP in the 192.168.10 subnet. Otherwise, DS-Tools might not be able to connect to the device. You may change the device´s IP address via DS-Tools later.

== IDS-50xx-WG (WLAN models) hints ==

* If you want IDS-50xx-WG to connect to your host PC (or another IDS-50xx-WG in tunnel mode), make sure no ethernet cable is connected to IDS-50xx-WG´s LAN port. If IDS-50xx-WG is connected via LAN, it will automatically disable WLAN to avoid dual connection. So, WLAN will only work when there is no connection to a wire-based LAN available.
* The SSID of your WLAN should not contain a "space" - i.e., you may call it for example "IDS_WLAN", but "IDS WLAN" will not work.

== IP Module In Serial Tunnel ==

* In paired mode (or tunnel mode) you will need 2 IDS-50xx
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* DS-Tools (included) allows easy tunnel mode setup via step-by-step Wizard
* Tunnel mode works either via LAN or WLAN connection (IDS-50xx-WG models)

[[Category:Produkt|IDS-50xx]]

IDS-50xx

2010-07-01T12:58:03Z

Jan Keyling:

IDS-50xx

2010-06-30T12:51:50Z

Jan Keyling:

IDS-50XX are serial device servers for either serial-over-ethernet and/or serial-over-WLAN communication (IDS-50XX-WG models). Several models (IDS-50X2) feature dual LAN ports for ethernet redundancy (recovery time <10ms). Also all models share redundant dual power inputs (12-48VDC). The supplied DS-Tools setup & administration software allows complete configuration of devices, and includes Wizard function for easy step-by-step setup of all connected devices.

== General hints ==

* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of IDS-50XX is 192.168.10.2 - so the host PC should have for example 192.168.10.1 or any other IP in the 192.168.10 subnet. Otherwise, DS-Tools might not be able to connect to the device. You may change the device´s IP address via DS-Tools later.

== IDS-50XX-WG (WLAN models) hints ==

* If you want IDS-50XX-WG to connect to your host PC (or another IDS-50XX-WG in tunnel mode), make sure no ethernet cable is connected to IDS-50XX-WG´s LAN port. If IDS-50XX-WG is connected via LAN, it will automatically disable WLAN to avoid dual connection. So, WLAN will only work when there is no connection to a wire-based LAN available.
* The SSID of your WLAN should not contain a "space" - i.e., you may call it for example "IDS_WLAN", but "IDS WLAN" will not work.

== IP Module In Serial Tunnel ==

* In paired mode (or tunnel mode) you will need 2 IDS-50XX
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* DS-Tools (included) allows easy tunnel mode setup via step-by-step Wizard
* Tunnel mode works either via LAN or WLAN connection (IDS-50XX-WG models)

[[Category:Produkt|IDS-50XX]]

IDS-50xx

2010-06-30T12:51:11Z

Jan Keyling:

IDS-50XX are serial device servers for either serial-over-ethernet and/or serial-over-WLAN communication (IDS-50XX-WG models). Several models (IDS-50X2) feature dual LAN ports for ethernet redundancy (recovery time <10ms). Also all models share redundant dual power inputs (12-48VDC). The supplied DS-Tools setup & administration software allows complete configuration of devices, and includes Wizard function for easy step-by-step setup of all connected devices.

== General hints ==
* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of IDS-50XX is 192.168.10.2 - so the host PC should have for example 192.168.10.1 or any other IP in the 192.168.10 subnet. Otherwise, DS-Tools might not be able to connect to the device. You may change the device´s IP address via DS-Tools later.

== IDS-50XX-WG (WLAN models) hints ==
* If you want IDS-50XX-WG to connect to your host PC (or another IDS-50XX-WG in tunnel mode), make sure no ethernet cable is connected to IDS-50XX-WG´s LAN port. If IDS-50XX-WG is connected via LAN, it will automatically disable WLAN to avoid dual connection. So, WLAN will only work when there is no connection to a wire-based LAN available.
* The SSID of your WLAN should not contain a "space" - i.e., you may call it for example "IDS_WLAN", but "IDS WLAN" will not work.

== IP Module In Serial Tunnel ==
* In paired mode (or tunnel mode) you will need 2 IDS-50XX
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* DS-Tools (included) allows easy tunnel mode setup via step-by-step Wizard
* Tunnel mode works either via LAN or WLAN connection (IDS-50XX-WG models)

[[Category:Produkt|IDS-50XX]]

IDS-50xx

2010-06-30T12:19:02Z

Jan Keyling:

== IDS-50XX ==
IDS-50XX are serial device servers for either serial-over-ethernet and/or serial-over-WLAN communication (IDS-50XX-WG models). Several models (IDS-50X2) feature dual LAN ports for ethernet redundancy (recovery time <10ms). Also all models share redundant dual power inputs (12-48VDC). The supplied DS-Tools setup & administration software allows complete configuration of devices, and includes Wizard function for easy step-by-step setup of all connected devices.

== General hints ==
* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of IDS-50XX is 192.168.10.2 - so the host PC should have for example 192.168.10.1 or any other IP in the 192.168.10 subnet. Otherwise, DS-Tools might not be able to connect to the device. You may change the device´s IP address via DS-Tools later.

== IDS-50XX-WG (WLAN models) hints ==
* If you want IDS-50XX-WG to connect to your host PC (or another IDS-50XX-WG in tunnel mode), make sure no ethernet cable is connected to IDS-50XX-WG´s LAN port. If IDS-50XX-WG is connected via LAN, it will automatically disable WLAN to avoid dual connection. So, WLAN will only work when there is no connection to a wire-based LAN available.
* The SSID of your WLAN should not contain a "space" - i.e., you may call it for example "IDS_WLAN", but "IDS WLAN" will not work.

== IP Module In Serial Tunnel ==
* In paired mode (or tunnel mode) you will need 2 IDS-50XX
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* DS-Tools (included) allows easy tunnel mode setup via step-by-step Wizard
* Tunnel mode works either via LAN or WLAN connection (IDS-50XX-WG models)

[[Category:Produkt|IDS-50XX]]

IDS-50xx

2010-06-30T12:16:21Z

Jan Keyling:

== IDS-50XX ==
IDS-50XX are serial device servers for either serial-over-ethernet and/or serial-over-WLAN communication (IDS-50XX-WG models). Several models (IDS-50X2) feature dual LAN ports for ethernet redundancy (recovery time <10ms). Also all models share redundant dual power inputs (12-48VDC). The supplied DS-Tools setup & administration software allows complete configuration of devices, and includes Wizard function for easy step-by-step setup of all connected devices.

== General hints ==
* When connecting the modules for the first time with the host PC, make sure both are in the same subnet. The default IP of IDS-50XX is 192.168.10.2 - so the host PC should have for example 192.168.10.1 or any other IP in the 192.168.10 subnet. Otherwise, DS-Tools might not be able to connect to the device. You may change the device´s IP address via DS-Tools later.

== IDS-50XX-WG (WLAN models) hints ==
* If you want IDS-50XX-WG to connect to your host PC (or another IDS-50XX-WG in tunnel mode), make sure no ethernet cable is connected to IDS-50XX-WG´s LAN port. If IDS-50XX-WG is connected via LAN, it will automatically disable WLAN to avoid dual connection. So, WLAN will only work when there is no connection to a wire-based LAN available.

== IP Module In Serial Tunnel ==
* In paired mode (or tunnel mode) you will need 2 IDS-50XX
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* DS-Tools (included) allows easy tunnel mode setup via step-by-step Wizard
* Tunnel mode works either via LAN or WLAN connection (IDS-50XX-WG models)

[[Category:Produkt|IDS-50XX]]

IP101

2010-03-25T10:06:48Z

Jan Keyling:

== IP10x / APort-31x ==
IP10x/APort31x series are easy to use Serial over Ethernet modules. Every module features one 10/100 Ethernet port and 1 to 4 RS232/422/485 ports (DIP-switch selectable). IP101 and APort-311 have one serial port, IP102/Aport-312 2 ports and IP104 has 4 ports.

== IP Module In Serial Tunnel ==
* In paired mode (or tunnel mode) you will need 2 IP10x/APort31x
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* For make safe pairing we need to use fixed IP addresses

== RoHS conformity changes ==
The hardware for old IP101 and new IP101 is same architecture. But there are some modification in part to meet RoHS. The major different is in power adaptor. So it is no difference in firmware.

== Firmware ==
Please keep in mind that ver1.5 and ver1.8 firmware is fully different.
If customer could use ver1.5 firmware, then we don't suggest to upgrade.
The upgrade procedure is very complex. Please read the PDF file in
attached file carefully. There are two steps to upgrade the firmware.
* step 1===> to upgrade ver1.5 to middle version firmware.
* step 2===> to upgrade middle version to ver1.8

Please use one clean environment (just one PC and one IP101 in LAN connection) to do
upgrade procedure.

[[Category:Produkt|Ip101]]

Matrix-500

2010-03-23T16:00:57Z

Jan Keyling: /* SD card slot */

Matrix-500 is an embedded computer with 200MHz ARM9 RISC CPU manufactured by [http:///www.Artila.com Artila]. There are 4 high speed RS232 ports (1 port RS232/422/485 selectable), 2 USB host controller ports, 1 USB device controller port, 16 general purpose [http://en.wikipedia.org/wiki/Input/output digital IO port] (inside case connector). Matrix-500 uses [http://www.arm.linux.org.uk/ ARM-Linux], so it behaves like a standard Linux machine regarding the handling of USB, serial and Ethernet ports. Users can upload their own programs in order to customize Matrix-500 for their special purpose. SDK for both Linux and Windows host PCs is included.

Note that other Matrix-5xx products have different features. For example, the USB device controller is only available on the Matrix-500.

== Console Port ==

Matrix 500's console is disable as factory default setting. To enable the
console port, please find the information attached. Because the console
port (ttyS0) share the same pins with serial port P3 (ttyS3), user need to
prepare a special cable to connect ttyS0 via the RJ45 connector of Port 3.
To trigger the console port function, user need to press "@@@@" (Artila doc says "$$$$")
continuously right after power up and after the screen show "Starting Matrix 500......."
Remember to disable the console port before leaving the Loader program.

Regarding the special cable, it is different from the RJ45 to DB9 cable used on Port 1 to Port 4 ([http://www.acceed.info/manuals/artila/Matrix-500%20Enable%20Serial%20Console.pdf Details])

== Protocols ==

* SSL ([http://en.wikipedia.org/wiki/Transport_Layer_Security Secure Socket Layer])
* SSH ([http://en.wikipedia.org/wiki/Secure_Shell Secure Shell])
* TelNet ([http://en.wikipedia.org/wiki/TELNET TelNet]) (TELetype NETwork)
* and more
== USB Modem ==

USB Modem Support

USB modems (for plain old telephone service, ISDN or cable) are supposed to conform to the Communication Device Class (CDC) specification <http://www.usb.org/developers/data/devclass/usbcdc11.pdf>, and usually to the Abstract Control Model (ACM) sub-class. If your modem doesn't comply with the specification, it will not work with this driver.

You need to select the *USB Modem (CDC ACM) support* kernel option. If you build as modules, you need to install the acm.o option.

You need to set up the device node entries for the various modems. You can use up to 32 modems with this driver. Use the following commands to set up the first four:

*mknod /dev/usb/ttyACM0 c 166 0
*mknod /dev/usb/ttyACM1 c 166 1
*mknod /dev/usb/ttyACM2 c 166 2
*mknod /dev/usb/ttyACM3 c 166 3

You should now be able to use a terminal emulator program to attach to this device and connect to your modem or other terminal device.

== SD Card Slot ==

Matrix-500's internal SD card slot meets SD 1.0 standard. This means SD cards up to 2GB are supported. Caution: SDHC cards will not work in Matrix-500.

== WLAN ==

Please use "dmesg" to check if the kernel detect the wireless. If kernel detect the usb wireless lan. You can skip the "modprob command" just type
* ifconfig wlan0 up
* iwconfig wlan0 essid XXXX key YYYY mode MMMM

(where XXXX is the network name YYYY is the hardware key MMMM is managed for infrastructure mode and ad-hoc for ad-hoc mode)

To configure IP address
* dhcpcd wlan0 & ("&" means run in the background)
or
* ifconfig wlan0 xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx

New driver for Ralink RT2571 is available in Artila CD\Matrix 500\Wifi\rt73.ko

copy rt73.ko to Matrix 500\disk
cd \disk
insmod rt73.ko

to insert the driver module to Matrix 500

Artila has drivers for WLAN sticks with Ralink 2500/2501 chipsets. Ralink provides a list of these products made by different companies at http://ralink.rapla.net/

== Bluetooth ==

For Bluetooth stick, Artila provides drivers for Broadcom Blutonium (BCM2033) and Tektronix BPA 100/105 (Digianswer)

== Tools ==

* SDK for download [http://www.acceed.info/product.phtml?matrix-500-16 SDK]
* The ARM Linux Project : [http://www.arm.linux.org.uk/ Linux for all ARM based machines]

== Connectors ==

* [http://www.acceed.com/manuals/artila/Matrix%20500%20Internal%20Connector.pdf Connector layout]
* [http://www.acceed.com/manuals/artila/Matrix%20500%20Quick%20Installation%20Guide.pdf Board layout]
* A mini-USB connector for the USB Device Controller (UDC) is on the right side of the housing (not shown on above documents)

== Options ==

Standard [http://de.wikipedia.org/wiki/Flash-Speicher flash memory] option is with 16MB flash memory. On request 8MB or 32MB and 64MB are available.

== Watchdog ==

Matrix 500 has a watchdog device and it works as a standard watchdog device under Linux. The default setting of the watchdog timer is 5 seconds. Kernel will reset the watchdog timer before it time out. If for some unexpected reason, kernel fails to reset the watchdog timer, Matrix 500 will reset itself and system will reboot again. We do not recommend user to use watchdog timer in his application. To implement a software Watchdog process is a better way for application level watchdog

== Application Stories ==

Matrix-500 is a standalone embedded computer. Typical applications are in data collection and preparation in POS ([http://de.wikipedia.org/wiki/POS-Terminal Point Of Sale]), at a gas station to prepare and transmit accounting data or in advertisement systems with displays.

== Tech Spec ==

* 2*USB, 3*RS232, 1*RS232/422/485, 1*10/100 Ethernet
* Matrix 500 has a MMU. It is a MMU ready Linux Kernel and fork() is ok. It is not necessary to specify stack size at compile time.
* Matrix 500 uses Standard Linux with MMU Kernel version 2.6.14
* Root Filesystem uses ETX2 format. The Root Filesystem is extract and built on the RAMDISK of Matrix 500 during system startup. The system image uses about 4MB space of the Flash Memory
* User Flash disk uses JFFS2 format and space size is Flash memory size minus 4MB of image(e.g. 16MB Flash - 4MB Image = 12 MB [11764KB ] user flash disk )
* USB WLAN Adaptor Support List (RT2570): [http://rt2x00.serialmonkey.com/wiki/index.php?title=Hardware RT2570 Hardware]
* Boot from USB Disk and SD Card are not available at this moment. We will consider it in the future.

== Firmware Upgrade ==
In case you want to upgrade firmware: use an USB disk and load all files to be upgraded on it. Then
# copy the files "matrix500v2.alf", "m500kv2" and "m500rv2" to a USB flash disk
# Insert the USB disk to Matrix 500
# mount USB disk by " mount /mnt/sda1"
# change to the /mnt/sda1 directory
# type "update m500kv2"
# type "update m500rv2"
# type "update matrix500v2.alf"
# Reboot the Matrix 500

== Source ==

The new link is [ftp://ftp:ftp@ftp.artila.com/Matrix5xx ftp.artila.com/Matrix5xx] (login: ftp, password: ftp).

Python is available on request.

== Flash Recovery ==

1) Recovery from wrong boot image

Please use serial console and under loader screen ( type @@@@ right after reboot to enter loader screen), select format option (H) to format the user disk. After format, reset the system. Doing this will reload the factory setting at next system boot. But it will take about two minute for system to rebuild its /etc/rc.

2) Recovery from corrupt flash

After download newest firmware please perform following steps:

Find the flash corrupted Matrix 500
# Open metal case of Matrix 500
# Find JP1 near COM4 port connector
# Place JP1 to 1-2 position
# Connect the console cable on Port 3 of Matrix 500
# Open hyper terminal software and serial port setting as 115200, n,8,1
# Power on Matrix 500 again (or push reset button)
# You will see "CCCCC" pop up on the hyper terminal from console port
# upload file "loader.bin" with Xmodem protocol
# once done, "CCC" will show up again then
# upload "m500v2.bin" with xmodem
# once complete, loader screen will show up. Type "L" key to upload "matrix500v2.alf " with Kermit protocol
# once done, type "S" to upload "m500kv2" with Kermit
# once done, type "T" to upload "m500rv2" with Kermit

After all these steps are done, place the JP1 to 2-3 position and then reset Matrix 500. The new loader and kernel will boot up and you can perform the test again.

== Why to choose ARM9 with MMU ==

MMU (Memory Management Unit) is important unit for CPU which is operated on multi-task Operating System and software. If the CPU does not have MMU, it have to use uCLinux which is a special version Embedded Linux OS which is designed for non-MMU CPU. Special care must be taken into consideration if you want to port x86 Linux software to a non-MMU RISC-based Linux plaftform. To avoid this compatibility issue, it is better to choose ARM9 RISC with MMU

[[Category:Produkt]]

Matrix-500

2010-03-23T16:00:14Z

Jan Keyling:

Matrix-500 is an embedded computer with 200MHz ARM9 RISC CPU manufactured by [http:///www.Artila.com Artila]. There are 4 high speed RS232 ports (1 port RS232/422/485 selectable), 2 USB host controller ports, 1 USB device controller port, 16 general purpose [http://en.wikipedia.org/wiki/Input/output digital IO port] (inside case connector). Matrix-500 uses [http://www.arm.linux.org.uk/ ARM-Linux], so it behaves like a standard Linux machine regarding the handling of USB, serial and Ethernet ports. Users can upload their own programs in order to customize Matrix-500 for their special purpose. SDK for both Linux and Windows host PCs is included.

Note that other Matrix-5xx products have different features. For example, the USB device controller is only available on the Matrix-500.

== Console Port ==

Matrix 500's console is disable as factory default setting. To enable the
console port, please find the information attached. Because the console
port (ttyS0) share the same pins with serial port P3 (ttyS3), user need to
prepare a special cable to connect ttyS0 via the RJ45 connector of Port 3.
To trigger the console port function, user need to press "@@@@" (Artila doc says "$$$$")
continuously right after power up and after the screen show "Starting Matrix 500......."
Remember to disable the console port before leaving the Loader program.

Regarding the special cable, it is different from the RJ45 to DB9 cable used on Port 1 to Port 4 ([http://www.acceed.info/manuals/artila/Matrix-500%20Enable%20Serial%20Console.pdf Details])

== Protocols ==

* SSL ([http://en.wikipedia.org/wiki/Transport_Layer_Security Secure Socket Layer])
* SSH ([http://en.wikipedia.org/wiki/Secure_Shell Secure Shell])
* TelNet ([http://en.wikipedia.org/wiki/TELNET TelNet]) (TELetype NETwork)
* and more
== USB Modem ==

USB Modem Support

USB modems (for plain old telephone service, ISDN or cable) are supposed to conform to the Communication Device Class (CDC) specification <http://www.usb.org/developers/data/devclass/usbcdc11.pdf>, and usually to the Abstract Control Model (ACM) sub-class. If your modem doesn't comply with the specification, it will not work with this driver.

You need to select the *USB Modem (CDC ACM) support* kernel option. If you build as modules, you need to install the acm.o option.

You need to set up the device node entries for the various modems. You can use up to 32 modems with this driver. Use the following commands to set up the first four:

*mknod /dev/usb/ttyACM0 c 166 0
*mknod /dev/usb/ttyACM1 c 166 1
*mknod /dev/usb/ttyACM2 c 166 2
*mknod /dev/usb/ttyACM3 c 166 3

You should now be able to use a terminal emulator program to attach to this device and connect to your modem or other terminal device.

== SD card slot ==

Matrix-500 meets SD 1.0 standard. This means SD cards up to 2GB are supported. Caution: SDHC cards will not work in Matrix-500.

== WLAN ==

Please use "dmesg" to check if the kernel detect the wireless. If kernel detect the usb wireless lan. You can skip the "modprob command" just type
* ifconfig wlan0 up
* iwconfig wlan0 essid XXXX key YYYY mode MMMM

(where XXXX is the network name YYYY is the hardware key MMMM is managed for infrastructure mode and ad-hoc for ad-hoc mode)

To configure IP address
* dhcpcd wlan0 & ("&" means run in the background)
or
* ifconfig wlan0 xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx

New driver for Ralink RT2571 is available in Artila CD\Matrix 500\Wifi\rt73.ko

copy rt73.ko to Matrix 500\disk
cd \disk
insmod rt73.ko

to insert the driver module to Matrix 500

Artila has drivers for WLAN sticks with Ralink 2500/2501 chipsets. Ralink provides a list of these products made by different companies at http://ralink.rapla.net/

== Bluetooth ==

For Bluetooth stick, Artila provides drivers for Broadcom Blutonium (BCM2033) and Tektronix BPA 100/105 (Digianswer)

== Tools ==

* SDK for download [http://www.acceed.info/product.phtml?matrix-500-16 SDK]
* The ARM Linux Project : [http://www.arm.linux.org.uk/ Linux for all ARM based machines]

== Connectors ==

* [http://www.acceed.com/manuals/artila/Matrix%20500%20Internal%20Connector.pdf Connector layout]
* [http://www.acceed.com/manuals/artila/Matrix%20500%20Quick%20Installation%20Guide.pdf Board layout]
* A mini-USB connector for the USB Device Controller (UDC) is on the right side of the housing (not shown on above documents)

== Options ==

Standard [http://de.wikipedia.org/wiki/Flash-Speicher flash memory] option is with 16MB flash memory. On request 8MB or 32MB and 64MB are available.

== Watchdog ==

Matrix 500 has a watchdog device and it works as a standard watchdog device under Linux. The default setting of the watchdog timer is 5 seconds. Kernel will reset the watchdog timer before it time out. If for some unexpected reason, kernel fails to reset the watchdog timer, Matrix 500 will reset itself and system will reboot again. We do not recommend user to use watchdog timer in his application. To implement a software Watchdog process is a better way for application level watchdog

== Application Stories ==

Matrix-500 is a standalone embedded computer. Typical applications are in data collection and preparation in POS ([http://de.wikipedia.org/wiki/POS-Terminal Point Of Sale]), at a gas station to prepare and transmit accounting data or in advertisement systems with displays.

== Tech Spec ==

* 2*USB, 3*RS232, 1*RS232/422/485, 1*10/100 Ethernet
* Matrix 500 has a MMU. It is a MMU ready Linux Kernel and fork() is ok. It is not necessary to specify stack size at compile time.
* Matrix 500 uses Standard Linux with MMU Kernel version 2.6.14
* Root Filesystem uses ETX2 format. The Root Filesystem is extract and built on the RAMDISK of Matrix 500 during system startup. The system image uses about 4MB space of the Flash Memory
* User Flash disk uses JFFS2 format and space size is Flash memory size minus 4MB of image(e.g. 16MB Flash - 4MB Image = 12 MB [11764KB ] user flash disk )
* USB WLAN Adaptor Support List (RT2570): [http://rt2x00.serialmonkey.com/wiki/index.php?title=Hardware RT2570 Hardware]
* Boot from USB Disk and SD Card are not available at this moment. We will consider it in the future.

== Firmware Upgrade ==
In case you want to upgrade firmware: use an USB disk and load all files to be upgraded on it. Then
# copy the files "matrix500v2.alf", "m500kv2" and "m500rv2" to a USB flash disk
# Insert the USB disk to Matrix 500
# mount USB disk by " mount /mnt/sda1"
# change to the /mnt/sda1 directory
# type "update m500kv2"
# type "update m500rv2"
# type "update matrix500v2.alf"
# Reboot the Matrix 500

== Source ==

The new link is [ftp://ftp:ftp@ftp.artila.com/Matrix5xx ftp.artila.com/Matrix5xx] (login: ftp, password: ftp).

Python is available on request.

== Flash Recovery ==

1) Recovery from wrong boot image

Please use serial console and under loader screen ( type @@@@ right after reboot to enter loader screen), select format option (H) to format the user disk. After format, reset the system. Doing this will reload the factory setting at next system boot. But it will take about two minute for system to rebuild its /etc/rc.

2) Recovery from corrupt flash

After download newest firmware please perform following steps:

Find the flash corrupted Matrix 500
# Open metal case of Matrix 500
# Find JP1 near COM4 port connector
# Place JP1 to 1-2 position
# Connect the console cable on Port 3 of Matrix 500
# Open hyper terminal software and serial port setting as 115200, n,8,1
# Power on Matrix 500 again (or push reset button)
# You will see "CCCCC" pop up on the hyper terminal from console port
# upload file "loader.bin" with Xmodem protocol
# once done, "CCC" will show up again then
# upload "m500v2.bin" with xmodem
# once complete, loader screen will show up. Type "L" key to upload "matrix500v2.alf " with Kermit protocol
# once done, type "S" to upload "m500kv2" with Kermit
# once done, type "T" to upload "m500rv2" with Kermit

After all these steps are done, place the JP1 to 2-3 position and then reset Matrix 500. The new loader and kernel will boot up and you can perform the test again.

== Why to choose ARM9 with MMU ==

MMU (Memory Management Unit) is important unit for CPU which is operated on multi-task Operating System and software. If the CPU does not have MMU, it have to use uCLinux which is a special version Embedded Linux OS which is designed for non-MMU CPU. Special care must be taken into consideration if you want to port x86 Linux software to a non-MMU RISC-based Linux plaftform. To avoid this compatibility issue, it is better to choose ARM9 RISC with MMU

[[Category:Produkt]]

GPort104

2009-08-18T13:20:23Z

Jan Keyling:

GPort104

2009-08-18T13:10:09Z

Jan Keyling:

== GPort104 ==
GPort104 is an easy to use Serial over Ethernet module. There are 4 RS232 ports (with DB9 male connector), one 100/10 Ethernet port and one RJ 45 console port. The internal processing is done by a Linux system which runs on a 32bit 100MHz MIPS CPU with 8MB flash ROM and 16MB SDRAM

== Quick Installation Guide for Virtual COM mode ==
1. Install the Gport_ap-Software which is found on the included CD.
2. Connect the GPort104 with your LAN using GPOrt´s WAN-Port on the right side of the front panel. Switch on the device.
3. Start the software, click "Search" to determine if the GPort is connected

[[Category:Produkt|GPort104]]

GPort104

2009-08-17T15:56:53Z

Jan Keyling:

GPort104

2009-08-17T15:54:28Z

Jan Keyling:

GPort-104

2009-08-17T15:48:20Z

Jan Keyling: GPort-104 moved to GPort104

#REDIRECT [[GPort104]]

GPort104

2009-08-17T15:48:20Z

Jan Keyling: GPort-104 moved to GPort104

== GPort104 ==
GPort104 is an easy to use Serial over Ethernet module. There is one 100/10 Ethernet port and one port DIP switch selectable to RS232, RS422 or RS485. IP101 has one serial port, IP102 2 ports and IP104 has 4 ports

== IP Module In Serial Tunnel ==
* In paired mode (or tunnel mode) you will need 2 IP101
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* For make safe pairing we need to use fixed IP addresses

== RoHS conformity changes ==
The hardware for old IP101 and new IP101 is same architecture. But there are some modification in part to meet RoHS. The major different is in power adaptor. So it is no difference in firmware.

== Firmware ==
Please keep in mind that ver1.5 and ver1.8 firmware is fully different.
If customer could use ver1.5 firmware, then we don't suggest to upgrade.
The upgrade procedure is very complex. Please read the PDF file in
attached file carefully. There are two steps to upgrade the firmware.
* step 1===> to upgrade ver1.5 to middle version firmware.
* step 2===> to upgrade middle version to ver1.8

Please use one clean environment (just one PC and one IP101 in LAN connection) to do
upgrade procedure.

[[Category:Produkt|Ip101]]

GPort104

2009-08-17T15:47:20Z

Jan Keyling:

GPort104

2009-08-17T15:42:03Z

Jan Keyling:

== GPort-104 ==
GPort-104 is an easy to use Serial over Ethernet module. There is one 100/10 Ethernet port and one port DIP switch selectable to RS232, RS422 or RS485. IP101 has one serial port, IP102 2 ports and IP104 has 4 ports

== IP Module In Serial Tunnel ==
* In paired mode (or tunnel mode) you will need 2 IP101
* Choose either TCP (safer, recommended) or UDP (faster) mode
* One module needs to work as "client" and the other as "server"
* For make safe pairing we need to use fixed IP addresses

== RoHS conformity changes ==
The hardware for old IP101 and new IP101 is same architecture. But there are some modification in part to meet RoHS. The major different is in power adaptor. So it is no difference in firmware.

== Firmware ==
Please keep in mind that ver1.5 and ver1.8 firmware is fully different.
If customer could use ver1.5 firmware, then we don't suggest to upgrade.
The upgrade procedure is very complex. Please read the PDF file in
attached file carefully. There are two steps to upgrade the firmware.
* step 1===> to upgrade ver1.5 to middle version firmware.
* step 2===> to upgrade middle version to ver1.8

Please use one clean environment (just one PC and one IP101 in LAN connection) to do
upgrade procedure.

[[Category:Produkt|Ip101]]

PassPortNetworks

2008-09-16T09:58:33Z

Jan Keyling:

== Firmware Update Procedure ==

Please make sure:
* The serial port mode is upgrade mode.
* DIP switch is off-off position.
* Make sure the RS232 cable is NULL modem cable. If there is no NULL modem cable, please use Virtual COM for upgrading.
* Use 19200 Bd, 8-N-1 on both the device server and the host pc.
* After upgrading firmware with manager software, reboot the serial device server and re-enter your settings (like baudrate, IP address etc.).
== Firmware Version ==

This firmware version (31. Oct. 2007) fixes an auto direction timing problem:
* 1 port module [http://www.acceed.com/download/artila/aport311_upgrade_103107.hex aport311]
* 2 port module [http://www.acceed.com/download/artila/aport312_upgrade_103107.hex aport312]

== History of Firmware ==

This firmware version (13. Jul. 2007) does significantly reduce answering delay time:
* 1 port module [http://www.acceed.com/download/artila/aport311_upgrade_071307.hex aport311]
* 2 port module [http://www.acceed.com/download/artila/aport312_upgrade_071307.hex aport312]

PassPortNetworks

2008-09-16T09:57:49Z

Jan Keyling:

== Firmware Update Procedure ==

Please make sure:
* The serial port mode is upgrade mode.
* DIP switch is off-off position.
* Make sure the RS232 cable is NULL modem cable. If there is no NULL modem cable, please use Virtual COM for upgrading.
* Use 19200b, 8-N-1 on both the device server and the host pc.
* After upgrading firmware with manager software, reboot the serial device server and re-enter your settings (like baudrate, IP address etc.).
== Firmware Version ==

This firmware version (31. Oct. 2007) fixes an auto direction timing problem:
* 1 port module [http://www.acceed.com/download/artila/aport311_upgrade_103107.hex aport311]
* 2 port module [http://www.acceed.com/download/artila/aport312_upgrade_103107.hex aport312]

== History of Firmware ==

This firmware version (13. Jul. 2007) does significantly reduce answering delay time:
* 1 port module [http://www.acceed.com/download/artila/aport311_upgrade_071307.hex aport311]
* 2 port module [http://www.acceed.com/download/artila/aport312_upgrade_071307.hex aport312]