#echo 0 > /sys/class/gpio/gpio346/valueSerial PortSerial device nodes mapping.Table 2. Serial device nodes mapping table.Port Type Connector Device NodeRS232 DB9 /dev/ttyS6RS422_485 5 pin terminal /dev/ttyS4RS485 3 pin terminal /dev/ttyS5RS485 3 pin terminal /dev/ttyS2Execute the #sudo chmod 777 /dev/ttyS# command on two systems, where # is port number corresponding to ports beingused.• On system A, execute the #cat < /dev/ttyS# command, this will put system A waiting for transmission.• On system b, execute the #echo "test" > /dev/ttyS# command, this will let system B send out transmission.Expansion IO ModulePCIeThe PCIe slot on the external IO Module for the Edge Gateway is driven directly from the host PCIe bus. Since it is generic PCIeexpansion, there are no PCIe device-specific drivers integrated into the OS image. If there is specific PCIe card used on this slot,contact the Vendor of that PCIe card for drivers.GPIOThe GPIOs on the external IO Module for the Edge Gateway are behind PIC microcontroller. The PIC microcontroller is exposed tothe host system and to the host OS as a USB-HID device. Software application developed to communicate with the GPIOs may usethe protocol defined in following set of references to communicate with the GPIO modules. There is no native application softwareavailable on the factory OS image that communicates with the IO Module GPIOs.ZigbeeNOTE: This feature is only supported if hardware module presented.The OS provides the capability of mutual communication between user space application and physical module. If there is a specificZigbee programming requirement of user mode application, contact the hardware provider of that module for API Documentation.Controller Area NetworkNOTE: This feature is only supported if hardware module presented.The OS provides the capability of mutual communication between user space application and physical module. If there is a specificController Area Network (CAN) bus programming requirement of user mode application, contact the hardware provider of thatmodule for API documentation.To find the device bus iver dmesg (if hardware is presented):• #dmesg | grep –i microchip• for i in /sys/class/hidraw/*; do udevadm info $i --attribute-walk | grep -q 'CANBus HIDDevice' && echo path: /dev/$(basename $i); done36