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 [...]
Our display controllers do not directly support this J1939 vehicle communications standard. If you found a host computer (ex., microprocessor board) that does use J1939, it may be possible to use the data from this protocol with our display controllers. The host computer needs either RS-232, TTL, or USB (depending on the module) to receive the data using our command set.
We do not support Modbus RTU Protocol (software).
UART is the only serial bus we support: RS232, TTL/CMOS, and on some modules USB. We also support an RS485 like addressed protocol over the UART.
No, we only support serial data transfer. We do not support parallel data transfer.
