Opale Wiki - User contributions [en]

Release notes

2026-05-28T14:55:00Z

Administrator: /* Base firmware History (Most recent first): */

== Base firmware History (Most recent first): ==

==== opale-1.0-605003-2026-05-25.bin ====

* Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.
* Default password is now : root/admin
* Add /etc/opale-build file which contains build file name
* MAC address and Serial number are preserved during firmware update
* Provide additional utilies : setmac, getserialno, atcmdb, qpower, modscan, modinf, netinfo
* update SSH banner with Opale's name and unit serial number
* breed is no longer required as U-boot, as setmac utility can be used to set mac address.

==== xxxxxx-WS1688AX-GO2026-05-07-upgrade.bin ====

* Fix reboot problem on WS1688 latest motherboard.
* Update Plug & Play files for proper detection of EG25-G M.2 modules

==== xxxxxx-WS1688AX-GO2025-05-28-upgrade.bin ====

* First documented firmware release.

== Opale R2D2 Software history (Most recent first): ==

==== Version 1.1 - 2026-04-01 ====
TBA

==== Version 1.0 - 2025-05-28 ====
First initial GA release. Includes:

* gsmrobotd_0.9.29_mipsel_24kc.ipk
* gsmuxsvc_0.9.8_mipsel_24kc.ipk
* r2d2_0.9.9_mipsel_24kc.ipk
* r2d2config_0.9.9_mipsel_24kc.ipk

Quectel RM520N Firmware Update (New)

2026-04-27T15:33:14Z

Administrator:

This page describes how to update the firmware of any of the Quectel RM520N modems within the Opale 5G Robot.

'''In the following, it is assumed the Opale 5G Robot is properly configured and accessible through IP.'''

Note that the procedure described in this page will be obsoleted when Modem updates will be integrated in the Opale Robot firmware.

[[File:Robots_Slots.jpg|394x394px]]

The Opale 5G Robot can include one or two RM520N (Among other possible configurations) modem(s) as illustrated in the above picture.

In order to '''SAFELY''' upgrade any modem from the Opale 5G Robot, this procedure needs to be carefully followed.

'''This procedure describes updating one RM520N at a time.'''

First, the new RM520N modem firmware has to be downloaded on the Robot using a SFTP client.
[[File:Firmware Uploaded.png|thumb|606x606px|none]]The picture above shows where the Quectel RM520N Update file has to be downloaded.

Once this is done, the RM520N Update file need to be unzipped with the following command:<syntaxhighlight lang="termcap">
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 22.03-SNAPSHOT, r0-031ace73
-----------------------------------------------------
root@ROBOT2p:~# cd /mnt/sdcard
root@ROBOT2p:/mnt/sdcard# unzip RM520N*
Archive: RM520NGLAAR03A04M4G_01.204.01.204.zip
inflating: md5.txt
<...>
inflating: update/firehose/partition_complete_p4K_b256K.mbn
inflating: Quectel_RM520N-GL-AA_Firmware_Release_Notes_V0304_01.204.01.204.pdf
root@ROBOT2p:/mnt/sdcard#
</syntaxhighlight>The system should then be prepared with the following commands:

* The first one stops the robot software,
* and the second one power up the modem, so that we can set it up later.
<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# sc stop all
root@ROBOT2p:/mnt/sdcard# echo "1" > /sys/class/gpio/mdm_pwr/value

</syntaxhighlight>Then run the microcom terminal utility to enter AT commands to the RM520N modem (you may have to wait a few seconds so that the modem is ready):<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# microcom /dev/COM3
</syntaxhighlight>Then enter the following AT command to reconfigure the USB interface of the modem<syntaxhighlight lang="termcap">
at+qcfg="usbcfg",0x2c7c,0x0801,1,1,1,1,1,0,0
at+cfun=1,1

</syntaxhighlight>You may have to enter <control-x> in order to exit the microcom terminal utility.

Then the module can be updated with the following commands:<syntaxhighlight lang="termcap">
root@ROBOT2p: cd /mnt/sdcard
root@ROBOT2p:/mnt/sdcard# QFirehose -f .
[000.000]: Version: QFirehose_Linux_Android_V1.4.21
[000.000]: Builded: Apr 5 2025 18:08:59
[000.000]: Find md5 check file <./md5.txt>
[000.005]: md5 checking: ./contents.xml pass
[000.025]: md5 checking: ./update/abl.elf pass
[000.041]: md5 checking: ./update/aop.mbn pass
[000.045]: md5 checking: ./update/apdp.mbn pass
[000.050]: md5 checking: ./update/devcfg_low_ddr.mbn pass
[000.054]: md5 checking: ./update/devcfg.mbn pass
[000.056]: md5 checking: ./update/firehose/partition_complete_p4K_b256K.mbn pass
[000.056]: md5 checking: ./update/firehose/patch_p4K_b256K.xml pass
[000.085]: md5 checking: ./update/firehose/prog_firehose_lite.elf pass
[000.086]: md5 checking: ./update/firehose/rawprogram_nand_p4K_b256K_update.xml pass
[000.097]: md5 checking: ./update/hyp.mbn pass
[000.103]: md5 checking: ./update/ipa_fws.elf pass
[000.106]: md5 checking: ./update/logfs_ufs_8mb.bin pass
[000.108]: md5 checking: ./update/multi_image.mbn pass
[000.110]: md5 checking: ./update/multi_image_qti.mbn pass
<...>
[059.741]: Upgrade module successfully.
[059.741]: inf[0] ep_in -1/1024, errno = 143 (Cannot send after socket shutdown)
[059.741]: qusb_noblock_read read=-1, errno: 143 (Cannot send after socket shutdown)
[059.742]: qusb_noblock_read cur=0, min_size=1
root@ROBOT2p:/mnt/sdcard#
</syntaxhighlight>The update is successfull if one of the last lines displayed shows that the module has been successfully updated.

It is now needed to reconfigure properly the modem for Robot usage.

You need to run the microcom program as shown below (with different device as the modem has now a default configuration):<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# microcom /dev/ttyUSB2
</syntaxhighlight>Once connected, you'll have to enter the following AT commands:<syntaxhighlight lang="termcap">
at+qcfg="usbcfg",0x1075,0x407C,0,0,1,1,1,0,1
at+qcallcfg="voice_disable",2
AT+qnvfw="/nv/item_files/modem/uim/remote/uim_remote_service_enable",01
at+cfun=1,1

</syntaxhighlight>Once this is done, the Robot software can be restarted with the following command:<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# sc restart all
</syntaxhighlight>If there is another modem to update, then please proceed as explained at the beginning of this page.

If there is no more update to be done, you can remove the directory /mnt/sdcard/update and the other files which are parts of the Quectel update delivery.

Quectel RM520N Firmware Update (New)

2026-04-27T13:31:44Z

Administrator:

This page describes how to update the firmware of any of the Quectel RM520N modems within the Opale 5G Robot.

'''In the following, it is assumed the Opale 5G Robot is properly configured and accessible through IP.'''

Note that the procedure described in this page will be obsoleted when Modem updates will be integrated in the Opale Robot firmware.

[[File:Robots_Slots.jpg|394x394px]]

The Opale 5G Robot can include one or two RM520N (Among other possible configurations) modem as illustrated in the above picture.

In order to '''SAFELY''' upgrade any modems from the Opale 5G Robot, this procedure needs to be carefully followed.

'''This procedure describes updating one RM520N at a time.'''

