Wireless Joint

Hi! Thanks for coming to help.
Okay so I bought a generic WE826-T2 off of aliexpress. It came with no modem. Purchased a Fibocom Modem, specifically the XMM 7560 Cat 16 modem. It's a m.2 so I obviously bought the adapter. Assembled everything. The router was running some "Intelligent Router" firmware. Did the recovery boot system to flash OpenWRT onto it. Once OpenWRT was flashed onto it I flashed Rooter onto it. Then I flashed WiFiX-WE826GO onto it. (Current Install)

Issue: The router still shows No Modem Present (yes I tried both Modem 1 and 2). I already did the system time set. I already set the APN to the specific one that comes with my sim. (100% positive it's the right APN) In the DEBUG INFO it shows the Modem and says, Manufacturer = Intel Corp. (*DEBUG INFO POSTED AT END) So it's recognizing the modem right? I've already power cycled this 4 times. Is there a step I'm missing?

Any help is awesome. Thanks, guys!

*DEBUG INFO
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 4.14
S: Manufacturer=Linux 4.14.167 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=101c0000.ehci
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=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=05e3 ProdID=0608 Rev=85.36
S: Product=USB2.0 Hub
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=256ms
********************************************************************************************************
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=8087 ProdID=095a Rev= 3.50
S: Manufacturer=Intel Corp.
S: Product=MODEM + 2 CDC-ACM + 3 CDC-NCM + SS
S: SerialNumber=004999010640000:004999010640000:004999010640000:004999010640000
C:* #Ifs=13 Cfg#= 1 Atr=e0 MxPwr=100mA
A: FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=02 Prot=01
A: FirstIf#= 2 IfCount= 2 Cls=02(comm.) Sub=02 Prot=00
A: FirstIf#= 4 IfCount= 2 Cls=02(comm.) Sub=02 Prot=00
A: FirstIf#= 6 IfCount= 2 Cls=02(comm.) Sub=0d Prot=00
A: FirstIf#= 8 IfCount= 2 Cls=02(comm.) Sub=0d Prot=00
A: FirstIf#=10 IfCount= 2 Cls=02(comm.) Sub=0d Prot=00
I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=cdc_acm
E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=02 Prot=00 Driver=cdc_acm
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=00 Driver=cdc_acm
E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I:* If#= 3 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=02 Prot=00 Driver=cdc_acm
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=00 Driver=cdc_acm
E: Ad=85(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=02 Prot=00 Driver=cdc_acm
E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 6 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0d Prot=00 Driver=cdc_ncm
E: Ad=87(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I: If#= 7 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
I:* If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=08(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 8 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0d Prot=00 Driver=cdc_ncm
E: Ad=89(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I: If#= 9 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
I:* If#= 9 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
E: Ad=8a(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0a(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#=10 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0d Prot=00 Driver=cdc_ncm
E: Ad=8b(I) Atr=03(Int.) MxPS= 64 Ivl=1ms
I: If#=11 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
I:* If#=11 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=01 Driver=cdc_ncm
E: Ad=8c(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0c(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#=12 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=01 Prot=00 Driver=(none)
E: Ad=8d(I) Atr=03(Int.) MxPS= 4 Ivl=125us
********************************************************************************************************
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 1
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 4.14
S: Manufacturer=Linux 4.14.167 ohci_hcd
S: Product=Generic Platform OHCI controller
S: SerialNumber=101c1000.ohci
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= 2 Ivl=255ms

Try setting the modem to use USBtty2 or USBtty1 or USBtty0 in the custom modem ports section under the modem menu. IT is seeing it, but its trying to use the wrong ports.

Also I think the WiFiX firmware is for the WE826Q, but not 100% sure.

for giggles try the straight goldenorb for the T2: http://ofmodemsandmen.com/download/GoldenOrb/16meg/we826-GO2020-03-01.zip

Change both communication port and modem data port to usb2? Thanks for feedback

I would. try 2, 1 or 0.

Tried all. Any other suggestions?

Different firmware on the router, posted above? It is newer.

Or even newer: Goldenorb regular version: http://ofmodemsandmen.com/upload/we826-GO2020-12-03.zip

I'm not super familiar with that brand modem, but I'll guess that it is using ports for the AT and data commands that the router isn't expecting.

So when I flashed the new firmware the modem actually showed up. When I restarted it said no modem again. Any ideas?

So now IG its recognizing the modem??? but its giving me these errors
Wed Jan 29 16:17:39 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:18:00 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:18:20 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:18:40 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:19:01 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:19:21 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:19:41 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:20:01 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:20:22 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:20:42 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:21:03 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:21:23 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:21:43 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:22:04 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:22:24 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:22:44 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

Wed Jan 29 16:23:05 2020 : /dev/ttyUSB80 AT+CPMS="SM"
ERROR

ITS WORKING!!! I believe my sim connection was not properly seated. For those wondering. The Fibocom L860 modem will work. God bless

*SOLVED:
For anyone having this issue. I believe this issue lies between three things.
1) The modem does not appear to be as compatible as other modems with the goldenorb software.
2) The sim has to be in the router for the modem to function. (Secure the sim with a good “sim-tray” adapter. My old one had wiggle room and it would not recognize the sim and modem)
3)The power supply should be upgraded as the default one coming with the router is not very good.
FIX:
For anyone having an issue with their Fibocom 860-GL and WE826-T2. Try these fixes.
-Download the newest software. This fixed a lot of the bugs I was experiencing.
(From what I am aware of GoldenOrbs website doesn’t show the latest versions of their software by default. You can find the latest version here: https://www.ofmodemsandmen.com/upload )
-Soft reboot the modem. You can do this by running this at command (AT+CFUN=1,1) As always at commands can brick your modem use them wisely.
-If the modem still will not show up make sure the sim is seated properly. Like mentioned previously check to make sure the sim seats snug in the router and make sure it is inserted properly. (Obviously lol)

* My modem keeps not detecting the modem on restarts. (THIS WAS BECAUSE OF THE SOFTWARE IF YOU DOWNLOAD THE NEW GOLDENORB VERSION IT FIXES THIS)

I have been running this setup for a month as of 2/20/21 and it works well.

The only downside to a fibocom modem is the lack of common at commands. Most people on this forum use a Sierra modem. Some at commands from the Sierra card will not translate to the fibocom. But if you can read the modem manual online which details its at commands you should be good!

Edited 2/20/21

How has it been working for you over the last week or so?

Currently setting up two systems here wg1608d
with a Sierra Wireless mc7354 The second system is a wg3526p with a Sierra Wireless em7565. Both systems show that same error. I have not yet inserted a sim card in either system yet due to finding out carrier of interest recently made changes. Guessing you need a working sim card to have access to the at commands and to show a modem connected.

Both routers acknowledge the modems but refuse to connect.. Exact same code lines as you.

When I get my sim cards I will report back on my expierence.

Both of my routers and modems are stock as of now, so no errors have been made yet as far as wrong at commands and such...lol

Gorilla

Without a SIM card it has no keys to the networks, so it cant get in the door, so to speak.

You got a point there. lol. Found out what my issues were. The com port was wrong , Had to use Putty to correct it. and then use some at commands on the at command. At least my 1608 router has been communicating with the modem correctly. Some reason my 3526 router has a issue with putty connecting on 192.168.1.1 on port 22. Says to network refused connection. It seems to be a common issue now in days with that putty error message. Had dissabled as much as I can regarding firewalls and such. At least I go the 1608 working. Seems like this issue Myself and others on here with Sierra Modems of any model type have comm issues with the router.

GORILLA

GORILLA wrote: Sun Jan 31, 2021 5:56 pm You got a point there. lol. Found out what my issues were. The com port was wrong , Had to use Putty to correct it. and then use some at commands on the at command. At least my 1608 router has been communicating with the modem correctly. Some reason my 3526 router has a issue with putty connecting on 192.168.1.1 on port 22. Says to network refused connection. It seems to be a common issue now in days with that putty error message. Had dissabled as much as I can regarding firewalls and such. At least I go the 1608 working. Seems like this issue Myself and others on here with Sierra Modems of any model type have comm issues with the router.

GORILLA

Did you make sure and set the admin/root webUI password? It wont allow SSH logins without the password set. I gotta ask

GORILLA wrote: Sun Jan 31, 2021 5:56 pm You got a point there. lol. Found out what my issues were. The com port was wrong , Had to use Putty to correct it. and then use some at commands on the at command. At least my 1608 router has been communicating with the modem correctly. Some reason my 3526 router has a issue with putty connecting on 192.168.1.1 on port 22. Says to network refused connection. It seems to be a common issue now in days with that putty error message. Had dissabled as much as I can regarding firewalls and such. At least I go the 1608 working. Seems like this issue Myself and others on here with Sierra Modems of any model type have comm issues with the router.

GORILLA

Hiya, hope this finds its way to you, where and what port did you set it to?

I too have a 1608 and have to date not been able to get anything to work in the m.2 port. Have been trying to get the Fibocom 860-GL to work but so far no luck! lsusb does not show anything either!

My WE862-T2 recognizes the Fibocom L860-GL modem but won't recognize a SIM being installed. Who has their 860-GL working and what FW version are you using?

NHeydary wrote: Sat Feb 17, 2024 11:20 pm My WE862-T2 recognizes the Fibocom L860-GL modem but won't recognize a SIM being installed. Who has their 860-GL working and what FW version are you using?

I would test the sim card in a phone first if you haven't done so already.
In rare cases SIM cards can go bad.

Ok, I didn't want to put the new SIM in there until I had the IMEI changed so I was using an old Verizon SIM that no longer has service. Would not having service make the SIM show up as "Missing"? Here's what I am seeing: https://1drv.ms/i/s!AjcwMUKGyqifgZ0rQFu ... w?e=Uk9quC

And, would it be bad if I put my Verizon phone SIM (I know it works) without changing the IMEI? I'm still in the process of figuring out how to change the IMEI of the Fibocom because the AT command that works for Quectel doesn't work for the Fibocom and there's not much available in terms of working magik.

NHeydary wrote: Sun Feb 18, 2024 7:39 pm Ok, I didn't want to put the new SIM in there until I had the IMEI changed so I was using an old Verizon SIM that no longer has service. Would not having service make the SIM show up as "Missing"? Here's what I am seeing: https://1drv.ms/i/s!AjcwMUKGyqifgZ0rQFu ... w?e=Uk9quC

Regardless if a sim is active or not, it shouldn't display "SIM Missing" in both a router or a phone.
You can safely insert your active sim into a phone for testing purposes, just to make sure you can make a call and go online.

Yea, the SIM is and has been working fine in my iphone for 18 months so the issue is with the router as it still shows SIM is Missing with the known working SIM is installed. I took the board out of the WE-826 and although the sticker on the bottom of the router says WE826-T2, the board says: ZBT-WE826-WD-V05. I'm wondering if the firmware I installed on the router (WE826-T2) is not correct and should be another one.

I installed the WE826-WD firmware and that made no change to the SIM Missing error.

NHeydary wrote: Tue Feb 20, 2024 2:21 am I installed the WE826-WD firmware and that made no change to the SIM Missing error.

Well, if the sim was working before in the router without any changes, then it's unlikely caused by the firmware.
As far as I know, the WE826-T2 is basically the same hardware as the WE826-WD, so try reflashing it with the WiFix WE826GO firmware.
https://drive.google.com/file/d/1omKTO7 ... d3vAyM5Kk/

Just because the sim has been working in your phone for 18 months, sim cards can go bad on rare occasions (happened to me), therefore it wouldn't hurt to retest it in a phone if you haven't done done so already (don't worry about the IMEI for a quick test). However, since you already tested the router with an inactive sim, even that should not display a "SIM missing error".

Have you been swapping the sim in and out of the router recently before displaying the error?
If so, it's possible that one of the sim contacts may have gotten damaged or broken off during swapping, or the sensor switch which tells the main board that a sim is inserted is not closing properly.
In order to eliminate a flaky contact, try covering the top of the sim adapter with one layer of transparent tape, and trim it around carefully with a scissor. If it still doesn't work, then apply a second layer, make sure to unplug and replug the router during each test.
Double check the orientation of the nano sim in the adapter to match up the beveled edge.
The adapter should go into the router upside down with the metal pins facing up and the beveled edge facing the router, making a click when pushed all the way in.

If still not working, then test if the modem is functioning properly by sending the following AT commands (all upper case) a couple of times each under Modem > Miscellaneous > AT-Command Terminal. You should get some response besides and error.
ATI
AT+GMM
If no response or an error, try clicking on Next Modem at the top right, wait a minute, then resend the AT commands again till you get a valid response. It would be helpful if you posted a device information log under Modem > Debug Information > Device Information