it should be on auto gear recognize, dialing and connect,.

which version rooter you are using ?

latest version - Huntsman 2013-10-16red

yes, it used to be working well, but recently it fail, and i thought tower issue, until i swap e1550 it works well
try e398 on computer, it works well.

from the system log, its saying failed to connect.

Try the latest E398 firmware in case you haven't

http://blacktubi.com/files/E398%20Firmware...33.61.10.55.exe

alright.... will try

blacktubi after updated to new firmware, it looks good, and connection stick for 3 hours without any dc.
just that rooter modem information cant show any info, thats fined for me, as long as the connection is up....
thank you for your help.

if u using rooter, under modem -> network status u need to find correct port for the communication, go to modem tab -> support -> communication port -> try either ttyUSB0 or ttyUSB1 or ttyUSB2 -> click save and apply

or u can go to modem tab -> network status -> decrease or increase port till u see the info display out

,. confirm either one of these port will work

This post has been edited by chuahcs79: Nov 8 2013, 09:24 PM

i did a router reboot, it works again...

sometimes the communication port run away between those 3 port,. so once u reboot, it will restart the recognize process again...

just manual decrease or increase the port will do the job

Anyone is using 2013-11-10 red?
I was trying just now, with my E398.
It is super lag, 3000ms ping and 1.xx dl speed.

no problem on my WR710N, MR3020 or MR3420V1. Running more than 24 hours already.

it was fine running with my V2 with E3276 on the 2013-11-10 red

Seem like the problem is on my side.
Maybe will reflash again when i am free later.
Thanks all.

so far no issue for me, probably u might want to check your modem E398 whether the firmware is up to date, and the rooter reflashed again

after i update my modem, my TL-MR3420 cannot detect my modem. and doing AT command also doesn't help


but weird thing is, when using stock firmware modem can detect like normal

is there anything i miss here? currently using openwrt-mr3420-v2-HM2013-11-10red firmware

Use yellow then

Red always feel funny to me

Wait at least 5 minutes for initial detection

i am using the red latest version though, yellow one totally failed on the E3276 ,

yellow also cannot detect, even after several reboot

I have the same situation with you, tested using E398 & mr3420 v2, happening twice
If someone can re-upload the Huntsman 2013-10-16red & 2013-10-12 for mr3420 v2?
This is the more stable version.

Need to flash back to stock firmware.
Then flash back to 2013-11-10red or 2013-11-10 (yellow)
I can confirm 2013-11-10red or 2013-11-10 (yellow) a bit buggy

i have Huntsman 2013-10-16red, but also cannot detect.

maybe need to downgrade modem firmware?

This post has been edited by syahpian: Nov 12 2013, 12:22 AM

what about stock firmware ? cannot performs with your E398 ?