First, the new RM520N modem firmware has to be downloaded on the Robot using a SFTP client.
[[File:Firmware Uploaded.png|thumb|606x606px|none]]The picture above shows where the Quectel RM520N Update file has to be downloaded.

Once this is done, the RM520N Update file need to be unzipped with the following command:<syntaxhighlight lang="termcap">
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 22.03-SNAPSHOT, r0-031ace73
-----------------------------------------------------
root@ROBOT2p:~# cd /mnt/sdcard
root@ROBOT2p:/mnt/sdcard# unzip RM520N*
Archive: RM520NGLAAR03A04M4G_01.204.01.204.zip
inflating: md5.txt
<...>
inflating: update/firehose/partition_complete_p4K_b256K.mbn
inflating: Quectel_RM520N-GL-AA_Firmware_Release_Notes_V0304_01.204.01.204.pdf
root@ROBOT2p:/mnt/sdcard#
</syntaxhighlight>The system should then be prepared with the following commands:

* The first one stops the robot software,
* and the second one power up the modem, so that we can set it up later.
<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# sc stop all
root@ROBOT2p:/mnt/sdcard# echo "1" > /sys/class/gpio/mdm_pwr/value

</syntaxhighlight>Then run the microcom terminal utility to enter AT commands to the RM520N modem (you may have to wait a few seconds so that the modem is ready):<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# microcom /dev/COM3
</syntaxhighlight>Then enter the following AT command to reconfigure the USB interface of the modem<syntaxhighlight lang="termcap">
at+qcfg="usbcfg",0x2c7c,0x0801,1,1,1,1,1,0,0
at+cfun=1,1

</syntaxhighlight>You may have to enter <control-x> in order to exit the microcom terminal utility.

Then the module can be updated with the following commands:<syntaxhighlight lang="termcap">
root@ROBOT2p: cd /mnt/sdcard
root@ROBOT2p:/mnt/sdcard# QFirehose -f .
[000.000]: Version: QFirehose_Linux_Android_V1.4.21
[000.000]: Builded: Apr 5 2025 18:08:59
[000.000]: Find md5 check file <./md5.txt>
[000.005]: md5 checking: ./contents.xml pass
[000.025]: md5 checking: ./update/abl.elf pass
[000.041]: md5 checking: ./update/aop.mbn pass
[000.045]: md5 checking: ./update/apdp.mbn pass
[000.050]: md5 checking: ./update/devcfg_low_ddr.mbn pass
[000.054]: md5 checking: ./update/devcfg.mbn pass
[000.056]: md5 checking: ./update/firehose/partition_complete_p4K_b256K.mbn pass
[000.056]: md5 checking: ./update/firehose/patch_p4K_b256K.xml pass
[000.085]: md5 checking: ./update/firehose/prog_firehose_lite.elf pass
[000.086]: md5 checking: ./update/firehose/rawprogram_nand_p4K_b256K_update.xml pass
[000.097]: md5 checking: ./update/hyp.mbn pass
[000.103]: md5 checking: ./update/ipa_fws.elf pass
[000.106]: md5 checking: ./update/logfs_ufs_8mb.bin pass
[000.108]: md5 checking: ./update/multi_image.mbn pass
[000.110]: md5 checking: ./update/multi_image_qti.mbn pass
<...>
[059.741]: Upgrade module successfully.
[059.741]: inf[0] ep_in -1/1024, errno = 143 (Cannot send after socket shutdown)
[059.741]: qusb_noblock_read read=-1, errno: 143 (Cannot send after socket shutdown)
[059.742]: qusb_noblock_read cur=0, min_size=1
root@ROBOT2p:/mnt/sdcard#
</syntaxhighlight>The update is successfull if one of the last lines displayed shows that the module has been successfully updated.

It is now needed to reconfigure properly the modem for Robot usage.

You need to run the microcom program as shown below (with different device as the modem has now a default configuration):<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# microcom /dev/ttyUSB2
</syntaxhighlight>Once connected, you'll have to enter the following AT commands:<syntaxhighlight lang="termcap">
at+qcfg="usbcfg",0x1075,0x407C,0,0,1,1,1,0,1
at+qcallcfg="voice_disable",2
AT+qnvfw="/nv/item_files/modem/uim/remote/uim_remote_service_enable",01
at+cfun=1,1

</syntaxhighlight>Once this is done, the Robot software can be restarted with the following command:<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# sc restart all
</syntaxhighlight>If there is another modem to update, then please proceed as explained at the beginning of this page.

If there is no more update to be done, you can remove the directory /mnt/sdcard/update and the other files which are parts of the Quectel update delivery.

Quectel RM520N Firmware Update (New)

2026-04-27T13:10:53Z

Administrator: Created page with "This page describes how to update the firmware of any of the Quectel RM520N modems within the Opale 5G Robot. '''In the following, it is assumed the Opale 5G Robot is properly configured and accessible through IP.''' Note that the procedure described in this page will be obsoleted when Modem updates will be integrated in the Opale Robot firmware. 394x394px The Opale 5G Robot can include one or two RM520N (Among other possible configur..."

This page describes how to update the firmware of any of the Quectel RM520N modems within the Opale 5G Robot.

'''In the following, it is assumed the Opale 5G Robot is properly configured and accessible through IP.'''

Note that the procedure described in this page will be obsoleted when Modem updates will be integrated in the Opale Robot firmware.

[[File:Robots_Slots.jpg|394x394px]]

The Opale 5G Robot can include one or two RM520N (Among other possible configurations) modem as illustrated in the above picture.

In order to '''SAFELY''' upgrade any modems from the Opale 5G Robot, this procedure needs to be carefully followed.

'''This procedure describes updating one RM520N at a time and the RM520N must be inserted into SLOT 0.'''

You will have to open the robot in order to access the RM520N modems.

'''Power off the robot and remove the four screws on the sides in order to open the robot.'''

Once the screws are removed process with caution while removing the cover as antennas cables are connected to the RM520N modems.
{| class="wikitable"
|Once the robot is opened (and still powered off):
* If your robot has just one RM520N modem, it should be located at SLOT 0. In that case, there is nothing more to do inside the robot and you can carefully close the robot and screw the cover back on.
* If you have two RM520Ns, as only the one in SLOT 0 will be safely upgraded, disconnect the modem in SLOT 1 by removing the screw which attach the modem to the SLOT, and, without disconnecting the antennas from the modem, remove the modem from the slot and leave it unplugged (while taking care that it does not touch any electric part)
* To upgrade the modem which is in SLOT 1, you have to insert this modem into SLOT 0 and leave unplugged the modem which was in SLOT 0.
'''In any case, to properly execute the update procedure, only one RM520N should be inserted in the robot and in SLOT 0'''
|}
Once the robot is ready with the RM520N modem to be updated inserted in SLOT 0, it can be powered on.

First, the new RM520N modem firmware has to be downloaded on the Robot using a SFTP client.
[[File:Firmware Uploaded.png|thumb|606x606px|none]]The picture above shows where the Quectel RM520N Update file has to be downloaded.

Once this is done, the RM520N Update file need to be unzipped with the following command:<syntaxhighlight lang="termcap">
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 22.03-SNAPSHOT, r0-031ace73
-----------------------------------------------------
root@ROBOT2p:~# cd /mnt/sdcard
root@ROBOT2p:/mnt/sdcard# unzip RM520N*
Archive: RM520NGLAAR03A04M4G_01.204.01.204.zip
inflating: md5.txt
<...>
inflating: update/firehose/partition_complete_p4K_b256K.mbn
inflating: Quectel_RM520N-GL-AA_Firmware_Release_Notes_V0304_01.204.01.204.pdf
root@ROBOT2p:/mnt/sdcard#
</syntaxhighlight>The system should then be prepared with the following commands:

