The baud rate is set in the init script on the module: /etc/init.d/sio-agent. You can change this using various approaches. If you’re familiar with Linux and the ‘vi’ editor, you can use a terminal emulator connected to the debug port, login as ‘root’, with no password, then edit the file, and change the default baud rate to another. Simply reboot the module for the change to take effect. Another approach would be to use G2Link. Connect to the display module’s debug port with the “Select Serial Port” button, then click on View>-Advanced View, then click on “Edit SIO settings”. You can select the desired baud rate from the pull-down, then click OK. This will edit the sio-agent script for you. Another approach is to use G2Link, connect to the debug port as before, but then click “View Files in Explorer”. When the file browser window appears, click on “conifg”, then click on [...]

The +5_EXT signal is for powering small external circuits. This signal comes from the +5V DC input to the display module and is routed through a PTC resettable fuse. The PTC has a rating of 2A at 20C or 1.5A at 60C, and this is the power budget for the combined total of all +5V_EXT outputs. Also, each individual +5_EXT pin is limited to 1A max.

The SD Card section discusses the tools you can use.

The On-Board Flash section discusses the process.

This is covered in our Application Note, AN-117, found in the Application Notes section in the G2H Software Documentation.  

Yes, our controllers with the CAN option support the CAN 2.0B protocol specification.

Reserved I2C devices addresses vary based on the module. Find G2C1 and G2H2 addresses in the tables below. G2C1 Reserved I2C Device Addresses G2H2 Reserved I2C Device Addresses NOTE: Bus 0 is an internal I2C bus. Bus 1 is available on connector J21 (full-stuff modules only).

It is luck-of-the-draw on whether the driver in our kernel supports any given USB-Ethernet adapter or not. The adapters use one of many different controllers, and some might work while others do not. Even if you find one that works, you might not be able to get the exact module again because the vendor will change the internal controller. Because of this driver/controller issue, we don’t support the USB-Ethernet feature.

This issue rarely occurs, and it is due to an unknown configuration setting in the Windows system. We have not been able to determine why this occurs, but we have a workaround, which is to add a Windows credential for the display module. Use these steps to add a credential: Open Control Panel. Click on “User Accounts”. Click on “Manage Windows Credentials”. Click on “Add a Windows Credential”. In the new window, enter the display module’s IP address, enter ‘root’ for “User name:” and leave “Password:” blank. Then click on OK.

Microsoft recently changed their security policy to use Samba 2.0 instead of Samba 1.0, and have disabled Samba 1.0 by default. Our module uses Samba 1.0. Use the steps below to enable Samba 1.0, and this should fix the issue. On Windows 10, starting with build 1709, Microsoft has deprecated and disabled SMBv1 in favor of v2 for security reasons. This will cause G2Link to get an error when trying to Publish and Run a QML application, saying that the path does not exist. If you see this error, you can check which build of Windows 10 is on your system with the “winver” command. It will give you a screen such as: Note: The above screenshot is showing Version 1607 instead. If your system is showing version 1709, you can use the steps below to work around the problem. Start Control Panel, click on Programs, then in Programs and [...]