Hello, I am trying to use multiple MC7304 devices in our test equipment.
We use the device instance path to identify which device we are using, but this value changes depending in what order the modems are powered up in.
The Com port numbers also switch.
We have had this working fine with MC7750’s using the AT!CUSTOM=“USBSERIALENABLE”,1 command, but this does not appear to be supported for the MC7304.
If I power on MC7304#1 then MC7304#2 I see
Device Instance Path#1 = USB\VID_1199&PID_68C0\0123456789ABCDEF
Device Instance Path#2 - USB\VID_1199&PID_68C0\6&34275E43&0&4
If I power them on in the reverse order I get:
Device Instance Path#1 - USB\VID_1199&PID_68C0\6&34275E43&0&3
Device Instance Path#2 - USB\VID_1199&PID_68C0\0123456789ABCDEF
Does anyone know if there is a different firmware that supports this command or if there is another way to achieve this using a driver registry setting
Syslog? Isn’t that for linux systems?
I’m on Windows 7 Embedded.
And for a bit of background, our device contains between 1 and 4 modems and is used for testing.
We have customers using it with 7700, 7710 and 7750 devices and are now adding support for the 7304.
Each modem has its own power control so they can be powered on/off independently and this is what is causing the device instance paths to change.
We did not see this problem with 7700 and 7710.
This problem was present on the 7750 but was fixed by setting USBSERIALENABLE to 1.
But this custom command does not appear to be available for the 7304.
This is what I get from PuTTY when I try to set USBSERIALENABLE
ati
Manufacturer: Sierra Wireless, Incorporated
Model: MC7304
Revision: SWI9X15C_06.03.17.00 r23799 CNSHZ-AR-BUILD 2014/08/08 12:51:51
IMEI: 356853050340498
IMEI SV: 0
FSN: J3448501830210
+GCAP: +CGSM,+FCLASS,+DS
OK
AT!ENTERCND="A710"
OK
AT!Custom="USBSERIALENABLE",1
ERROR
Oh yeah missed that windows thing…
So it seems with 2 mc7750… You are getting the same device instance paths every time… May be an issue with mc73… Seems like when 2 modems are inserted with same vid pid… Windows generate the unique string… But then it is working with mc7750…
I’ll check this internally… But just for info… Can you share the mc7750 device instance paths??