* The first one stops the robot software,
* and the second one power up the modem, so that we can set it up later.
<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# sc stop all
root@ROBOT2p:/mnt/sdcard# echo "1" > /sys/class/gpio/mdm_pwr/value

</syntaxhighlight>Then run the microcom terminal utility to enter AT commands to the RM520N modem (you may have to wait a few seconds so that the modem is ready):<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# microcom /dev/COM3
</syntaxhighlight>Then enter the following AT command to reconfigure the USB interface of the modem<syntaxhighlight lang="termcap">
at+qcfg="usbcfg",0x2c7c,0x0801,1,1,1,1,1,0,0
at+cfun=1,1

</syntaxhighlight>You may have to enter <control-x> in order to exit the microcom terminal utility.

Then the module can be updated with the following commands:<syntaxhighlight lang="termcap">
root@ROBOT2p: cd /mnt/sdcard
root@ROBOT2p:/mnt/sdcard# QFirehose -f .
[000.000]: Version: QFirehose_Linux_Android_V1.4.21
[000.000]: Builded: Apr 5 2025 18:08:59
[000.000]: Find md5 check file <./md5.txt>
[000.005]: md5 checking: ./contents.xml pass
[000.025]: md5 checking: ./update/abl.elf pass
[000.041]: md5 checking: ./update/aop.mbn pass
[000.045]: md5 checking: ./update/apdp.mbn pass
[000.050]: md5 checking: ./update/devcfg_low_ddr.mbn pass
[000.054]: md5 checking: ./update/devcfg.mbn pass
[000.056]: md5 checking: ./update/firehose/partition_complete_p4K_b256K.mbn pass
[000.056]: md5 checking: ./update/firehose/patch_p4K_b256K.xml pass
[000.085]: md5 checking: ./update/firehose/prog_firehose_lite.elf pass
[000.086]: md5 checking: ./update/firehose/rawprogram_nand_p4K_b256K_update.xml pass
[000.097]: md5 checking: ./update/hyp.mbn pass
[000.103]: md5 checking: ./update/ipa_fws.elf pass
[000.106]: md5 checking: ./update/logfs_ufs_8mb.bin pass
[000.108]: md5 checking: ./update/multi_image.mbn pass
[000.110]: md5 checking: ./update/multi_image_qti.mbn pass
<...>
[059.741]: Upgrade module successfully.
[059.741]: inf[0] ep_in -1/1024, errno = 143 (Cannot send after socket shutdown)
[059.741]: qusb_noblock_read read=-1, errno: 143 (Cannot send after socket shutdown)
[059.742]: qusb_noblock_read cur=0, min_size=1
root@ROBOT2p:/mnt/sdcard#
</syntaxhighlight>The update is successfull if one of the last lines displayed shows that the module has been successfully updated.

It is now needed to reconfigure properly the modem for Robot usage.

You need to run the microcom program as shown below (with different device as the modem has now a default configuration):<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# microcom /dev/ttyUSB2
</syntaxhighlight>Once connected, you'll have to enter the following AT commands:<syntaxhighlight lang="termcap">
at+qcfg="usbcfg",0x1075,0x407C,0,0,1,1,1,0,1
at+qcallcfg="voice_disable",2
AT+qnvfw="/nv/item_files/modem/uim/remote/uim_remote_service_enable",01
at+cfun=1,1

</syntaxhighlight>Once this is done, the Robot software can be restarted with the following command:<syntaxhighlight lang="termcap">
root@ROBOT2p:/mnt/sdcard# sc restart all
</syntaxhighlight>If there is another modem to update, then please proceed as explained at the beginning of this page.

If there is no more update to be done, you can remove the directory /mnt/sdcard/update and the other files which are parts of the Quectel update delivery.

GetGsmNetworkList

2026-04-10T08:46:23Z

Administrator:

This command gets the PLMN (MCC and MNC), the name, the status and the access technology for all GSM operators detectable by the modem.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetGsmNetworkList'''
|PortIndex
|List of Operators’ PLMN, status, technology and name
|}

'''OUTPUT''' GSM port operator selection mode and GSM operator PLMN:

"%s %s %s\n", mode, plmn, status

'''Where''' technology (access technology) are :

* <code>0</code> = GSM
* <code>2</code> = UTRAN (3G)
* <code>7</code> = LTE
* <code>12</code> = NR5G (5G SA)
* <code>13</code> = NR5G (5G NSA)

'''EXAMPLE''' <syntaxhighlight lang="text">
~# GetGsmNetworkList 0
20801 CURRENT 7 Orange F
20801 AVAILABLE 2 Orange F
20801 AVAILABLE 0 Orange F
20810 AVAILABLE 7 F SFR
20815 FORBIDDEN 7 Free
20820 FORBIDDEN 2 F-Bouygues Telecom
20820 FORBIDDEN 7 F-Bouygues Telecom
</syntaxhighlight>

[[Category:NETWORK]]
[[Category:R2D2]]

Release notes

2026-03-23T11:06:09Z

Administrator:

== Base firmware History (Most recent first): ==

==== Opale-OPR1688X32-GO2026-03-20-upgrade.bin ====
Fix reboot problem on WS1688 latest motherboard.

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address.

==== Opale-OPR1688X32-GO2025-05-28-upgrade.bin ====
First documented firmware release.

== Opale R2D2 Software history (Most recent first): ==

==== Version 1.1 - 2026-04-01 ====
TBA

==== Version 1.0 - 2025-05-28 ====
First initial GA release. Includes:

* gsmrobotd_0.9.29_mipsel_24kc.ipk
* gsmuxsvc_0.9.8_mipsel_24kc.ipk
* r2d2_0.9.9_mipsel_24kc.ipk
* r2d2config_0.9.9_mipsel_24kc.ipk

Release notes

2026-03-23T11:04:50Z

Administrator:

== Base firmware History (Most recent first): ==

==== Opale-OPR1688X32-GO2026-03-20-upgrade.bin ====
Fix reboot problem on WS1688 latest motherboard.

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address.

==== Opale-OPR1688X32-GO2025-05-28-upgrade.bin ====
First documented firmware release.

== Opale R2D2 Software history (Most recent first): ==

==== '''Version 1.1 - 2026-04-01''' ====
TBA

==== '''Version 1.0 - 2025-05-28''' ====
First initial GA release. Includes:

* gsmrobotd_0.9.29_mipsel_24kc.ipk
* gsmuxsvc_0.9.8_mipsel_24kc.ipk
* r2d2_0.9.9_mipsel_24kc.ipk
* r2d2config_0.9.9_mipsel_24kc.ipk

Release notes

2026-03-23T11:03:42Z

Administrator:

== Base firmware History (Most recent first): ==

==== Opale-OPR1688X32-GO2026-03-20-upgrade.bin ====
Fix reboot problem on WS1688 latest motherboard.

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address.

==== Opale-OPR1688X32-GO2025-05-28-upgrade.bin ====
First documented firmware release.

== Opale R2D2 Software history (Most recent first): ==
'''Version 1.1 - 2026-04-01'''

TBA

'''Version 1.0 - 2025-05-28'''

First initial GA release. Includes:

* gsmrobotd_0.9.29_mipsel_24kc.ipk
* gsmuxsvc_0.9.8_mipsel_24kc.ipk
* r2d2_0.9.9_mipsel_24kc.ipk
* r2d2config_0.9.9_mipsel_24kc.ipk

Release notes

2026-03-23T10:45:03Z

Administrator:

Base firmware History:
{| class="wikitable mw-collapsible"
|+
!
!
!
!
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|}
- on March 20th, 2026

Fix reboot problem on WS1688 latest motherboard

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address

Opale R2D2 Software history:

Release notes

2026-03-23T10:39:46Z

Administrator:

Base firmware History:

Opale-OPR1688-32-GO2025-05-28-upgrade

Opale-OPR1688-32-GO2026-03-20-upgrade

- on March 20th, 2026

Fix reboot problem on WS1688 latest motherboard

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address

Opale R2D2 Software history:

Release notes

2026-03-23T10:37:03Z

Administrator:

Base firmware History:

Huasifei-WS1688AX-32-GO2025-05-28-upgrade

Huasifei-WS1688AX-32-GO2026-03-20-upgrade

- on March 20th, 2026

Fix reboot problem on WS1688 latest motherboard

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address

Opale R2D2 Software history:

Release notes

2026-03-23T10:34:53Z

Administrator: Created page with "firmware History: Huasifei-WS1688AX-32-GO2025-05-28-upgrade Huasifei-WS1688AX-32-GO2026-03-20-upgrade - on March 20th, 2026 Fix reboot problem on WS1688 latest motherboard Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log. breed is no longer required as U-boot, as setmac utility can be used to set mac address"

firmware History:

Huasifei-WS1688AX-32-GO2025-05-28-upgrade

Huasifei-WS1688AX-32-GO2026-03-20-upgrade

- on March 20th, 2026

Fix reboot problem on WS1688 latest motherboard

Fix firmware signature with 'Linux version 5.10.168 (opale@opale-builder)' in the system log.

breed is no longer required as U-boot, as setmac utility can be used to set mac address

SetIMEI

2026-03-10T15:39:59Z

Administrator:

This command sets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|SetIMEI
|Port_index IMEI
|GSM port IMEI
|}
'''OUTPUT'''

Set the IMEI number of the specified port. To restore the original number, this number should be read using GetIMEI first.

'''EXAMPLES'''<syntaxhighlight lang="text">
~# SetIMEI 1 895825000699682
OK

</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

GetIMEI

2026-03-10T15:36:14Z

Administrator:

This command gets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetIMEI'''
|Port_index [ORIGINAL]
|GSM port IMEI
|}
'''OUTPUT'''

