New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PPPCellularInterface::connect calls nwk_registration with a hard coded value #7213
Comments
Please use new cellular because PPPCellularInterface is to be deprecated. You can then define modem to be GSM/LTE in |
Thanks one final question. When i attempt to run the cell test, I receive the following error. Build successes:
The rest to the test suite runs just fine. Do cellular targets need to be define in any other locations? |
@cedrickkukela-cd - can you confirm the test name you are trying to run? There is a blog post about running network socket tests. Be sure to pass in a test config file which specifies the interface you are using? Does this help? https://os.mbed.com/blog/entry/Verify-a-Network-Driver-Greentea/ For details, see Testing section of https://os.mbed.com/docs/v5.8/reference/contributing-connectivity.html |
@cedrickkukela-cd you need to define CELLULAR_DEVICE to select correct cellular module drivers. |
Already done in current pull request. The only remaining issue is the use of atd vs vs at+cgdata in at_cellularnetwork. There should be a way to select with command is used for initiating a ppp connection as some modules may not support at+cgdata( ublox r410). |
Please see my comment about |
sorry about the delay |
@cedrickkukela-cd do you think we can close this issue? The "use of atd vs at+cgdata in at_cellularnetwork" as you requested above is now supported with PR #7870. |
Description
While attempting to bring on a new target enabled target mbed, I noticed that in PPPCellularInterface::connect the value passed to nwk_registration is hard coded. Since this value is used to switch between at+creg and at+cgreg, I effectively locks you into using at+cgreg for registration. This may not be a problem on cat 1 modems but on cat m modems such a Ublox r410, at+cgreg will always return a 0,4. Only creg and cereg will return the proper value. I was wondering if there was a fix for this issue in place or should i extend the interface to support nwk_type.
@maclobdell
Issue request type
[ ] Question
[x] Enhancement
[ ] Bug
The text was updated successfully, but these errors were encountered: