Closed vidavidorra closed 4 years ago
I've got this part figured out myself now but I don't have a good source for why yet.
Apparently the R4 module can't use AT+CGDATA="PPP",
to go to data mode (see AT commands manual p 135). It needs to use ATD*99***#1
to go to data mode. The only 'real' hint for that is the fact that the R4's AT commands manual doesn't explicitly document the +CGDATA
command.
The DTR
pin needs to be pulled low in order to go to data mode. I haven't been able to find a good source (yet) on why that is needed. Only source I have is this and this forum post.
WIth this information I don't know why the UBLOX_AT cellular target specifies AT_CGDATA=1
(see here) for the TARGET_UBLOX_C030_R41XM
target. Based on the above I don't think that would work.
I think I've got most of this figured out myself now. Only thing I'm still struggling with is how I can select the protocol to use (e.g. LTE Cat M1) for the SARA-R412M from the application. Can anyone help with that?
how I can select the protocol to use (e.g. LTE Cat M1) for the SARA-R412M from the application network capabilities can be set using AT+URAT e.g. AT+URAT=7 (LTE Cat M1 only) AT+URAT=8 (NBIoT only) AT+URAT=7,9 (LTE Cat M1 with EDGE fallback) Depends what MNO /MVNO SIM you use but in our situation the modem attaches to EDGE instead of LTE Cat M1, because registration took longer on the LTE roaming partner resulting in a timeout and fallback to 2G EDGE.
I think I need to elaborate a bit. I know how to manually set the the protocol to use using the AT commands, that is indeed what @partychief posted using the AT+URAT=...
commands.
What I want to know is how I can use the OS drivers (e.g. CellularNetwork
) to set the protocol, or rather the RAT (radio access technology). I've found the CellularNetwork:: set_access_technology
function but I don't see anywhere internally how that could possibly be using the AT+URAT=...
command to set the RAT.
Thank you for raising this issue. Please note we have updated our policies and now only defects should be raised directly in GitHub. Going forward questions and enhancements will be considered in our forums, https://forums.mbed.com/ . If this issue is still relevant please re-raise it there. This GitHub issue will now be closed.
Description
I'm trying to use the u-blox PPP with the u-blox SARA-R412M-02B. The u-blox module is running on firmware version
M0.09.00
. The latest version isM0.10.00
but in the release notes of that I can't see any relevant changes to going to PPP mode. I'm running on mbed-os-5.11.4, but didn't see significant changes for this in the release notes of later releases. Please let me know if there are significant changes (and which) that can help with this issue.The issue seems related to #7682, but I also cannot get this working when I manually change
AT+CGDATA="PPP",1
toATD*99***1#
. That change is basically using thiselse
-statement. See the log below (when I was usingAT+CGDATA
but output is the same for theATD
option.Log
Issue request type