If ORIGINAL is specified then the original IMEI of the modem is returned. Otherwise, the last programmed IMEI is returned.

Note that the original IMEI numbers are store in the following files : /etc/slidn with n beeing the port index number. The file can be empty or not present as long as the IMEI has not been modified on the module.

Command output in the following format:

"%s\n", imei

'''EXAMPLES'''<syntaxhighlight lang="text">
~# GetIMEI 1
895825000699682

# GetIMEI 0 ORIGINAL
895825000699682
</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

SetIMEI

2026-03-10T15:30:58Z

Administrator:

This command sets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|SetIMEI
|Port_index IMEI
|GSM port IMEI
|}
'''OUTPUT'''

Sets the IMEI number of the specified port. To restore the original number, this number should be read using GetIMEI first.

'''EXAMPLES'''<syntaxhighlight lang="text">
~# SetIMEI 1 895825000699682
OK

</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

SetIMEI

2026-03-10T15:29:27Z

Administrator:

This command sets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|SetIMEI
|Port_index IMEI
|GSM port IMEI
|}
'''OUTPUT'''

Sets the IMEI number of the specified port. To restore the original number, this number should be read using GetIMEI firstr.

'''EXAMPLES'''<syntaxhighlight lang="text">
~# SetIMEI 1 895825000699682

</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

GetIMEI

2026-03-10T15:28:27Z

Administrator:

This command gets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetIMEI'''
|Port_index [ORIGINAL]
|GSM port IMEI
|}
'''OUTPUT'''

If ORIGINAL is specified then the original IMEI of the modem is returned. Otherwise, the last programmed IMEI is returned.

Command output in the following format:

"%s\n", imei

'''EXAMPLES'''<syntaxhighlight lang="text">
~# GetIMEI 1
895825000699682

# GetIMEI 0 ORIGINAL
895825000699682
</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

SetIMEI

2026-03-10T15:27:10Z

Administrator:

This command sets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|SetIMEI
|Port_index IMEI
|GSM port IMEI
|}
'''OUTPUT'''

Sets the IMEI number of the specified port. To restore the original number, this number should be read using GetIMEI firstr.

Command output in the following format:

"%s\n", imei

'''EXAMPLES'''<syntaxhighlight lang="text">
~# SetIMEI 1 895825000699682

</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

SetIMEI

2026-03-10T15:24:31Z

Administrator: Created page with "This command sets module IMEI number for the specified GSM port. '''COMMAND''' {| class="wikitable" !Command !Line Arguments !Returns |- |'''GetIMEI''' |Port index [ORIGINAL] |GSM port IMEI |} '''OUTPUT''' If ORIGINAL is specified then the original IMEI of the modem is returned. Otherwise, the last programmed IMEI is returned. Command output in the following format: "%s\n", imei '''EXAMPLES'''<syntaxhighlight lang="text"> ~# GetIMEI 1 895825000699682 # Get IMEI 0..."

This command sets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetIMEI'''
|Port index [ORIGINAL]
|GSM port IMEI
|}
'''OUTPUT'''

If ORIGINAL is specified then the original IMEI of the modem is returned. Otherwise, the last programmed IMEI is returned.

Command output in the following format:

"%s\n", imei

'''EXAMPLES'''<syntaxhighlight lang="text">
~# GetIMEI 1
895825000699682

# Get IMEI 0 ORIGINAL
895825000699682
</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

GetIMEI

2026-03-10T15:23:41Z

Administrator:

This command gets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetIMEI'''
|Port index [ORIGINAL]
|GSM port IMEI
|}
'''OUTPUT'''

If ORIGINAL is specified then the original IMEI of the modem is returned. Otherwise, the last programmed IMEI is returned.

Command output in the following format:

"%s\n", imei

'''EXAMPLES'''<syntaxhighlight lang="text">
~# GetIMEI 1
895825000699682

# Get IMEI 0 ORIGINAL
895825000699682
</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

GetIMEI

2026-03-10T15:23:16Z

Administrator:

This command gets module IMEI number for the specified GSM port.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetIMEI'''
|Port index [ORIGINAL]
|GSM port IMEI
|}
'''OUTPUT'''

If ORIGINAL is specified then the original IMEI of the modem is returned. Otherwise, the last programmed IMEI is returned.

Command output in the following format:

"%s\n", imei

'''EXAMPLE'''<syntaxhighlight lang="text">
~# GetIMEI 1
895825000699682

# Get IMEI 0 ORIGINAL
895825000699682
</syntaxhighlight>

[[Category:R2D2]]
[[Category:SIM]]

GetMbnList

2026-02-18T16:01:21Z

Administrator:

