Search found 5 matches
- Wed Dec 12, 2018 7:16 pm
- Jump to forum
- Jump to topic
Re: WG3526 connection problems - no signal, AT!GSTATUS? fails
Yes, give me a few minutes and I will work you up a game plan.
- Thu Dec 13, 2018 9:23 am
- Jump to forum
- Jump to topic
Re: WG3526 connection problems - no signal, AT!GSTATUS? fails
Hi Jim -
I am using SMA connectors that I purchased from Air802. I know there are a lot of garbage products on the market from ebay etc. but these appeared to be high quality. The LMR400 cable is from Altelix...i'll have to test the cables next and get back to you. Thanks again for helping
do ...
- Thu Dec 13, 2018 9:38 am
- Jump to forum
- Jump to topic
Re: WG3526 connection problems - no signal, AT!GSTATUS? fails
One other task that you may want to perform to assure the router firmware is actually programming the MC7455 is to program it manually.
at!entercnd="A710"
at!usbcomp=1,1,1009
at!selrat=06
at+cfun=1
at+cgdcont=1,"ipv4v6","broadband"
at!custom="IPV6ENABLE",1
at!reset
at!entercnd="A710"
at!usbcomp=1,1,1009
at!selrat=06
at+cfun=1
at+cgdcont=1,"ipv4v6","broadband"
at!custom="IPV6ENABLE",1
at!reset
- Mon Jun 10, 2019 4:57 pm
- Jump to forum
- Jump to topic
Re: WG3526 connection problems - no signal, AT!GSTATUS? fails
That may be part of your problem. We have discussed allowing Windows to control a modem on previous posts:
MEMBER: I am not sure about other Windows versions, but Windows 10 64Bit, if you have the MC7455 drivers installed in a USB adapter with everything running fine while connected to a ROOter ...
MEMBER: I am not sure about other Windows versions, but Windows 10 64Bit, if you have the MC7455 drivers installed in a USB adapter with everything running fine while connected to a ROOter ...
- Thu Jun 27, 2019 1:39 am
- Jump to forum
- Jump to topic
Re: WG3526 connection problems - no signal, AT!GSTATUS? fails
I also just noticed that your firmware build numbers don't match your carrier configuration (the PRI lines) in the AT!IMAGE? results. One of them matches your preferred firmware build number and the other one matches your current firmware build number. Something doesn't seem right there.
Sprint is ...
Sprint is ...