Hi, after problem solving and reading for the past couple of days I have to try the forum. What am I missing?
My setup:
- Sierra Wireless MC7700 mpcie (unlocked according to DC-unlocker, and I have two MC7700 I am playing with)
- RB922UAGS-5HPacD running ROS 7.10.2 (I have two of these as well)
- Winbox
- Sierra Wireless DIP-QMI switcher
- USB to mpcie adapter for Windows firmware flashing
Many of the guides and previous solutions don't work anymore, as MT has moved and renamed a lot of the LTE commands.
MC7700 Firmware:
Tried a lot of different firmware, and no difference, all of the DIP type:
- 03.05.20.03
- 03.05.23.02 (MC7710 just for kicks)
- 03.05.19.00
- 03.05.29.03
- 03.05.14.00
I can't flash if the modem if it is in DIP mode, I have to switch to QMI, flash and then switch back to DIP.
Using DIP (mbim)
- I can see the lte1 interface, but nothing happens when I enable it. LTE log shows nothing other than device enabled/disabled
- Trying some AT commands gives me the error "modem not ready"
Using serial mode
- ppp-out1 is created, and i can read the info of the modem from channel 3, most times
- I can establish a connection from channel 2, but no ip nor traffic is showing, but the status is connected and info show "GSM compact"
- IMSI says "Error"
- Operator is "Telenor Telenor (cellid: 17cf, lac: 2f4f"
Re: Another LTE noob having problems with MC7700
DIP/DirectIP is not MBIM in V7. But you'd want MBIM mode on Sierra if possible.
What I'm not sure is if MBIM is even support on the MC7700, I think so. So what does "AT!UDUSBCOMP=?" report when run from serial to the AT port of modem...
e.g. either serial console on your desktop ... OR if serial at least is appearing in RouterOS and info channel is correct (likely info-channel=2 on PPP)
/interface/ppp-client/at-chat [find] input="AT!UDUSBCOMP=?"
or with an LTE interface, you can try:
/interface/lte/at-chat [find] input="AT!UDUSBCOMP=?"
My guess is you need to do a AT!UDUSBCOMP=7 to get MBIM mode to show up on RouterOS – but those number vary by modem.... why the "=?" version of AT will show the possible USB configurations that are possible.
What I'm not sure is if MBIM is even support on the MC7700, I think so. So what does "AT!UDUSBCOMP=?" report when run from serial to the AT port of modem...
e.g. either serial console on your desktop ... OR if serial at least is appearing in RouterOS and info channel is correct (likely info-channel=2 on PPP)
/interface/ppp-client/at-chat [find] input="AT!UDUSBCOMP=?"
or with an LTE interface, you can try:
/interface/lte/at-chat [find] input="AT!UDUSBCOMP=?"
My guess is you need to do a AT!UDUSBCOMP=7 to get MBIM mode to show up on RouterOS – but those number vary by modem.... why the "=?" version of AT will show the possible USB configurations that are possible.
Re: Another LTE noob having problems with MC7700
Thank you for a quick response!
With serial:
[admin@MikroTik] > /interface/ppp-client/at-chat [find] input="AT!UDUSBCOMP=?"
output: AT!UDUSBCOMP=?
ERROR
but
[admin@MikroTik] > /interface/ppp-client/at-chat [find] input="AT"
output: AT
OK
With mbim:
[admin@MikroTik] > /interface/lte/at-chat [find] input="AT!UDUSBCOMP=?"
failure: modem not ready
DIP
Can I use DIP with v7?
With serial:
[admin@MikroTik] > /interface/ppp-client/at-chat [find] input="AT!UDUSBCOMP=?"
output: AT!UDUSBCOMP=?
ERROR
but
[admin@MikroTik] > /interface/ppp-client/at-chat [find] input="AT"
output: AT
OK
With mbim:
[admin@MikroTik] > /interface/lte/at-chat [find] input="AT!UDUSBCOMP=?"
failure: modem not ready
DIP
Can I use DIP with v7?
Re: Another LTE noob having problems with MC7700
QMI will not work. In theory, DIP (in Linux, CDC-ECM, or "DirectIP" in RouterOS v6) should work... And, I'd make sure you're on the latest firmware for sure. We know your modem's serial interface is taking commands, so that good.
And it's likely in DIP modem, since LTE is showing up – BUT I suspect the LTE interface might confused by that since it may expect a Sierra modem to be MBIM since all the new ones do NOT support DIP. e.g. the MC7700 is a weird one — one the first and last ones to support even DIP (or "DirectIP" or CDC-ECM in Linux as it's called in RouterOS V7) – they moved on MBIM pretty quick. And Mikrotik has never support Gobi/QMI protocol, which is the default, making it even trickier....
BUT my bad... you need to unlock the Sierra modems to use hardware commands – why the AT!UDUSBCOMP=? is not working – and critical to know what mode the sucker is in...
So if you use a BEFORE any of the other commands.
Then run the same:
And either report the output here.... or if you see "DIAG NMEA AT MBIM" next one (likely, but not sure, 7 in the list) that what you need in a "AT!UDUSBCOMP=7" command that switch it to MBIM modem (in which case physically unplug/replug power the unit to ensure it takes after doing it)...
Adding logging help too...
or to get even less clutter (and not using OR removing the previous one 
) the following will log even less LTE stuff:
Often some clue buried in the logs...
And it's likely in DIP modem, since LTE is showing up – BUT I suspect the LTE interface might confused by that since it may expect a Sierra modem to be MBIM since all the new ones do NOT support DIP. e.g. the MC7700 is a weird one — one the first and last ones to support even DIP (or "DirectIP" or CDC-ECM in Linux as it's called in RouterOS V7) – they moved on MBIM pretty quick. And Mikrotik has never support Gobi/QMI protocol, which is the default, making it even trickier....
BUT my bad... you need to unlock the Sierra modems to use hardware commands – why the AT!UDUSBCOMP=? is not working – and critical to know what mode the sucker is in...
So if you use a BEFORE any of the other commands.
Code: Select all
/interface/ppp-client/at-chat [find] input="AT!ENTERCND=\"A710\""Code: Select all
/interface/ppp-client/at-chat [find] input="AT!UDUSBCOMP=?"Adding logging help too...
Code: Select all
/system/logging add topics="lte,!packet" Code: Select all
/system/logging add topics="lte,!packet,!raw" Re: Another LTE noob having problems with MC7700
Here are the outputs, looks like mbim isn't supported?
Would downgrading to v6 solve this?
**UPDATE: ROS 6.49.8 works much better, I get an IP now on lte1. Trying to bridge lte1 and spf1 now, don't really know what I am doing
**UPDATE 2: I am stuck at "GSM Compact", don't know what it should be. Have not got them bridged yet either.
**UPDATE 3: After moving the setup upstairs I now get "Evolved 3G (LTE)". Got some traffic moving as well on lte1, will try to connect to internet soon
Would downgrading to v6 solve this?
**UPDATE: ROS 6.49.8 works much better, I get an IP now on lte1. Trying to bridge lte1 and spf1 now, don't really know what I am doing
**UPDATE 2: I am stuck at "GSM Compact", don't know what it should be. Have not got them bridged yet either.
**UPDATE 3: After moving the setup upstairs I now get "Evolved 3G (LTE)". Got some traffic moving as well on lte1, will try to connect to internet soon
Code: Select all
[admin@MikroTik] > /interface/ppp-client/at-chat [find] input="AT!ENTERCND=\"A710\""
output: AT!ENTERCND="A710"
OK
[admin@MikroTik] > /interface/ppp-client/at-chat [find] input="AT!UDUSBCOMP=?"
output: AT!UDUSBCOMP=?
0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS SUPPORTED
1 - HIP DM NMEA AT MDM1 MS NOT SUPPORTED
2 - HIP DM NMEA AT NIC1 MS SUPPORTED
3 - HIP DM NMEA AT MDM1 NIC1 MS SUPPORTED
4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS SUPPORTED
5 - HIP DM NMEA AT ECM1 MS SUPPORTED
6 - DM NMEA AT QMI NOT SUPPORTED
7 - DM NMEA AT RMNET1 RMNET2 RMNET3 NOT SUPPORTED
8 - DM NMEA AT MBIM NOT SUPPORTED
9 - MBIM NOT SUPPORTED
10 - NMEA MBIM NOT SUPPORTED
11 - DM MBIM NOT SUPPORTED
12 - DM NMEA MBIM NOT SUPPORTED
13 - Config1: comp6 Config2: comp8 NOT SUPPORTED
14 - Config1: comp6 Config2: comp9 NOT SUPPORTED
15 - Config1: comp6 Config2: comp10 NOT SUPPORTED
16 - Config1: comp6 Config2: comp11 NOT SUPPORTED
17 - Config1: comp6 Config2: comp12 NOT SUPPORTED
18 - Config1: comp7 Config2: comp8 NOT SUPPORTED
19 - Config1: comp7 Config2: comp9 NOT SUPPORTED
20 - Config1: comp7 Config2: comp10 NOT SUPPORTED
21 - Config1: comp7 Config2: comp11 NOT SUPPORTED
22 - Config1: comp7 Config2: comp12 NOT SUPPORTED
OKRe: Another LTE noob having problems with MC7700
Hmm. RouterOS make guesses on the port mapping based on the USB device ID...
So V6 does not support MBIM modems, so it only looks for DirectIP modems. So from the MC7700 USB device ID, it knows it DIP.
Under V7, it support both DirectIP and MBIM modes. But I'm guess it's assuming the MC7700 USB device ID are for a MBIM modem – and, generally, that's what you'd want for the Sierra modems. So it's not likely looking/trying DIP with for that deviceID. And, while you can force MBIM in the LTE settings, you can't force DirectIP/CDC-ECM in V7.
The normal solution be switch the modem to MBIM mode. But seems your modem does not support MBIM, at least based on the output. If you're happy with V6, that may be best.
But if you want to try V7 again... I suppose you can try the AT!ENTERCND command to unlock the modem, then try setting AT!UDUSBCOMP=8 – but I suspect that will return an error since your =? output shows =8 as "NOT SUPPORTED".
SO...you may need to file a bug at help.mikrotik.com. They may know the right AT!UDPID to set to get RouterOS v7 to recognize the MC7700 as DirectIP. If you file a ticket, you'll need to try V7 again, and generate a supout.rif. Make sure to add logging suggested above, reboot, and then generate a supout.rif after the reboot – that will have the extra logs during initialization Mikrotik may need.
So V6 does not support MBIM modems, so it only looks for DirectIP modems. So from the MC7700 USB device ID, it knows it DIP.
Under V7, it support both DirectIP and MBIM modes. But I'm guess it's assuming the MC7700 USB device ID are for a MBIM modem – and, generally, that's what you'd want for the Sierra modems. So it's not likely looking/trying DIP with for that deviceID. And, while you can force MBIM in the LTE settings, you can't force DirectIP/CDC-ECM in V7.
The normal solution be switch the modem to MBIM mode. But seems your modem does not support MBIM, at least based on the output. If you're happy with V6, that may be best.
But if you want to try V7 again... I suppose you can try the AT!ENTERCND command to unlock the modem, then try setting AT!UDUSBCOMP=8 – but I suspect that will return an error since your =? output shows =8 as "NOT SUPPORTED".
SO...you may need to file a bug at help.mikrotik.com. They may know the right AT!UDPID to set to get RouterOS v7 to recognize the MC7700 as DirectIP. If you file a ticket, you'll need to try V7 again, and generate a supout.rif. Make sure to add logging suggested above, reboot, and then generate a supout.rif after the reboot – that will have the extra logs during initialization Mikrotik may need.
Re: Another LTE noob having problems with MC7700
Thanks for the continued problem solving!
I would like to use the newest version of all software, including ROS. I have upgraded to v7.11, enabled logging and created a supout.rif after a reboot and submitted a bug.
I did try AT!ENTERCND and thereafter AT!UDUSBCOMP=8, but i got an error on the last command, as expected.
I would like to use the newest version of all software, including ROS. I have upgraded to v7.11, enabled logging and created a supout.rif after a reboot and submitted a bug.
I did try AT!ENTERCND and thereafter AT!UDUSBCOMP=8, but i got an error on the last command, as expected.
Re: Another LTE noob having problems with MC7700
Maybe file a bug at help.mikrotik.com?
I think the issue is the MC7700 uses the same USB IDs as the other things in the 77xx family – but MC7710,7354,7455 do NOT support DIP, only MBIM. This is likely confusing V7 since it finds detect the modem, but I think it trying to use MBIM even though it's not supported.
Basically modems work in three modes: serial/PPP, CDC-ECM (aka DIP, DirectIP), and MBIM – but there is no "hey I'm MBIM" messages or anything in USB to the OS. RouterOS/linux has to use USB IDs to know what how USB channels map to know what USB channel# to use for things. BUT modems, Sierra in particular, have a bunch of possible USB channel maps (e.g. the options you see in AT!UDUSBCOMP) for the same USB Device ID...this make is hard for RouterOS/linux since only the modem knows the channel map.
But you can change the USB IDs on the Sierra so your MC7700 look different. I just know know what value you'd need to use a AT!UDPID=XX command to change them that cause Mikrotik to know it's a DIP (CDC-ECM) modem. But Mikrotik would, why a ticket may be a good idea here.
I think the issue is the MC7700 uses the same USB IDs as the other things in the 77xx family – but MC7710,7354,7455 do NOT support DIP, only MBIM. This is likely confusing V7 since it finds detect the modem, but I think it trying to use MBIM even though it's not supported.
Basically modems work in three modes: serial/PPP, CDC-ECM (aka DIP, DirectIP), and MBIM – but there is no "hey I'm MBIM" messages or anything in USB to the OS. RouterOS/linux has to use USB IDs to know what how USB channels map to know what USB channel# to use for things. BUT modems, Sierra in particular, have a bunch of possible USB channel maps (e.g. the options you see in AT!UDUSBCOMP) for the same USB Device ID...this make is hard for RouterOS/linux since only the modem knows the channel map.
But you can change the USB IDs on the Sierra so your MC7700 look different. I just know know what value you'd need to use a AT!UDPID=XX command to change them that cause Mikrotik to know it's a DIP (CDC-ECM) modem. But Mikrotik would
, why a ticket may be a good idea here.Re: Another LTE noob having problems with MC7700
I did and they are working on it 
Re: Another LTE noob having problems with MC7700
Yeah... I only know about this since we had a couple MC7700 many years ago...upgraded to using MC7354s etc and found those do NOT support DIP/DirectIP. So any "modern" Sierra modem, other than the MC7700, did not work V6 since it does not have MBIM support. So, yeah, the reverse problem makes sense
Re: Another LTE noob having problems with MC7700
Great news!
Mikrotik uploaded a custom fw to my RB, and now the MC7700 is detected properly as an LTE interface.
I will test it further tomorrow.
**UPDATE: How do I connect spf1 to lte1? Tried some scripts I found on the inteweb, but I don't really understand what they are doing and hence I can't really correct them when they don't work:
**Update 2: Got it on the interweb, used quick set and added a masquerade from the lines below. Stuck at "GSM Compact" for now, even as the signal strength is "excellent",
Mikrotik uploaded a custom fw to my RB, and now the MC7700 is detected properly as an LTE interface.
I will test it further tomorrow.
**UPDATE: How do I connect spf1 to lte1? Tried some scripts I found on the inteweb, but I don't really understand what they are doing and hence I can't really correct them when they don't work:
**Update 2: Got it on the interweb, used quick set and added a masquerade from the lines below. Stuck at "GSM Compact" for now, even as the signal strength is "excellent",
Code: Select all
/interface bridge
add name=bridge1
/ip pool
add name=dhcp_pool1 ranges=192.168.100.2-192.168.100.254
/ip dhcp-server
add address-pool=dhcp_pool1 disabled=no interface=bridge1 lease-time=1d name=dhcp1
/interface bridge port
add bridge=bridge1 interface=sfp1
/ip address
add address=192.168.100.1/24 interface=bridge1 network=192.168.100.0
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether1
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=lte1
/ip dhcp-server network
add address=192.168.100.0/24 gateway=192.168.100.1
/ip firewall filter
add action=drop chain=output comment="Drop pings to8.8.8.8 if they go through proximus" dst-address=8.8.8.8 out-interface=lte1
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1
add action=masquerade chain=srcnat out-interface=lte1
/ip route
add comment=telenet distance=1 gateway=192.168.0.1 scope=11
add comment=proximus distance=10 gateway=192.168.9.1
add comment="Force test pings through telenet" distance=1 dst-address=8.8.8.8/32 gateway=192.168.0.1Re: Another LTE noob having problems with MC7700
I have now gotten LTE connectivity, but with very poor signal strength and 20/2 mbps speed. I have some DNS issues as well that I don't know how to solve.
Re: Another LTE noob having problems with MC7700
Glad they fixed it. I'm actually not sure what LTE stats be shown however, in MBIM mode with Sierra you'd only get an RSSI value to know signal strength. Maybe in DirectIP/DIP/ECM mode you'd get more, since these were support in V6 pretty well and that carried over – dunno.
And since you're likely very familar with "at-chat" now... "AT!GSTATUS?" will display a range of LTE statics. This will run it in a loop so you can see it changing:
viewtopic.php?t=186137#p995230
(you likely can remove the AT!LTEINFO? one – that's a newer command that very likely not on the MC7700)
It could also be the antenna configuration and/or position – but if you post the AT!GSTATUS? that help know what the modem things of the RF.
Do you have BOTH antennas wired up? If you're using terminal antennas, make sure they're at 90º to each (e.g. like TV rabbit ears from 1970s) to get MIMO effects. If you ran a couple other commands like "AT!CUSTOM?", "AT!RXDEN?", and "AT!BAND?" that be helpful to know the config of modem. But assuming you have BOTH antenna wired up, may need to set "AT!RXDEN=1" – but be good know what it was before (e.g. if it was only using primary antenna, that explain speed). (To run any of these, you need the ENTERCND AT command first)
FWIW, I wrote up how to enable GPS – imagine it work similar on MC7700:
viewtopic.php?p=1011191&hilit=sierra#p1011191
And since you're likely very familar with "at-chat" now... "AT!GSTATUS?" will display a range of LTE statics. This will run it in a loop so you can see it changing:
viewtopic.php?t=186137#p995230
(you likely can remove the AT!LTEINFO? one – that's a newer command that very likely not on the MC7700)
It could also be the antenna configuration and/or position – but if you post the AT!GSTATUS? that help know what the modem things of the RF.
Do you have BOTH antennas wired up? If you're using terminal antennas, make sure they're at 90º to each (e.g. like TV rabbit ears from 1970s) to get MIMO effects. If you ran a couple other commands like "AT!CUSTOM?", "AT!RXDEN?", and "AT!BAND?" that be helpful to know the config of modem. But assuming you have BOTH antenna wired up, may need to set "AT!RXDEN=1" – but be good know what it was before (e.g. if it was only using primary antenna, that explain speed). (To run any of these, you need the ENTERCND AT command first)
FWIW, I wrote up how to enable GPS – imagine it work similar on MC7700:
viewtopic.php?p=1011191&hilit=sierra#p1011191
Re: Another LTE noob having problems with MC7700
Might also post your config. But I think if signal is bad, then DNS be flaky is my thought.
Re: Another LTE noob having problems with MC7700
Here are the outputs of the commands:
I have two similar antennas, and one big one. Currently using the two small ones. They are not "grounded" to each other as my case is 3d-printed. Is that a problem?
I have been trying different configurations of the antennas:
- Both straight up
- One up and one straight out
- Same as the one over, but the flat one rotated 90 degrees
- As a V
- As an upside down V
- Far appart
There are small changes, but nothing giving me any good coverage.
There is a lot of info in the web fig, see attachment.
Code: Select all
[admin@MikroTik] > /interface lte at-chat lte1 input="AT!GSTATUS?"
output: !GSTATUS:
Current Time: 1225 Temperature: 49
Bootup Time: 1 Mode: ONLINE
System mode: LTE PS state: Attached
LTE band: B1 LTE bw: 20 MHz
LTE Rx chan: 300 LTE Tx chan: 18300
EMM state: Registered Normal Service
EMM connection:RRC Connected
RSSI (dBm): -86 Tx Power: 21
RSRP (dBm): -118 TAC: 81A4 (33188)
RSRQ (dB): -10 Cell ID: 03222308 (52568840)
SINR (dB): -4.8
OK
[admin@MikroTik] > /interface lte at-chat lte1 input="AT!CUSTOM?"
output: !CUSTOM:
PUKPRMPT 0x01
ISVOICEN 0x02
PRLREGION 0x04
PCSCDISABLE 0x07
GPSENABLE 0x01
CSVOICEREJECT 0x02
GPSLPM 0x01
GPSSEL 0x01
ROAMRATDIS 0x04
OK
[admin@MikroTik] > /interface lte at-chat lte1 input="AT!RXDEN?"
output: !RXDEN:
01
OK
[admin@MikroTik] > /interface lte at-chat lte1 input="AT!BAND?"
output: Index, Name, GW Band Mask L Band Mask
00, All bands, 000000000CE80380 0000000000010009
OK
I have two similar antennas, and one big one. Currently using the two small ones. They are not "grounded" to each other as my case is 3d-printed. Is that a problem?
I have been trying different configurations of the antennas:
- Both straight up
- One up and one straight out
- Same as the one over, but the flat one rotated 90 degrees
- As a V
- As an upside down V
- Far appart
There are small changes, but nothing giving me any good coverage.
There is a lot of info in the web fig, see attachment.
You do not have the required permissions to view the files attached to this post.
Re: Another LTE noob having problems with MC7700
My config:
Code: Select all
# 2023-08-18 20:38:48 by RouterOS 7.12alpha92
# software id = **ELIDED**
#
# model = RB922UAGS-5HPacD
# serial number = **ELIDED**
/interface bridge
add admin-mac=**ELIDED** auto-mac=no comment=defconf name=bridge
/interface wireless
set [ find default-name=wlan1 ] frequency=auto installation=outdoor mode=ap-bridge ssid=**ELIDED**
/interface ethernet
set [ find default-name=sfp1 ] auto-negotiation=no
/interface list
add name=WAN
add name=LAN
/interface lte apn
set [ find default=yes ] apn=telenor.smart use-network-apn=no
add apn=telenor.smart name=Telenor
/interface lte
set [ find default-name=lte1 ] apn-profiles=Telenor
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.1.200-192.168.1.205
/ip dhcp-server
add address-pool=dhcp interface=bridge name=dhcp1
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=sfp1
add bridge=bridge comment=defconf interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add interface=lte1 list=WAN
add interface=bridge list=LAN
/ip address
add address=192.168.1.1/24 interface=bridge network=192.168.1.0
/ip dhcp-client
add comment=defconf interface=bridge
/ip dhcp-server network
add address=0.0.0.0/24 dns-server=0.0.0.0 gateway=0.0.0.0 netmask=24
add address=192.168.1.0/24 dns-server=192.168.1.1 gateway=192.168.1.1 netmask=24
/ip dns
set allow-remote-requests=yes
/ip firewall filter
add action=accept chain=input protocol=icmp
add action=accept chain=input connection-state=established
add action=accept chain=input connection-state=related
add action=drop chain=input in-interface-list=!LAN
/ip firewall nat
add action=masquerade chain=srcnat out-interface-list=WAN
add action=masquerade chain=srcnat out-interface=lte1
/system clock
set time-zone-name=Europe/Oslo
/system note
set show-at-login=no
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
Last edited by tangent on Fri Aug 18, 2023 9:42 pm, edited 1 time in total.
Reason: Elided sensitive information
Reason: Elided sensitive information
Re: Another LTE noob having problems with MC7700
Yeah when in DIP/DirectIP mode... RouterOS shows the needed cell signals — that helps here.
The RSRP is what I'd focus on first – -118 is virtually unusable. Even -110 is pretty bad. It's so low, that if you in a city and/or "close" to some towers, that would point to the antennas/connectors to modem. If you are actually some distance from cell towers/civilization, where you might expect a weak signal...you option there is to get a bigger antennas (or perhaps ones tuned for ~1900MHz)
But I'm not the hardware or antenna guy... But guessing a plastic case have no "ground plane".... So playing with the orientation of antenna is unlikely to change the RSRP that dramatically — that -118 RSRP is just very weak.
Keep in mind it takes at least 10 or more seconds for signals to update after "doing something". In fact waiting 30 seconds to verify a change in signal from doing something is likely a good idea... e.g. modem talks to tower, modem has to process, and then routeros polls the data periodically – so it's not instantaneous on the signal levels.
The RSRP is what I'd focus on first – -118 is virtually unusable. Even -110 is pretty bad. It's so low, that if you in a city and/or "close" to some towers, that would point to the antennas/connectors to modem. If you are actually some distance from cell towers/civilization, where you might expect a weak signal...you option there is to get a bigger antennas (or perhaps ones tuned for ~1900MHz)
But I'm not the hardware or antenna guy... But guessing a plastic case have no "ground plane".... So playing with the orientation of antenna is unlikely to change the RSRP that dramatically — that -118 RSRP is just very weak.
Keep in mind it takes at least 10 or more seconds for signals to update after "doing something". In fact waiting 30 seconds to verify a change in signal from doing something is likely a good idea... e.g. modem talks to tower, modem has to process, and then routeros polls the data periodically – so it's not instantaneous on the signal levels.
Re: Another LTE noob having problems with MC7700
Tried another MC7700, same results.
My iPhone has 5 bars, but uses channel 20 ( 800 MHz). The nearest cell tower is 1,1 km away, in sight.
Will test another pair of antenna connectors now.
My iPhone has 5 bars, but uses channel 20 ( 800 MHz). The nearest cell tower is 1,1 km away, in sight.
Will test another pair of antenna connectors now.
Re: Another LTE noob having problems with MC7700
Yeah guessing the MC7700 doesn't have B20... I think a "AT!BAND=?" would tell you the supported ones (although it might be AT!GBAND=? in that modem)
Just because you can see a tower, doesn't mean the 1900Mhz sector is pointing your direction.
Just because you can see a tower, doesn't mean the 1900Mhz sector is pointing your direction.
Re: Another LTE noob having problems with MC7700
According to coverage maps we should have good LTE and LTE+ coverage here.
Code: Select all
[admin@MikroTik] > /interface lte at-chat lte1 input="AT!BAND=?"
output: Index, Name, GW Band Mask L Band Mask
00, All bands, 000000000CE80380 0000000000010009
01, Europe 3G, 0000000000400000 0000000000000000
02, North America 3G, 0000000004800000 0000000000000000
03, Europe 2G, 0000000000000380 0000000000000000
04, North America 2G, 0000000000280000 0000000000000000
05, GSM ALL, 0000000000280380 0000000000000000
06, Europe, 0000000000400380 0000000000000001
07, North America, 0000000004A80000 0000000000010008
08, WCDMA ALL, 000000000CC00000 0000000000000000
09, LTE ALL, 0000000000000000 0000000000010009
0000000000010000 - B17
0000000000000008 - B4
0000000000000001 - B1
0000000008000000 - B6 (800)
0000000004000000 - B5 (850)
0000000000800000 - B2 (1900)
0000000000400000 - B1 (2100)
0000000000200000 - G1900
0000000000080000 - G850
0000000000000200 - G900P
0000000000000100 - G900E
0000000000000080 - G1800
OK
Re: Another LTE noob having problems with MC7700
As I said I'm not the RF guy. Your down to me suggestion aluminum foil around the 3D-printed plastic case...
Issue is your phone is using Band 20, which is getting good signal. But since we do NOT know what Band 1 is reading on your phone, there is nothing to compare with the MC7700... e.g. To know if your antennas OR just Band 1 isn't good were you at.
Your MC7700 doesn't have B20 & so it cannot use a band it doesn't support... The bottom of the AT!BAND=? shows the supported bands.
Issue is your phone is using Band 20, which is getting good signal. But since we do NOT know what Band 1 is reading on your phone, there is nothing to compare with the MC7700... e.g. To know if your antennas OR just Band 1 isn't good were you at.
Your MC7700 doesn't have B20 & so it cannot use a band it doesn't support... The bottom of the AT!BAND=? shows the supported bands.
Re: Another LTE noob having problems with MC7700
Fair point
My big 4g antenna supports bands 3, 7, 8, 20 and 38. Frequency bands 700-900 MHz, 1800-2100 MHz and 2400-2700 MHz.
I have been thinking about the foil myself. Fixed my DAB radio problems, but don't win any WAF awards.
Do I need two equal antennas to utilise MIMO? My big 4g antenna has 5 meters of cord, should (hopefully) be plenty to get away from any noise generated by the RB.
The next rabbit hole is GNU Radio and my SDR to figure out which bands are available. Until recently the government had an overview on the interweb, which showed placement, operators and frequencies of all base stations in the country. But the current situation in Europe led to the removal of those maps.
My big 4g antenna supports bands 3, 7, 8, 20 and 38. Frequency bands 700-900 MHz, 1800-2100 MHz and 2400-2700 MHz.
I have been thinking about the foil myself. Fixed my DAB radio problems, but don't win any WAF awards.
Do I need two equal antennas to utilise MIMO? My big 4g antenna has 5 meters of cord, should (hopefully) be plenty to get away from any noise generated by the RB.
The next rabbit hole is GNU Radio and my SDR to figure out which bands are available. Until recently the government had an overview on the interweb, which showed placement, operators and frequencies of all base stations in the country. But the current situation in Europe led to the removal of those maps.
Who is online
Users browsing this forum: No registered users and 4 guests