This command gets a list of the LTE configuration MBN profiles for the specified LTE port. It is available only for the LTE ports equipped with Quectel modems.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetMbnList'''
|PortIndex
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

List of the LTE configuration MBN profiles

'''EXAMPLE'''<syntaxhighlight lang="text">
~# GetMbnList 0
+QMBNCFG: "List",0,1,1,"ROW_Generic_3GPP",0x05010812,000000000
+QMBNCFG: "List",1,0,0,"Commercial-DT",0x05011F11,000000000
+QMBNCFG: "List",2,0,0,"Commercial-EE",0x05012214,000000000
+QMBNCFG: "List",3,0,0,"Orange_Grp_Non_IMS-Commercial",0x05010B0C,000000000
+QMBNCFG: "List",4,0,0,"TF_Germany_VoLTE",0x05010C14,000000000
+QMBNCFG: "List",5,0,0,"TF_Non_VoLTE",0x05010C24,000000000
+QMBNCFG: "List",6,0,0,"TF_UK_VoLTE",0x05010C05,000000000
+QMBNCFG: "List",7,0,0,"VF_Germany_VoLTE",0x05010415,000000000
+QMBNCFG: "List",8,0,0,"VF_Italy_VoLTE",0x05010434,000000000
+QMBNCFG: "List",9,0,0,"VF_Non_VoLTE",0x05010422,000000000
+QMBNCFG: "List",10,0,0,"VF_Portugal_VoLTE",0x05010454,000000000
+QMBNCFG: "List",11,0,0,"VF_Spain_VoLTE",0x05010445,000000000
+QMBNCFG: "List",12,0,0,"VF_Turkey_VoLTE",0x05010461,000000000
+QMBNCFG: "List",13,0,0,"VF_UK_VoLTE",0x05010405,000000000
+QMBNCFG: "List",14,0,0,"Commercial-Cherry",0x05012300,000000000
+QMBNCFG: "List",15,0,0,"Commercial-iMobile",0x05012400,000000000
+QMBNCFG: "List",16,0,0,"Commercial-Smartfren",0x05012503,000000000
+QMBNCFG: "List",17,0,0,"YTL_Generic_3GPP",0x05012A00,000000000
+QMBNCFG: "List",18,0,0,"Bouygues_France_VoLTE",0x05800101,000000000
</syntaxhighlight>

[[Category:R2D2]]
[[Category:VOLTE]]

SendAtCommand

2026-02-02T10:49:36Z

Administrator:

This places an AT Command to the specified modem port.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|SendAtCommand
|Port index ATCommand (*)
|Issue an AT Command to the specified module.
|}

(*) Note that the ATCommand must be entered with quotes if the AT Command itself includes double quotes or spaces. See below.

'''OUTPUT:'''

Response from the modem to the AT command.

'''EXAMPLE:'''<syntaxhighlight lang="text">
~# SendAtCommand 0 "ATI4"
ATI4
Quectel
RM520N-GL
Revision: RM520NGLAAR03A05M4G

OK
</syntaxhighlight>'''OR'''<syntaxhighlight lang="text">
~# SendAtCommand 0 'AT+QCALLCFG="voice_disable"'
+QCALLCFG: "voice_disable",1
OK
</syntaxhighlight>

[[Category:GENERAL]]
[[Category:R2D2]]

SendAtCommand

2026-02-02T10:35:31Z

Administrator:

This places an AT Command to the specified modem port.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|SendAtCommand
|Port index ATCommand (*)
|Issue an AT Command to the specified module.
|}

(*) Note that the ATCommand must be entered with quotes if the AT Command itself includes double quotes or spaces. See below.

'''OUTPUT:'''

Response from the modem to the AT command.

'''EXAMPLE:'''<syntaxhighlight lang="text">
~# SendAtCommand 0 "ATI4"
ATI4
Quectel
RM500Q-AE
Revision: RM500QAEAAR13A03M4G
OK
</syntaxhighlight>'''OR'''<syntaxhighlight lang="text">
~# SendAtCommand 0 'AT+QCALLCFG="voice_disable"'
+QCALLCFG: "voice_disable",1
OK
</syntaxhighlight>

[[Category:GENERAL]]
[[Category:R2D2]]

SendAtCommand

2026-02-02T10:32:25Z

Administrator:

This places an AT Command to the specified modem port.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|SendAtCommand
|Port index ATCommand (*)
|Issue an AT Command to the specified module.
|}

(*) Note that the ATCommand must be entered with quotes if the AT Command itself includes double quotes or spaces. See below.

'''OUTPUT:'''

Response from the modem to the AT command.

'''EXAMPLE:'''<syntaxhighlight lang="text">
~# SendAtCommand 0 "ATI4"
ATI4
Quectel
RM500Q-AE
Revision: RM500QAEAAR13A03M4G
OK
</syntaxhighlight>'''OR'''<syntaxhighlight lang="text">
~# SendAtCommand 0,'AT+QCALLCFG="voice_enable"'
+QCALLCFG: "voice_disable",1
OK
</syntaxhighlight>

[[Category:GENERAL]]
[[Category:R2D2]]

R2D2 HTTP API

2026-01-28T15:24:13Z

Administrator:

Any command from the R2D2 API can be accessed through a HTTP Interface.

It has the following syntax:
{| class="wikitable"
|'''Syntax''':
|http://['''user:password'''@]'''IP_Address'''[:'''Port_Number]'''/cgi-bin?command='''R2D2Command'''&'''arg1'''=val1&'''arg2'''=val2...&'''argN'''=v
|-
|
| - '''User:password''' are user & password to connect to the Robot

- '''IP_Address''' is the TCP/IP address of the Robot, '''Port''' is the port used to access the R2D2 API

- '''R2D2Commmand''' is the R2D2 API command to be executed

- '''arg1''' to '''argN''' depend on the arguments needed for the R2D2 API command entered.

Argument between brackets are optionals.
|-
|'''Examples:'''
|If Robot's credentials are user=root and password=admin, at IP Address 192.168.1.1 with port 8000:

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=StartGsmPort&arg1=0</nowiki>

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=SendAtCommand&arg1=0&arg2=ATI4</nowiki>
|}
In order to allow the HTTP interface to work, it has to be enabled by the following command (through a SSH session):

<code>reg add services/gsmrobotd/parameters /v HTTPListeningPort /t REG_DWORD /d 8000</code>

It sets the HTTP ListingPort to 8000, or any desired and available value (note that 80 will conflict with the robot web interface).

<code>reg add services/gsmrobotd/parameters /v HTTPSListeningPort /t REG_DWORD /d 8443</code>

It sets the HTTPS ListingPort to 8443, or any desired and available value. And the following line saves the modification on disk.

<code>reg regsave</code>

Then to take into account the changes the following commands must be entered:

<code>sc restart all</code>

The following command can then be used to check if the configuration is correct:

<code>reg query services/gsmrobotd/parameters /v HTTPListeningPort</code>

<code>reg query services/gsmrobotd/parameters /v HTTPSListeningPort</code>

It will either return the HTTP or the HTTPS Listening port depending on the command above entered.

R2D2 HTTP API

2026-01-28T10:19:29Z

Administrator:

Any command from the R2D2 API can be accessed through a HTTP Interface.

It has the following syntax:
{| class="wikitable"
|'''Syntax''':
|http://['''user:password'''@]'''IP_Address'''[:'''Port_Number]'''/cgi-bin?command='''R2D2Command'''&'''arg1'''=val1&'''arg2'''=val2...&'''argN'''=v
|-
|
| - '''User:password''' are user & password to connect to the Robot

- '''IP_Address''' is the TCP/IP address of the Robot, '''Port''' is the port used to access the R2D2 API

- '''R2D2Commmand''' is the R2D2 API command to be executed

- '''arg1''' to '''argN''' depend on the arguments needed for the R2D2 API command entered.

Argument between brackets are optionals.
|-
|'''Examples:'''
|If Robot's credentials are user=root and password=admin, at IP Address 192.168.1.1 with port 8000:

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=StartGsmPort&arg1=0</nowiki>

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=SendAtCommand&arg1=0&arg2=ATI4</nowiki>
|}
In order to allow the HTTP interface to work, it has to be enabled by the following command (through SSH):

<code>reg add services/gsmrobotd/parameters /v HTTPListeningPort /t REG_DWORD /d 8000</code>

It sets the HTTP ListingPort to 8000, or any desired and available value (note that 80 will conflict with the robot web interface).

<code>reg add services/gsmrobotd/parameters /v HTTPSListeningPort /t REG_DWORD /d 8443</code>

It sets the HTTPS ListingPort to 8443, or any desired and available value. And the following line saves the modification on disk.

<code>reg regsave</code>

Then to take into account the changes the following commands must be entered:

<code>sc restart all</code>

The following command can then be used to check if the configuration is correct:

<code>reg query services/gsmrobotd/parameters /v HTTPListeningPort</code>

<code>reg query services/gsmrobotd/parameters /v HTTPSListeningPort</code>

It will either return the HTTP or the HTTPS Listening port depending on the command above entered.

R2D2 HTTP API

2026-01-28T10:16:56Z

Administrator:

Any command from the R2D2 API can be accessed through a HTTP Interface.

It has the following syntax:
{| class="wikitable"
|'''Syntax''':
|http://['''user:password'''@]'''IP_Address'''[:'''Port_Number]'''/cgi-bin?command='''R2D2Command'''&'''arg1'''=val1&'''arg2'''=val2...&'''argN'''=v
|-
|
| - '''User:password''' are user & password to connect to the Robot

- '''IP_Address''' is the TCP/IP address of the Robot, '''Port''' is the port used to access the R2D2 API

- '''R2D2Commmand''' is the R2D2 API command to be executed

- '''arg1''' to '''argN''' depend on the arguments needed for the R2D2 API command entered.

Argument between brackets are optionals.
|-
|'''Examples:'''
|If Robot's credentials are user=root and password=admin, at IP Address 192.168.1.1 with port 8000:

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=StartGsmPort&arg1=0</nowiki>

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=SendAtCommand&arg1=0&arg2=ATI4</nowiki>
|}
In order to allow the HTTP interface to work, it has to be enabled by the following command (through SSH):

<code>reg add services/gsmrobotd/parameters /v HTTPListeningPort /t REG_DWORD /d 80</code>

It sets the HTTP ListingPort to 80, or any desired and available value.

<code>reg add services/gsmrobotd/parameters /v HTTPSListeningPort /t REG_DWORD /d 443</code>

It sets the HTTPS ListingPort to 443, or any desired and available value. And the following line saves the modification on disk.

<code>reg regsave</code>

Then to take into account the changes the following commands must be entered:

<code>sc stop gsmrobotd</code>

<code>sc stop gsmuxsvc</code>

<code>sc start gsmuxsvc</code>

<code>sc start gsmrobotd</code>

The following command can then be used to check if the configuration is correct:

<code>reg query services/gsmrobotd/parameters /v HTTPListeningPort</code>

<code>reg query services/gsmrobotd/parameters /v HTTPSListeningPort</code>

It will either return the HTTP or the HTTPS Listening port depending on the command above entered.

R2D2 HTTP API

2026-01-28T10:16:01Z

Administrator:

Any command from the R2D2 API can be accessed through a HTTP Interface.

It has the following syntax:
{| class="wikitable"
|'''Syntax''':
|http://['''user:password'''@]'''IP_Address'''[:'''Port_Number]'''/cgi-bin?command='''R2D2Command'''&'''arg1'''=val1&'''arg2'''=val2...&'''argN'''=v
|-
|
| - '''User:password''' are user & password to connect to the Robot

- '''IP_Address''' is the TCP/IP address of the Robot, '''Port''' is the port used to access the R2D2 API

- '''R2D2Commmand''' is the R2D2 API command to be executed

- '''arg1''' to '''argN''' depend on the arguments needed for the R2D2 API command entered.

Argument between brackets are optionals.
|-
|'''Examples:'''
|If Robot's credentials are user=root and password=admin, at IP Address 192.168.1.1 with port 8000:

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=StartGsmPort&arg1=0</nowiki>

* http://root:admin@192.168.1<nowiki/>.1:8000/cgi-bin?command=SendAtCommand&arg1=0&arg2=ATI4
|}
In order to allow the HTTP interface to work, it has to be enabled by the following command (through SSH):

<code>reg add services/gsmrobotd/parameters /v HTTPListeningPort /t REG_DWORD /d 80</code>

It sets the HTTP ListingPort to 80, or any desired and available value.

<code>reg add services/gsmrobotd/parameters /v HTTPSListeningPort /t REG_DWORD /d 443</code>

It sets the HTTPS ListingPort to 443, or any desired and available value. And the following line saves the modification on disk.

<code>reg regsave</code>

Then to take into account the changes the following commands must be entered:

<code>sc stop gsmrobotd</code>

<code>sc stop gsmuxsvc</code>

<code>sc start gsmuxsvc</code>

<code>sc start gsmrobotd</code>

The following command can then be used to check if the configuration is correct:

<code>reg query services/gsmrobotd/parameters /v HTTPListeningPort</code>

<code>reg query services/gsmrobotd/parameters /v HTTPSListeningPort</code>

It will either return the HTTP or the HTTPS Listening port depending on the command above entered.

R2D2 HTTP API

2026-01-28T10:11:27Z

Administrator:

Any command from the R2D2 API can be accessed through a HTTP Interface.

It has the following syntax:
{| class="wikitable"
|'''Syntax''':
|http://['''user:password'''@]'''IP_Address'''[:'''Port_Number]'''/cgi-bin?command='''R2D2Command'''&'''arg1'''=val1&'''arg2'''=val2...&'''argN'''=v
|-
|
| - '''User:password''' are user & password to connect to the Robot

- '''IP_Address''' is the TCP/IP address of the Robot, '''Port''' is the port used to access the R2D2 API

- '''R2D2Commmand''' is the R2D2 API command to be executed

- '''arg1''' to '''argN''' depend on the arguments needed for the R2D2 API command entered.

Argument between brackets are optionals.
|-
|'''Examples:'''
|If Robot's credentials are user=root and password=admin, at IP Address 192.168.1.1 with port 8000:

* <nowiki>http://root:admin@192.168.1.1:8000/cgi-bin?command=StartGsmPort&arg1=0</nowiki>

* http://root:admin@192.168.1<nowiki/>.1:8000/cgi-bin?command=SendAtCommand&arg1=0arg2=ATI4
|}
In order to allow the HTTP interface to work, it has to be enabled by the following command (through SSH):

<code>reg add services/gsmrobotd/parameters /v HTTPListeningPort /t REG_DWORD /d 80</code>

It sets the HTTP ListingPort to 80, or any desired and available value.

<code>reg add services/gsmrobotd/parameters /v HTTPSListeningPort /t REG_DWORD /d 443</code>

It sets the HTTPS ListingPort to 443, or any desired and available value. And the following line saves the modification on disk.

<code>reg regsave</code>

Then to take into account the changes the following commands must be entered:

<code>sc stop gsmrobotd</code>

<code>sc stop gsmuxsvc</code>

<code>sc start gsmuxsvc</code>

<code>sc start gsmrobotd</code>

The following command can then be used to check if the configuration is correct:

<code>reg query services/gsmrobotd/parameters /v HTTPListeningPort</code>

<code>reg query services/gsmrobotd/parameters /v HTTPSListeningPort</code>

It will either return the HTTP or the HTTPS Listening port depending on the command above entered.

StartQxdmTrace

2025-11-04T09:10:17Z

Administrator:

This command starts QXDM traces on DIAG port of the specifed port.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|StartQxdmTrace
|PortIndex Filename
|[[R2D2 Error Codes|Error Code]] in case of error
|}
'''OUTPUT:'''

None.

'''EXAMPLE:''' ~#StartQxdmTrace 0 /var/log.trc

[[Category:GENERAL]]
[[Category:R2D2]]

StreamVideo

2025-11-03T23:37:51Z

Administrator:

This command performs a video streaming action through the specified GSM port to download videos at given URL.

Data session should be active on the specified port.

Any youtube website is supported.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''StreamVideo'''
|PortIndex, URL
|[[R2D2 Error Codes|Error Code]] in case of error.
|}

