WG3526 EM7565 Modem Present Not Connected

[qisdtech]

Hey Jim,
I have a question regarding a WG3526 and EM7565, running the 2019 GO firmware. I'm having an issue with a static IP T-Mobile sim card that won't connect in LTE, only in HSPA+. T-Mobile uses B2B.static APN and IPV4 only. The router seems to have the modem boot up in IPV4V6 mode. I have typed the command +CGDCONT: 1,"IP","B2B.static" in the modem misc AT command terminal, but I notice when viewing what the modem is doing under Debug Information, another command automatically sent a short time later, AT+CGDCONT=1,"IPV4V6","B2B.static" which effectively cancels out the first command I sent. Any tips on how to make the the static APN just use IP instead of IPV4V6? I managed somehow to get the router to connect in LTE, but the next time I rebooted the router it goes back to HSPA+ and the IPV4V6. Thanks in advance.

[Jim Helms]

There are two possible solutions. I would try the first method and if that did not resolve, add the second.

First method. Add the preferred APN to the start up:

Code: Select all

at+cgdcont=1,"ip","B2B.static"

AT-Command At Startup.png

Be sure and SAVE & APPLY

You will need to reboot the router for it to take effect.

If that still does not cure the issue, you can disable IPV6 in the modem. This would keep the modem from connecting using IPv6 but may not change the IPV4V6 APN that is being sent to the modem (that the first method hopefully resolves):

Code: Select all

at!entercnd="A710"
at!custom="IPV6ENABLE",0
at!reset

[qisdtech]

Just an update. I tried both methods without success. It does send the correct APN info, but just a few seconds later the router overwrites what I did with the IPV4V6 APN. I assume there's not a setting to modify to change the IPV4V6 to IP ?
It's like it's built-into the boot-up of the WiFix firmware. I have found a workaround, I simply just keep typing in the correct line and eventually it takes, attaches to LTE and works well, until the router is rebooted.

[Jim Helms]

Just an update. I tried both methods without success. It does send the correct APN info, but just a few seconds later the router overwrites what I did with the IPV4V6 APN. I assume there's not a setting to modify to change the IPV4V6 to IP ?
It's like it's built-into the boot-up of the WiFix firmware. I have found a workaround, I simply just keep typing in the correct line and eventually it takes, attaches to LTE and works well, until the router is rebooted.

You will most like need to modify a line in one of the scripts that is issuing the IPV4V6 command. I will play with doing this when I get some extra time.

[darren.may]

Hi Jim,
I received my USB to M.2 adapter today and attempted to follow your EM7565 restore AT commands tutorial.

When I get to the fdt2.exe step I get the following output:

Code: Select all

FDT version: 1.0.1806.0
Awaiting suitable port or adapter ...
Enabling selective suspend ...
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 65 - Waiting command response timeout.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:
Final images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:

OEM PRI:

IMEI:

Total time elapsed: 39328 ms.
Images downloaded:
Press Enter to continue ...

Huawei_Modem_Terminal terminal only shows:

Code: Select all

