I have two fresh, unprogrammed from the factory FX30 modems, I have downloaded the drivers per the user guide from this link, as well as newer drivers from this link . After downloading and installing they both have the same functionality; I am not able to see the device at all in my device manager, only the sierra wireless location sensor. I have tried 3 different computers, 4 different cables, and two different FX30 modems, and both the sets of drivers, along with all combinations of those. The modems power LED is a solid red, and I have them on an adjustable power supply at 12V. At this point I have no idea what I am doing wrong… Any help is greatly appreciated.
Did you still see the location sensor when disconnecting from pc?
Btw, did they work in linux pc?
Yes, location sensor still shows up when disconnecting from PC.
I only have an old linux machine, but according to guide, nothing shows up under /dev//dev/
ttyUSB
How about dmesg in linux?
Does it show anything when fx30 is connected?
Yes it does! This is the output after its connected.
[ 3178.375659] wlp3s0: disconnect from AP 18:90:88:80:2d:26 for new auth to 18:90:88:79:e8:46
[ 3178.383254] wlp3s0: authenticate with 18:90:88:79:e8:46
[ 3178.397569] wlp3s0: send auth to 18:90:88:79:e8:46 (try 1/3)
[ 3178.411890] wlp3s0: authenticated
[ 3178.412892] wlp3s0: associate with 18:90:88:79:e8:46 (try 1/3)
[ 3178.420594] wlp3s0: RX AssocResp from 18:90:88:79:e8:46 (capab=0x1031 status=0 aid=12)
[ 3178.420668] wlp3s0: associated
[ 3178.423502] ath: EEPROM regdomain: 0x8348
[ 3178.423503] ath: EEPROM indicates we should expect a country code
[ 3178.423504] ath: doing EEPROM country->regdmn map search
[ 3178.423504] ath: country maps to regdmn code: 0x3a
[ 3178.423505] ath: Country alpha2 being used: US
[ 3178.423506] ath: Regpair used: 0x3a
[ 3178.423506] ath: regdomain 0x8348 dynamically updated by country IE
[ 3178.494685] wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 18:90:
I don’t see anything about fx30 in dmesg …
Even there is proper usb driver installed in linux, it should still show something in dmesg
Ah ok then nevermind… that’s just what showed up when the fx30 was plugged in.
Where would I find the proper USB drivers for linux?
you can find the linux driver here:
https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/
Ok, spent some time updating my linux machine (it was running an OS from a decade ago) still nothing in DMESG. However I would much rather prefer to use in windows anyways. I was able to make the PORTS (COM & LPT) show up in device manager, but there is a yellow triangle beside it, and still nothing shows up on FDT tool.
what have you changed compared to previous trial?
there is no such port in previous trial:
but i have no idea what this “sierra wireless iot device CLI commands port” is.
Never see such before…
So I found a guide how to view hidden ports. In device manager, went to action—> add legacy hardware —> Install the hardware that I manually select from a list —> Ports (COM & LPT) —> Sierra Wireless HL Communications —> Sierra Wireless IoT Device CLi Commands Port
Will this port disappear if you disconnect the usb of fx30?
No, absolutely nothing happens when FX30 is plugged in
Then the com port is not related to your fx30
OK… so any ideas how to fix this? Every guide just says, download drivers and it will show up and you can flash… I have FW ready to go to flash with but cant get it to show up
Problem is that it does not have any response with both windows or linux
Did you contact distributor for RMA?
@cchenry ,any idea on this fx30 device?
No, have not done that yet since both FX30’s did not work in the same manner, I assumed it was something on my end.