'''OUTPUT'''

Success or Error Message (See [[Data Messages|Data Commands Messages]])

'''EXAMPLE''' <syntaxhighlight lang="text">
~# StreamVideo 0 "https://www.youtube.com/watch?v=JmPgWUd896g"
Streaming done
</syntaxhighlight>
[[Category:R2D2]]
[[Category:DATA]]

GetListOfApiFunctions

2025-11-03T23:10:42Z

Administrator:

This command writes to the standard output the list of supported R2D2 API functions. Optional flag A can be used to get list in alphabetical order.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|GetListOfApiFunctions
|None or A
|List of supported R2D2 API commands
|}
'''OUTPUT'''

R2D2 API software version

'''EXAMPLE'''<syntaxhighlight lang="text">
~# GetListOfApiFunctions
R2D2 API functions:
GetGsmRobotApiVersion
GetListOfApiFunctions
...
RouteGsmPortToSip
GsmRoutePrint
</syntaxhighlight>

[[Category:R2D2]]
[[Category:GENERAL]]

GetListOfApiFunctions

2025-11-03T23:10:00Z

Administrator:

This command writes to the standard output the list of supported R2D2 API functions. Optional flag A can be used to get list in alphabetical order.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|GetListOfApiFunctions
|None
|List of supported R2D2 API commands
|}
'''OUTPUT'''

