RG255G-CL WinCE driver

IoT Modules 5G Module
1

Hi!
Short question regarding availability of USB driver support for RG255G-CL on legacy Windows CE operating systems (CE 6.0 / WEC7 / WEC2013).
This topic came up because there’s increasing demand to support 4G and 5G connectivity as 2G and 3G networks are closing down.

Right now we have legacy systems where the EC25 4G module is working quite happily with the “UC20 WinCE USB Driver”.
We’re using version 2.1.2.0 of the driver and get acceptable data transfer rates with dial-up networking (ATD*99#) on the virtual COM port of the EC25.
This uses Interface 3 - the “Modem Interface” - of the USB device.

I’ve tried the same approach with the RG255C-GL eval board.
After modifying the registry with appropriate VID/PID values to load the driver I get only one virtual COM port that responds to AT commands: Interface 2 of the USB device.
Dial-Up networking on this virtual COM port does work but is extremely slow; less than 70 kilobyte/s throughput.

So my question to the Quectel Team is:
Is there any way to get better throughput on this virtual COM port of the RG255G-CL?
If not, are there other options (RNDIS?) to get this modem up and running on Windows CE?

Thanks!

2

Quectel didn’t provide the driver for WinCE any more.
The RG255C support the RNDIS.
You need set it with the AT.

AT+QCFG="usbnet".3
AT+QMAPWAC=1

It will take effect after reboot.

3

I haven’t been able to test RNDIS yet.

Can you in the meantime please clarify if 2.1.2.0 is the latest version of the driver released by Quectel?
Because even if RNDIS works we will need the virtual COM port for AT commands and we want to make sure we’re using the latest version.

Also, is it expected behaviour that throughput on the virtual COM port is so slow?
I’m really surprised by this behaviour. With EC25 we’re getting a few megabytes per second - not 70 kilobytes per second…

4

Quectel will not release the driver for the WinCE. You can send the AT command before the module inserted in the WinCE.