E3372h-607 in stick mode on Beryl AX (MT3000) not working / unreliable connection

Hi

@alzhao,

I had a read of this GL-AXT1800 with e3372h in stick mode. No comgt-ncm package but it does not seem to be resolved. I flagged that thread back in Nov 22. Do we still need to add " package luci-proto-ncm in repository"?

Well I finally got around to converting my Huawei E3372h-607 to stick mode, now I have all the steps and all the software (Huawei Drivers, Balong usbloader, FW Update) that I need to do that as well as to out back the Orig IMEI (DC Unlocker) and Serial number (HxD). Was quite a journey, but that’s another story…

Note that in stick mode I do not have the DHCP issue with 192.168.8.1 conflicts that are mentioned here often.

So then I was put it into the USB Port of my Beryl AX (MT 3000) in the misguided hope it would all work first time. Well…nope. It recognises the modem OK, serial is correct, even got it to connect once (solid blue light) and I can’t remember which setting that was on, auto or some attempt at manual.

Anyway I tried auto and got the various screens below. It seemed to conenct once (not sure what the 3 means, it is 3HK though), but then there was no internet (except one time as shown) but it invariably disconnects. Very unstable.

So I went into Manual settings but I realy have no idea in the slightest what I am looking at. One observation was that everytime I entered the Manual screen for a look it had changed to a different Protocol, like it was cycling through them, NCM, then QCM then QMI. I did not select those myself.

I checked the APN settings for 3HK but they were OK. The only setting I was brave enough to try was TTL 65 but no change.

I downloaded some logs as attached.

So, how can I can help troubleshoot this?



Bottom

Modem-Debug.zip (919 Bytes)

k.

E3372h is not yet fully supported. I will pay attention to the issue.

1 Like

OK I look forward to it; btw because I converted it to “Stick Mode”, it is now actually an E3372s.
With that in mind, can I assume your answer is the same?

Over a month on, any updates on this please?

We have done some debugging. The results of the current test require a specific card to occasionally link successfully.

This seems a bit cumbersome at the moment. We will continue this work if future conditions permit.

2 Likes

Hi six months on - any updates please?

I'm also considering to get an E3372s (stick mode). @SmurfonToast Any update on whether this should work?

Hi,

No, GLiNET support still hasn’t come back on this one.

Seems like a little fish. :tropical_fish:.

k.

hmm, I just received a E3372h-607, and it seems to be already converted to stick mode (plugging it to a PC prompts me to install the Mobile Partner app).

when I plug it to the Beryl AX, it works after the "Auto Setup" process. However the Beryl fails to detect the carrier name, and therefore SMS doesn't work.

1 Like

Out of interest if you install the mobile partner app on your PC, can you send SMS? Just to test the SIM works?

The SIM works seamlessly with the Puli (XE300), even receiving/sending SMS.

Regarding the E3372 (in stick mode), I finally found a way to make it work consistently. Here: GL-MT3000 and HUAWEI E3372 - #12 by kentnek

The modem now connects automatically after plugging into the MT3000 too!

1 Like

Awesome, thank you. I will give it a try (with the SMS tool in Luci too).

@alzhao @ywp it’d be great if you could integrate kentnek’s solution to getting the E3372 (stick mode) recognized natively in the GLiNet Beryl using the AT command he refers to in the post (I.e, Force the modem only mode using

AT^SETPORT="FF;10,12,16"

Also, as he suggested, please consider putting the SMS function in the GUI.

:pray:

Hello @SmurfonToast here is a beta version 4.8 for Beryl AX. Could you update your Beryl AX to this version? Then see if you can get the E3372 (stick mode) work properly.

Hi Cathy,

Thanks for that, I am actually already running that beta 4.8.0 since the 18th April.
Thank you.

I am not sure what it was like before the Beta TBH (I tried this modem a few years ago, even sent @alzhao a few E3372 Modems to play with, (one E3372h and one E3372s (that was 'h', HiLink, until I used the needle method to turn it into stick mode).

I gave up at the time TBH, but thought I would try again after seeing this threads development, with details from @kentnek.

The modem works, sms-tools works, USSD Works (but actually causes the modem to stop responding) and I am not experienced enough to know what command to issue to check what mode it is actually in, AT^SETPORT="FF;10,12,16" seems to stick if I check with AT^SETPORT?, but whether it is in a stick-mode or not is hard to work out.

The USSD uses ports /dev/ttyUSB* but in this post @kentnek stated it will use /dev/cdc-wdm0. I am still unsure of the method used to check this.

You can select the cellular protocol and port in FW v4.8, as shown below, and then see if it works

Regarding the SMS plug-in, we will take a look.

Hi Cathy,

Unfortunately that interface does not show up on my unit, on the GLiNET GUI; despite (see attachments), /dev/cdc-wdm0 showing up in both sms-tools and on the CLI when I issue these commands:

ls /dev/c*
ls /dev/ttyUSB*

Hello, just want to confirm, can your device work properly without using /dev/cdc-wdm0?
Could the cellular information (including the name of the operator, IP address, etc.) displayed on the GL.iNet Web GUI be shown correctly and accurately?

Yes. But the speed is not so great. I’m not sure how much is provider and how much not being in modem only mode (if that is the case).

You can modify the MTU value and set it to 1428 to see if you can get a better speed.

Ok I will try that. But no update on this interface

/dev/cdc-wdm0

not showing up in the main GUI?