R2D2 API software version

'''EXAMPLE'''<syntaxhighlight lang="text">
~# GetListOfApiFunctions
R2D2 API functions:
GetGsmRobotApiVersion
GetListOfApiFunctions
...
RouteGsmPortToSip
GsmRoutePrint
</syntaxhighlight>

[[Category:R2D2]]
[[Category:GENERAL]]

StopQxdmTrace

2025-11-03T23:08:43Z

Administrator:

This command stops QXDM trace on specifed port.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|StopQxdmTrace
|PortIndex
|[[R2D2 Error Codes|Error Code]] in case of error
|}
'''OUTPUT:'''

None.

'''EXAMPLE:'''

~#StopQxdmTrace 0

[[Category:GENERAL]]
[[Category:R2D2]]

StartQxdmTrace

2025-11-03T23:06:23Z

Administrator:

This command starts QXDM traces on DIAG port of the specifed port.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|StartQxdmTrace
|PortIndex Filename
|[[R2D2 Error Codes|Error Code]] in case of error
|}
'''OUTPUT:'''

None.

'''EXAMPLE:''' ~#StopQxdmTrace 0 /var/log.trc

[[Category:GENERAL]]
[[Category:R2D2]]

StartQxdmTrace

2025-11-03T23:05:41Z

Administrator:

This command starts/opens the specified GSM port when a local sim card is used.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|StartQxdmTrace
|PortIndex Filename
|[[R2D2 Error Codes|Error Code]] in case of error
|}
'''OUTPUT:'''

None.

'''EXAMPLE:''' ~#StopQxdmTrace 0 /var/log.trc

[[Category:GENERAL]]
[[Category:R2D2]]

StopQxdmTrace

2025-11-03T23:03:03Z

Administrator:

This command starts/opens the specified GSM port when a local sim card is used.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|StartGsmPort
|PortIndex
|[[R2D2 Error Codes|Error Code]] in case of error
|}
'''OUTPUT:'''

None.

'''EXAMPLE:'''

~#StartGsmPort 0

[[Category:GENERAL]]
[[Category:R2D2]]

StopQxdmTrace

2025-11-03T23:01:45Z

Administrator:

StopQxdmTrace

2025-11-03T22:59:38Z

Administrator: Created blank page

StartQxdmTrace

2025-11-03T22:58:31Z

Administrator: Created page with "This command starts/opens the specified GSM port when a local sim card is used. '''COMMAND:''' {| class="wikitable" !Command !Input Arguments !Returns |- |StartGsmPort |PortIndex |Error Code in case of error |} '''OUTPUT:''' None. '''EXAMPLE:''' ~#StartGsmPort 0 Category:GENERAL Category:R2D2"

This command starts/opens the specified GSM port when a local sim card is used.

'''COMMAND:'''
{| class="wikitable"
!Command
!Input Arguments
!Returns
|-
|StartGsmPort
|PortIndex
|[[R2D2 Error Codes|Error Code]] in case of error
|}
'''OUTPUT:'''

None.

'''EXAMPLE:''' ~#StartGsmPort 0

[[Category:GENERAL]]
[[Category:R2D2]]

WaitVolteRegistration

2025-11-03T21:41:35Z

Administrator:

This command allows to wait until VoLTE registration is done.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''WaitVolteRegistration'''
|PortIndex [Timeout]
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

Command status

'''EXAMPLE'''<syntaxhighlight lang="text">
~# WaitVolteRegistration 0 180
OK
</syntaxhighlight>

[[Category:VOLTE]]
[[Category:R2D2]]

WaitRegistration

2025-11-03T21:40:52Z

Administrator:

This command allows to wait until Network registration is done.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''WaitRegistration'''
|PortIndex [Timeout]
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

Command status

'''EXAMPLE'''<syntaxhighlight lang="text">
~# WaitRegistration 0 180
OK
</syntaxhighlight>

[[Category:NETWORK]]
[[Category:R2D2]]

WaitRegistration

2025-11-03T21:39:51Z

Administrator:

This command allows to wait until Network registration is done.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''WaitRegistration'''
|PortIndex,Timeout
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

Command status

'''EXAMPLE'''<syntaxhighlight lang="text">
~# WaitRegistration 0 180
OK
</syntaxhighlight>

[[Category:NETWORK]]
[[Category:R2D2]]

WaitRegistration

2025-11-03T21:37:30Z

Administrator:

This command allows to wait until Network registration is done.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''WaitRegistration'''
|PortIndex,TimeoutVolteMode
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

Command status

'''EXAMPLE'''<syntaxhighlight lang="text">
~# WaitRegistration 0 180
OK
</syntaxhighlight>

[[Category:NETWORK]]
[[Category:R2D2]]

WaitRegistration

2025-11-03T21:36:54Z

Administrator:

