Loss detection of EM7565 modem in ZBT We826

[insaneswami]

Hello,

I upgraded to the EM7565 modem in my ZBT WE826-Q. Initially, it was detected and just would not connect to Verizon. APN was set correctly as I had used the old Quectel previously. Turns out that it likely was the antenna connections as the Quectel was mini-pcie and the Sierra modem is m.2. Finally found that out after a lot of frustration and unfortunately, using AT commands after firmware upgrade didn't solve the issue. It appears I lost the ability for the router to communicate with the modem and I cannot communicate with it on my PC using a USB adapter either.

I tried doing the following:
EM75XX -- Restoring Modem AT Command Port (After Using Wrong Commands)
Post by JimHelms » Wed Feb 26, 2020 6:16 pm

Using the incorrect AT Commands to change the composition of an EM7565/EM7511 mode to QMI and/or MBIM is a common mistake which results in removing the modem's AT Command port.

Most generally this occurs when using the AT Commands on the EM7565/EM7511 that apply to the EM/MC74XX modems. The difference in the command as very minor (i.e., 1 digit).

For instance, to place a MC7455 modem in MBIM composition uses the AT Command:
CODE: SELECT ALL

AT!USBCOMP=1,1,1009
where the EM75XX requires:
CODE: SELECT ALL

AT!USBCOMP=1,3,1009

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

Using PuTTy, login the router using the routers IP address, generally 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.


However, when I got to "At!entercnd="A710" it states error and no longer responds.

Tried doing ftd2 without any success as well. It just cannot find a port to communicate with it. The modem does show up in windows as "Other device" not a network adapter. Drivers have not helped this either. The modem shows up in the connection log of GoldenOrb/WiFix, but that it just sees it is there. It will not allow communication, or do anything either.

I'm at a loss on what to do. Will get the correct pigtails, but if I can't get it to work before that, there is no point. Any help is appreciated. Thanks.

[Didneywhorl]

Do you have the Huawei modem terminal?