Modem gobi firmware: Difference between revisions
Created page with "== Summary == Gobi firmware is pretty much the last resort of getting modem to work in RouterOS. If is does not support modes/drivers like: AT, cdc-ecm, mbim (ros v7). Supp..." |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
* gobi2000 | * gobi2000 | ||
Not supported: | Not supported (not tested): | ||
* gobi3000 | * gobi3000 | ||
| Line 36: | Line 36: | ||
Client waits for new RouterOS development build to become available in MikroTik download page. And checks it with gobi drivers | Client waits for new RouterOS development build to become available in MikroTik download page. And checks it with gobi drivers | ||
Details on which gobi version modem firmware uses and the firmware should be obtainable through modem manufacturer vendor support page or possibly through operator from which user got the modem (if that's the case). | |||
Gobi firmware files that needs to be uploaded to router: | Gobi firmware files that needs to be uploaded to router: | ||
Latest revision as of 11:57, 19 August 2015
Summary
Gobi firmware is pretty much the last resort of getting modem to work in RouterOS. If is does not support modes/drivers like: AT, cdc-ecm, mbim (ros v7).
Supported gobi versions:
- gobi1000
- gobi2000
Not supported (not tested):
- gobi3000
- gobi4000
- gobi5000
- newer ones.
Note: RouterOS supports only gobi serial option, other gobi modes are not supported.
Procedure on how to check if gobi option is available
Step 1
Client tries to use some modem, but after plugging it in device which is running latest RouterOS release it does not show up as ppp or lte interface.
Client generates supout file on that device where modem is mounted and sends it to MikroTik support.
Step 2
MikroTik support checks what options are available to try adding support for this device. IF is modem supports only gobi then we add initial support. And notify client that he should try next development build or ROS with gobi drivers.
Step 3
Client waits for new RouterOS development build to become available in MikroTik download page. And checks it with gobi drivers
Details on which gobi version modem firmware uses and the firmware should be obtainable through modem manufacturer vendor support page or possibly through operator from which user got the modem (if that's the case).
Gobi firmware files that needs to be uploaded to router:
- amss.mbn
- apps.mbn
- UQCN.mbn // >gobi1000
When files are uploaded to router in: port -> firmware menu there will be option to enter path to firmware files.
System should now start the firmware, modem hardware id's should change when the gobi firmware is loaded.
Step 4
User should then generate new supout file and send it again to MikroTik support (ideally as reply to original ticket).
Step 5
MikroTik support receives the new supout and checks what last changes need to be added. Then if everything goes as planned, changes in software is made and support notifies client to wait for fresh development build.
Step 6
Client waits for new ROS build and checks how modem responds there. Hopefully now modems works.