This command allows to wait until VoLTE registration is done.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''WaitRegistration'''
|PortIndex,TimeoutVolteMode
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

Command status

'''EXAMPLE'''<syntaxhighlight lang="text">
~# WaitVolteRegistration 0 180
OK
</syntaxhighlight>

[[Category:NETWORK]]
[[Category:R2D2]]

WaitRegistration

2025-11-03T21:36:39Z

Administrator:

WaitRegistration

2025-11-03T21:36:11Z

Administrator: Created page with "This command allows to wait until VoLTE registration is done. '''COMMAND''' {| class="wikitable" !Command !Line Arguments !Returns |- |'''WaitVolteRegistration''' |PortIndex,TimeoutVolteMode |Error Code in case of error. |} '''OUTPUT''' Command status '''EXAMPLE'''<syntaxhighlight lang="text"> ~# WaitVolteRegistration 0 180 OK </syntaxhighlight> Category:VOLTE Category:R2D2"

This command allows to wait until VoLTE registration is done.

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''WaitVolteRegistration'''
|PortIndex,TimeoutVolteMode
|[[R2D2 Error Codes|Error Code]] in case of error.
|}
'''OUTPUT'''

Command status

'''EXAMPLE'''<syntaxhighlight lang="text">
~# WaitVolteRegistration 0 180
OK
</syntaxhighlight>

[[Category:VOLTE]]
[[Category:R2D2]]

GetNeighborCellsInfoVerbose

2025-09-13T21:45:47Z

Administrator:

This command writes to the standard output GSM Cell information, in the format specific for GSM port, for the neighbor cells on the specified GSM port.

'''This command is not supported on QUECTEL modules.'''

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetNeighborCellsInfoVerbose'''
|PortIndex
|Neighbor Cells Info in GSM module format
|}
'''OUTPUT'''

Command output in the following format (for each Cell);

for 4G access technology:
"rat,earfcn,pcid,rsrq,rsrp,rssi,sinr,srxlev,cell_resel_priority,s_non_intra_search,thresh_serving_low,s_intra_search\n
%s,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d\n"
for 3G access technology:
"rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev\n
%s,%d,%d,%d,%d,%d,%d,%d,%d\n"
'''EXAMPLE'''<syntaxhighlight lang="text">
~ # GetNeighborCellsInfoVerbose 0
rat,mcc,mnc,lac,cellid,uarfcn,psc,rscp,ecno,srxqual,srxlev,set,rank
"3G",220,03,53FD,C7E2B,10638,200,-81,22,14,33,1,-22
rat,mcc,mnc,lac,cellid,uarfcn,psc,rscp,ecno,srxqual,srxlev,set,rank
"3G",220,03,53FD,C0439,10638,0,-80,21,15,34,1,-21
rat,mcc,mnc,lac,cellid,uarfcn,psc,rscp,ecno,srxqual,srxlev,set,rank
"3G",-,-,-,-,10638,379,-87,35,1,27,1,-35

~ # GetNeighborCellsInfoVerbose 1
rat,earfcn,pcid,rsrq,rsrp,rssi,sinr,srxlev,cell_resel_priority,
s_non_intra_search,thresh_serving_low,s_intra_search
"LTE",6400,305,-14,-109,-77,-20,14,255,10,8,62
rat,earfcn,pcid,rsrq,rsrp,rssi,sinr,srxlev,cell_resel_priority,
s_non_intra_search,thresh_serving_low,s_intra_search
"LTE",6400,303,-16,-114,-88,-20,9,255,10,8,62
rat,earfcn,pcid,rsrq,rsrp,rssi,sinr,srxlev,cell_resel_priority,
s_non_intra_search,thresh_serving_low,s_intra_search
"LTE",6400,15,-14,-114,-90,-20,10,255,10,8,62

~ # SetAccessTechnology 0 GSM
OK

~ # GetNeighborCellsInfoVerbose 0
rat,mcc,mnc,lac,cellid,bsic,arfcn,rxlev,c1,c2,c31,c32
"2G",220,03,88C6,571B,62,64,-83,24,24,0,0
rat,mcc,mnc,lac,cellid,bsic,arfcn,rxlev,c1,c2,c31,c32
"2G",220,03,7D0C,7DD3,31,60,-85,22,22,0,0

~ # SetAccessTechnology 1 UMTS
OK

~ # GetNeighborCellsInfoVerbose 1
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,344,0,0,3,-32768,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,244,-730,-100,3,-32768,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,452,-750,-100,3,-32768,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,342,-750,-105,3,-32768,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,395,-750,-115,3,-32768,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,0,-770,-115,2,-23,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,319,-780,-165,3,-32768,-
rat,uarfcn,srxqual,psc,rscp,ecno,set,rank,srxlev
"WCDMA",10688,-661,258,-860,-230,3,-32768,-
</syntaxhighlight>

[[Category:R2D2]]
[[Category:NETWORK]]

GetServingCellInfoVerbose

2025-09-13T21:45:03Z

Administrator:

This command writes to the standard output GSM Cell information, in the format specific for GSM port, for the serving cell on the specified GSM port.

'''This command is only supported on QUECTEL modules.'''

'''COMMAND'''
{| class="wikitable"
!Command
!Line Arguments
!Returns
|-
|'''GetServingCellInfoVerbose'''
|PortIndex
|Serving Cell Info in GSM module format
|}
'''OUTPUT'''

Command output in the following format;

On GSM port, for 4G access technology:
"state,rat,is_tdd,mcc,mnc,cellid,pcid,earfcn,freq_band_ind,ul_bandwidth,dl_bandwidth,tac,rsrp,rsrq,rssi,sinr,srxlev\n
%s,%s,%s,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d\n"
On GSM port, for 3G access technology:
"state,rat,mcc,mnc,lac,cellid,uarfcn,psc,rac,rscp,ecio,phych,sf,slot,speech_code,commode\n
%s,%s,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d,%d\n"
'''EXAMPLE'''<syntaxhighlight lang="text">
~ # GetServingCellInfoVerbose 0
state,rat,mcc,mnc,lac,cellid,uarfcn,psc,rssi,rscp,ecno,srxqual,srxlev,drx,PhysCh,SF,slot,dchrscp,dchecno,voicecodec,ComMod
"NOCONN","3G",220,03,53FD,C2775,10638,67,-80,-80,23,13,34,64,-,-,-,-,-,"-",-

~ # SetAccessTechnology 0 GSM
OK

~ # GetServingCellInfoVerbose 0
state,rat,mcc,mnc,lac,cellid,bsic,arfcn,band,rxlev,txp,rla,drx,c1,c2,gprs,tch,ts,ta,maio,hsn,rxlevsub,rxlevfull, rxqualsub,rxqualfull,voicecodec
"NOCONN","2G",220,03,88C6,2775,30,56,0,-68,5,4,64,39,39,1,-,-,-,-,-,-,-,-,-,"-"

~ # GetServingCellInfoVerbose 1
state,rat,is_tdd,mcc,mnc,cellid,pcid,earfcn,freq_band_ind,ul_bandwidth,dl_bandwidth,tac,rsrp,rsrq,rssi,sinr,srxlev
"LIMSRV","LTE","FDD",220,05,1120D,305,6400,20,3,3,18,-109,-16,-76,-1,14

~ # GetServingCellInfoVerbose 1
state,rat,mcc,mnc,lac,cellid,uarfcn,psc,rac,rscp,ecio,phych,sf,slot,speech_code,comMod
"NOCONN","WCDMA",220,03,53FD,CC9A5,10688,67,1,-84,-14,-,-,-,-,-
</syntaxhighlight>

[[Category:R2D2]]
[[Category:NETWORK]]