We are able to talk to an HE910 module over the USB interface from our proprietary Windows Embedded Compact 7 device. I can query the port configuration, as shown at the top of the screen-shot attachment.
However, when we try to talk to an LE910 module from the same device, we get no response from the single USB serial port presented by the module (the HE910 present 7 USB serial ports). Furthermore, when I try to query the port configuration over RS232, I get an ‘ERROR’ response, as shown at the bottom of the second-shot attachment.
What would cause the command to generate an ‘ERROR’ response? I believe we need to set the port configuration so that we have the full set of 7 USB serial ports available to us but, clearly, we can’t do this when the command generates an ‘ERROR’.
Hi Tim,
Currently we don’t have drivers for win CE 7.0 for the LTE modules.
Is there a reason why Microsoft’s standard USBSER driver (a USB CDCACM driver) wouldn’t work with LE910? It works fine with HE910. In other words, does the LE910 require a non-standard CDCACM driver?
Hi Tim,
Are you still referring to WIN CE?
Or to regular Windows?
Yes, we’re using Windows Embedded Compact 7 and Windows Embedded Compact 2013 (formerly Windows CE).
I’ve cloned Microsoft’s ‘USBSER’ USB client driver and added the appropriate registry keys for HE910 and LE910 modem modules. We get 7 USB serial ports with the HE910 module with a fully working AT interface on the first serial port (COM1 on our platform).
So far, we’ve only got the RS232 interface working with the LE910 module. The USB interface is not working correctly. We suspect the modem is not initialising correctly because PWRMON is permanently active, regardless of the state of ON_OFF#. However, we also have pre-production firmware in our LE910 module (17.00.521-B007) and some fairly simple functions, such as the following, return an error:
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
We are able to talk to an HE910 module over the USB interface from our proprietary Windows Embedded Compact 7 device. I can query the port configuration, as shown at the top of the screen-shot attachment.
However, when we try to talk to an LE910 module from the same device, we get no response from the single USB serial port presented by the module (the HE910 present 7 USB serial ports). Furthermore, when I try to query the port configuration over RS232, I get an ‘ERROR’ response, as shown at the bottom of the second-shot attachment.
What would cause the command to generate an ‘ERROR’ response? I believe we need to set the port configuration so that we have the full set of 7 USB serial ports available to us but, clearly, we can’t do this when the command generates an ‘ERROR’.
Hi Tim,
Currently we don’t have drivers for win CE 7.0 for the LTE modules.
Is there a reason why Microsoft’s standard USBSER driver (a USB CDCACM driver) wouldn’t work with LE910? It works fine with HE910. In other words, does the LE910 require a non-standard CDCACM driver?
Hi Tim,
Are you still referring to WIN CE?
Or to regular Windows?
Yes, we’re using Windows Embedded Compact 7 and Windows Embedded Compact 2013 (formerly Windows CE).
I’ve cloned Microsoft’s ‘USBSER’ USB client driver and added the appropriate registry keys for HE910 and LE910 modem modules. We get 7 USB serial ports with the HE910 module with a fully working AT interface on the first serial port (COM1 on our platform).
So far, we’ve only got the RS232 interface working with the LE910 module. The USB interface is not working correctly. We suspect the modem is not initialising correctly because PWRMON is permanently active, regardless of the state of ON_OFF#. However, we also have pre-production firmware in our LE910 module (17.00.521-B007) and some fairly simple functions, such as the following, return an error:
at#gpio=1,0,2
ERROR
Regards
Tim Clacy