Just had another MC7700 die! My laptop must get too hot. Next time I will try an MC7355 instead as it is specified up to 85 celsius.
Is thermal mitigation implemented correctly on the MC7700? Running firmware 3.5.24.0. Thermconfig shows all disabled. Even when I enable the values they remain disabled. See commands below.
Delta Tx power(dB)=1
Max backoff (dB)=1
time for non-backoff value of power (ms)=1
time for backoff value of power (ms)=1
timer for each step of backoff (ms) =1
I don’t aware that the temperature of laptop may damage the module.
But for !THERMCONFIG command, I think it should effective after power cycle, here’s my test with MC7710 running same FW.
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: MC7710
Revision: SWI9200X_03.05.24.00ap r5792 carmd-en-10527 2013/05/02 13:35:47
IMEI: 358178040029938
IMEI SV: 17
FSN: CCQ3561013210
3GPP Release 8
+GCAP: +CGSM,+DS,+ES
OK
AT!ENTERCND="pass"
OK
AT!THERMCONFIG?
Thermal mitigation configuration:
Adjust maximum Tx power(0-1) 0-Disabled
Disable Rx Diversity(0-1) 0-Disabled
Disable Q-ICE at mitigation state(0-1) 0-Disabled
DL RLC throttling control(0-1) 0-Disabled
UL RLC throttling control(0-1) 0-Disabled
OK
AT!THERMCONFIG=1,1,1,1,1
OK
AT!THERMCONFIG?
Thermal mitigation configuration:
Adjust maximum Tx power(0-1) 0-Disabled
Disable Rx Diversity(0-1) 0-Disabled
Disable Q-ICE at mitigation state(0-1) 0-Disabled
DL RLC throttling control(0-1) 0-Disabled
UL RLC throttling control(0-1) 0-Disabled
OK
AT!RESET
OK
(after back from reset)
AT!ENTERCND="pass"
OK
AT!THERMCONFIG?
Thermal mitigation configuration:
Adjust maximum Tx power(0-1) 1-Enabled
Disable Rx Diversity(0-1) 1-Enabled
Disable Q-ICE at mitigation state(0-1) 1-Enabled
DL RLC throttling control(0-1) 1-Enabled
UL RLC throttling control(0-1) 1-Enabled
OK
Maybe you can first reset module and make sure the setting applied and effective next time?
Still, after it “die”, does it mean MC7700 no longer enumerate and not consuming power?
Do you have chance to check with your distributor or FAE whether the module can recover or really damaged?
Thanks. I do not have a distributor or FAE. I rely on this forum for my support. I gave up on my mc7700 since I suspect the transmitter broke. PCVOLT and PCTEMP normal, see my earlier postings). It could still see wireless networks but not register (tried two distinct active sim cards, one AT&T and one T-Mobile). Which of the antenna ports is used for transmitting? I assume the main (non-diversity).
I just installed an MC7355. It’s working fine and remains so much cooler. LTE and GPS going and temps around 35 Celsius (AT!PCTEMP?). The MC7700 routinely went up to 75 or 80 Celsius under the same conditions. If the MC7355 breaks as well it will be a huge loss since it came all the way from Hong Kong and cost 3 times as much as an MC7700. If this too dies, I will definitely give up on Sierra Wireless modules.
Now the only thing I have a problem with is that Streets & Trips does not like the nmea sentences put out by the MC7355. I set it to the right COM port and checked with Visual GPS that NMEA data is coming in but Streets & Trips 2013 keeps saying it sees data but does not recognize the NMEA sentences as valid NMEA 2.0. Perhaps an MC7355 firmware update would help.
What is the latest AT&T firmware image version for the MC7355? Please do not answer indicating that I should contact my distributor or FAE for the latest firmware. I do NOT have a distributor or FAE. I would just like to know what the latest AT&T MC7355 firmware is and where to download it. Thank you.
yes, lotam and rex alex’s contempt for customers is all too apparent. All they know how to do is to refer users to their often nonexistent FAE or distributor. The list of unanswered questions on this forum is a mile long.
With all the bugs and issues in the Sierra Wireless products one of these days the company is going to be hit hard, perhaps in litigation or from being overtaken by more-capable competitors.
Yup, the products are good, but the support is thin, very thin. Even those who have an FAE aren’t getting support it seems. For being a “developer forum”, this is really a joke. They need to look at something like MSDN and see how a manufacturer should support their developers. We’ve all but switched to other hardware so that we can actually get bugs in firmware fixed, driver support, and in the short term, questions answered. Sad really.