COM3 (Sierra Wireless DM Port (COM3)
COM4 (Sierra Wireless NMEA Port (COM4)

Suggestions on where I should go from here? Any advice would be greatly appreciated.

[Jim Helms]

Hmm... If that did not do it, you will most likely need to use a Linux machine to restore, or possibly a load a modem manager build on your WG3526.

See this TOPIC.

[Jim Helms]

Any luck with this. If not, I may have one more suggestion.

[darren.may]

No luck. I don't have a Linux machine and don't quite understand how to use ModemManager properly. Can you please share your other suggestion? Thanks.

[Jim Helms]

I will work something up for you.

[Jim Helms]

You might also read the resolution where someone else had the identical issue on the ROOter forum.

[Jim Helms]

This is the important part that you may want to try using device manager on your PC to find the WWAM Modem COM Port:

Ok all is solved with the EM7565. I'm not sure how much I was originally doing wrong but here is what ended up working and it's basicly what everyone said to do.

Put em7565 into mbim using putty on Windows.

You will see the com port of the em7565 under device manager under modem.

Log into putty using serial and choose that com

Usb comp needs to be 1,3,1009 or you could do 1,3,100D

At!entercnd="A710"
at!usbcomp=1,3,1009
at!reset

I chose 9 as that's what everyone else did.

Next change the script from jhend up above using vi or a good text editor in winscp

Then create a startup script of this under system startup.

echo "1199 9091 0 1199 9079" >/sys/bus/usb-serial/drivers/qcserial/new_id
exit 0

I'm sure there's a better way than a startup script. I'm sure jhend or DM can add that in somewhere.

Don't copy and paste. You get hyphens instead of minus signs.

Everything works as intended.

As for the startup script, the corrected script mentioned above is:

Code: Select all

echo "1199 9091 0 1199 9079" > /sys/bus/usb-serial/drivers/qcserial/new_id
exit 0

But, I really believe those PID/VID's are already included in the newer GoldenOrb firmware and I am not sure what purpose they play.

However, you could always enter it and reboot, and then delete the script when it is no longer needed.

Startup Script.png

[muenchris]

I did the same mistake of typing 1,1,1009 instead of the 1,3,1009. Unfortunately my modem does not go in QDLoader mode - it shows the DM and NMEA ports but no QDLoader. in Windows the "Snapdragon" is showing with a band under the "Other drivers" section (No compatible driver found).

Is there a way to hardware reset the modem?

The ftd2.exe fails because it cannot find the modem either

[muenchris]

Hi Jim,
I received my USB to M.2 adapter today and attempted to follow your EM7565 restore AT commands tutorial.

When I get to the fdt2.exe step I get the following output:

Code: Select all

FDT version: 1.0.1806.0
Awaiting suitable port or adapter ...
Enabling selective suspend ...
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 65 - Waiting command response timeout.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:
Final images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:

OEM PRI:

IMEI:

Total time elapsed: 39328 ms.
Images downloaded:
Press Enter to continue ...

Huawei_Modem_Terminal terminal only shows:

Code: Select all

COM3 (Sierra Wireless DM Port (COM3)
COM4 (Sierra Wireless NMEA Port (COM4)

Suggestions on where I should go from here? Any advice would be greatly appreciated.

My ftd2.exe fails with the same errors above

I did the same mistake of typing 1,1,1009 instead of the 1,3,1009. Unfortunately my modem does not go in QDLoader mode - it shows the DM and NMEA ports but no QDLoader. in Windows the "Snapdragon" is showing with a band under the "Other drivers" section (No compatible driver found).

Is there a way to hardware reset the modem?

[muenchris]

The trick from Rooter did work. I had to do this:

echo 1199 9091 > /sys/bus/usb-serial/drivers/option1/new_id

on my WRT and the connect with picocom /dev/ttyUSB0 and set the correct 1,3,1009 and I got my modem back!

Thanks!

[Jim Helms]

One of the members on the Hacks Facebook group, clarified how to fix the issue of losing the Modem COM port. Coupled with the post above, we will help to better describe the fix.

The modem can fixed while installed in or behind a router running OpenWRT/GoldenOrb/WiFiX firmware.

Using PuTTy, login the router using the IP address 192.168.1.1

Once in, run the following command:

Code: Select all

echo 1199 9091 > /sys/bus/usb-serial/drivers/option1/new_id

Then repair the config with:

Code: Select all

picocom -b 115200 /dev/ttyUSB0

Then place the modem in MBIM composition with the follow commands:

Code: Select all

At!entercnd="A710"
At!usbcomp=1,3,1009
At!reset

And, that should do it.

[jcarson]

I just put together a WE-826-T2 with a EM7455, the Mini PCI-E to M.2 (NGFF) Key B Adapter with Top SIM Card Slot with the pigtail jumper cables.

I tried both wefix goldenorb files. But it always says modem present not connected. I've tried an att sim and a verizon which are both working on other routers.
I've been reading all day and it seems like this thread would provide a fix but I can't login via PuTTY. Is there a tutorial for that? Thanks

[Jim Helms]

Going to MODEM > MISCELLANEOUS > AT-COMMAND TERMINAL, are you able to issue any AT Commands?

[jcarson]

It won't let me input any AT commands. When I type one in, it disappears and nothing happens.

[jcarson]

Going to MODEM > MISCELLANEOUS > AT-COMMAND TERMINAL, are you able to issue any AT Commands?

It won't let me input any AT commands. When I type one in, it disappears and nothing happens. I'm not sure which method to use to fix this.

[Jim Helms]

First, go to the MODEM > DEBUG INFORMATION > DEVICE INFORMATION and see if you see the EM7565 listed. It should reference something like:

Code: Select all

P: Vendor=1199 ProdID=9091 Rev= 0.06 	
S: Manufacturer=Sierra Wireless, Incorporated 	
S: Product=Sierra Wireless EM7565 Qualcomm® Snapdragon™ X16 LTE-A

[Jim Helms]

If you are seeing it listed, you will need to use THIS method.

[brad2388]

i have the same problem but with a em7511 modem. is there a working setup on the we826?

[Jim Helms]

i have the same problem but with a em7511 modem. is there a working setup on the we826?

There is a large number of people running the EM7565 and EM7511 on the WE826-T2, using GoldenOrb.

The issue that some people have is using the AT Command for the MC7455 to place the modem into MBIM mode--which removes the WAN modem COM port. The EM75XX requires a different AT command.

[MitchDudley]

what was the fix for this? I'm experiencing the same issue

[Jim Helms]

what was the fix for this? I'm experiencing the same issue

Did you place the modem in MBIM using the AT Command for the MC7455 and lose the modem AT Command port?

[MitchDudley]

I did use the AT Command to place in MBIM but it was for the EM7565. the AT Command post is not working.

[Jim Helms]

If the modem was working when you placed it in MBIM mode (as it must have been in order to enter AT Commands), and now you are unable to communicate with the modem, then it sounds like to me you have lost your modem WAN port. This will happen when using the wrong AT Command.

[MitchDudley]

what's the fix?

[Jim Helms]

See THIS tutorial for restoring the COM Port.

[MitchDudley]

looks like you are out of USB to M.2 adapter for the EM7565. Can you recommend another location? Amazon?

[Jim Helms]

We have them on order but Amazon would probably be the quickest.

[derekdauzat]

im about to buy em7511 for the wg3526 is it plug and play other than the m.2 adapter?
MBIM +AT work out of the box or is there some tinkering? should I get the em7565 instead?
can someone please list the steps in order a procedure in case the EM7511 is not in the proper mode?... I'm afraid of getting wrob module. is there a version of the EM7511 not to get like the laptop version?

[Jim Helms]

If you are using AT&T, you may benefit by using the EM7511 which has band 14 which EM7565 does not.

There is not much tinkering to installing the modem in a router running GoldenOrb with will recognize and communicate with the EM75XX modem in QMI composition without having to place the modem in MBIM.

Also, be sure that any AT Commands used to change the composition of the modem are for the EM7565/EM7511 and NOT for the MC7455. Otherwise, you will lose your WAN port for AT Commands.

Try to purchase OEM modems, and not vendor branded (i.e., Dell, ....).

[Orvalman]

I am trying to upgrade the modem card in my WE826-T2 from a 7455 to a 7565. I am having the same problems as above and would like to issue the AT!USBCOMP=1,3,10D command, but the AT command line entry disappears when I start typing. The 7565 card shows up in the debug screens. I downloaded putty but am having problems connecting. I have tried SSH and Serial, but I'm not sure the ethernet to USB-C adapter I'm using to connect from the WE826 router to my laptop (with a USB-C port but no ethernet port) will allow a connection? Any suggestions?

[Jim Helms]

What version firmware are you running on the WG3526?

[Orvalman]

Golden-Orb 2017-12-15

The provider of the SIM card prefers this version over more recent versions which he says have some issues.

[Jim Helms]

I do not believe that version has support for the EM7565.

I would upgrade to the newest WiFiX version that we just released.

[Orvalman]

Does the WiFIX version include the "rndis package"? My SIM provider is asking - thinks it should be standard.

[Didneywhorl]

I dont know the answer to this question, but you can always send your provider a copy of the firmware to check out him/her self

[toddw]

One of the members on the Hacks Facebook group, clarified how to fix the issue of losing the Modem COM port. Coupled with the post above, we will help to better describe the fix.

The modem can fixed while installed in or behind a router running OpenWRT/GoldenOrb/WiFiX firmware.

Using PuTTy, login the router using the IP address 192.168.1.1

Once in, run the following command:

Code: Select all

echo 1199 9091 > /sys/bus/usb-serial/drivers/option1/new_id

Then repair the config with:

Code: Select all

picocom -b 115200 /dev/ttyUSB0

Then place the modem in MBIM composition with the follow commands:

Code: Select all

At!entercnd="A710"
At!usbcomp=1,3,1009
At!reset

And, that should do it.

Thank you for this!!!! I thought I bricked one of my 7411's last night and this did the trick. I did have to combine this with a clean install of wifix.

[jjhdtv]

Old thread but I have a similar problem (modem not present) and need some help fixing
I have a wg3526 with Sierra mc7445. The router is mounted 30 feet in the air, thus not really convenient to get to

Everything was working. Using an at&t sim.
Started to play around with assigning and locking bands using AT commands from the Rooter web interface. This was successful however I did seem to mess up carrier aggregation. So I attempted to remove the locked bands. Use the code AT!ENTERCND=“710” then AT!BAND=00. At this point I lost the modem wan connection. Upon reboot I now get “modem not present”. Hence no lte connection.

Not sure if the last AT command (perhaps fat fingered) messed things up or coincidence.
As I can’t easily physically access the router, I’m hoping something can be reset using the golden orb Rooter web interface or ssh. Help appreciated

[Didneywhorl]

Login via SSH and see if ttyUSB* is present.

Code: Select all

ls /dev/ttyUSB*

That is LS at the beginning.

This will tell you if the USB bus devices (modem ports) are present.

[jjhdtv]

Thanks for the reply. The ls command returns “no such file or directory”
Hoping that can be fixed. Any suggestions or guide?

The dev directory only shows tty, ttyS0, ttyS01,ttyS02. No ttyusb.

[Didneywhorl]

Place this:

Code: Select all

echo 1199 9071 >/sys/bus/usb-serial/drivers/option1/new_id

In this location: Menu: System->Startup->Local Startup Tab:
....on the line before 'exit 0'


Then Click the 'Save' button

Then reboot the router.

[Didneywhorl]

You may also want to look here: https://wirelessjoint.com/viewtopic.php?f=16&t=911

[jjhdtv]

I have tried the suggestions and still remain without the ability of the WG3526 to recognize the modem
Using Putty, I entered the commands

echo 1199 9091 > /sys/bus/usb-serial/drivers/option1/new_id

and,
picocom -b 115200 /dev/ttyUSB0

which returns
FATAL: cannot open /dev/ttyUSB0: No such file or directory

I have reflashed the wg3526 with both ROOter and OpenWRT (both the latest versions). Same story with both flavors.
I have also taken out and re-installed the pcie modem card mc 7445 from the adapter in the wg3526 (no difference).

still looking (almost begging) for suggested next steps.

[Didneywhorl]

Show us a full screen shot of the Modem->debug screen

Not the text box, the long list of text at the lower end. The whole page of text.

Screen shot, or copy paste it into a quote here.

[jjhdtv]

IMG_2507.jpg

I have posted the Putty screen from my SSH session.
The modem debug screen (in ROOter) is blank. I believe because the wg3526 does not find and/or load the modem. Similarly, AT commands from within Rooter or Putty do not work.

[jjhdtv]

If it helps. I wanted to reiterate that all was working until I remoted in to my raspberry Pi (connected to the local network, the wg3526 and the cellular WAN)using VNC and executed the following command through the ROOter web interface page: AT!BAND=00

Instantly lost my remote connection. Travelled 200 miles to the remote site to find everything still running but no modem present, hence no WAN connection. Still a mystery. I will be upgrading to an EM7565 in the near future if I can't get this 7445 up an running. thanks again.

[Didneywhorl]

The IMG_2509.jpg is what I need, but I need the Device Information section below what you posted. You can copy paste the text if you like.


After running AT!BAND=00 did you run AT!RESET?

I'm sure you rebooted, but did you power cycle it or reboot the modem with AT!RESET ?
Setting the modem to all bands shouldn't have done anything but need a hard reboot.

[jjhdtv]

I did not have the opportunity to run AT!RESET as all fell apart after attempting to set all bands (No modem connected - no ability to run AT commands. I have since physically rebooted and power cycled multiple times, in addition to reflashing with both OpenWRT/modemanger and the ROOter. No change to the issue at hand.

Attached are the rest of the Debug Information. Appreciate the help. (changed to a txt file)

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 5.04
S: Manufacturer=Linux 5.4.124 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
********************************************************************************************************
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev= 5.04
S: Manufacturer=Linux 5.4.124 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

[Didneywhorl]

Hmm. I wonder if the modem was put in a different protocol mode and you've somehow lost the AT command port. Or if its in low power mode now.

It's definitely not being recognized by the router.

[jjhdtv]

I ordered a USB adapter. I'm hoping reflashing the generic sierra firmware might be something to try (would you agree?)
Not sure what else to try other than a different modem card to start and eliminate possibilities.

[Didneywhorl]

It will definitely let you see if the modem is responsive by checking it on a pc. You may want to update the router firmware too.

[jjhdtv]

I received my USB To Mini PCI-E Adapter from The Wireless Haven.com. Followed the instruction given to install generic sierra drivers, check with the Huawei Terminal, and then proceed to flash with the generic Sierra MC7445 image.

As this is the first time flashing the a modem card. I'm not sure if I'm missing a step or have a bad modem card/adapter.

Even after multiple driver install attempts (Windows 10), I can not see a modem device listed in the Windows Device Manager. Additionally, the Huawei terminal and the Flash program does not find the modem.

I would like to know what else to try (getting windows to find the adapter and modem) or if this is an indication of something physically wrong with the MC 7445.

[jjhdtv]

UPDATE:
Put adapter and MC7445 into a linux machine. Ran dmseg and the adapter and MC7445 was found. Red led turned on (previously had not). Removed usb adapter and put back in the Windows 10 machine. Windows found and loaded drivers.
Was able to reflash (twice) the generic Sierra firmware. Perhaps it was a connection issue, perhaps the linux machine did something unique to enable the adapter. Not sure.

Will now test in the WG3625 and see if the Modem detection issue was fixed. standby.

[Didneywhorl]

Cool deal! Standing by

Good call on flashing twice. Otherwise the dreaded firmware mismatch error will rear its ugly head.

[jjhdtv]

I keep chugging.
Good news: the wg3625 found the modem and I have an LTE connection.
Bad news; No internet
As I'm working with a complete new install of ROOter and that I have been using my AT&T family sim card in multiple devices since I went down. I don't know if the problem is with AT&T (black listing my sim card) or some other default setting with the new install of ROOter.

I don't remember doing anything different the last setup when everything was working. That makes me suspect of the sim card. Curious if you can show a solid LTE connection but not have internet. If so, what should I check? The status page shows both an Ipv4 and Ipv6 address.

[jjhdtv]

installed latest version of WiFix-NEXP1Go. Internet came back. No understanding of why, but so far so good.

[Didneywhorl]

Awesome! Sometimes the oddest things can be cleared up with a new firmware install.

I flash firmware updates 3x in a row. Rarely do I still have issues.