-
Notifications
You must be signed in to change notification settings - Fork 793
todo
Module aithinker_a6
:
In gprsConnectImpl(): wait AT+CGATT?
In dtmfSendImpl(): correctly handle the duration parameter
In modemGetConnected(): correctly read the mux number
Module digi_xbee
:
In operator GsmClientXBee::read(): Read directly into user buffer?
In enterCommandMode(): optimize this
Module espressif_esp32
:
In handleURCs(): I'm not sure if each +IPD URC reports the amount newly received or the total now in the buffer. It appears to be the latter.
Class GsmClient< modemType, tcpConfig >
:
In <a href="class_gsm_client.html#ac3343dcdf3ba62f63aeb3b0775e4a93a" class="m-doc">GsmClient::<wbr />connect()</a>, confirm that we can trust sock_connected at the start of a new connection before calling stop or if we should call stop regardless for static mux assignment.
Module neoway_m590
:
In gprsConnectImpl(): configure DNS settings if needed
In gprsDisconnectImpl(): There is no command in AT command set
In modemConnect(): no need for loop?
Module quectel_bg96
:
In operator GsmClientBG96::read(): Read directly into user buffer?
In modemEndSend(): Wait for ACK? (AT+QISEND=id,0 or AT+QSSLSEND=id,0)
In modemGetConnected(): Verify mux
Module quectel_m95
:
In modemEndSend(): get len/ack properly
In modemRead(): Does this even work????
Module quectel_mc60
:
In modemEndSend(): verify len/ack
In modemRead(): Does this even work????
In handleURCs(): QIRD? or QIRDI?
Module simcom_a7672x
:
In GsmClientA7672X constructor: Ensure the secure socket mux isn't out of range
In getLocalIPSecure(): figure out when to use each command properly
In deleteCertificateImpl(): test
In <a href="class_gsm_client.html#ac3343dcdf3ba62f63aeb3b0775e4a93a" class="m-doc">connect()</a> (secure path): Shouldn't CCHSET be called only once during the init or during the GPRS connection process?
In <a href="class_gsm_client.html#ac3343dcdf3ba62f63aeb3b0775e4a93a" class="m-doc">connect()</a> (secure path): Should CCHSTART be called once during the GPRS connection process instead of repeatedly here?
In <a href="class_gsm_client.html#ac3343dcdf3ba62f63aeb3b0775e4a93a" class="m-doc">connect()</a> (secure path): verify the socket returned by CCHOPEN
In <a href="class_gsm_client.html#ac3343dcdf3ba62f63aeb3b0775e4a93a" class="m-doc">connect()</a> (non-secure path): Should NETOPEN be called once during the GPRS connection process instead of repeatedly here?
In modemSend(): make sure requested and confirmed bytes match
In modemGetConnected(): Does this work? It's not the right command by the manual
Module simcom_sim7000ssl
:
In configureSSLContext(): Skip verifying the context number?
Module simcom_sim7080
:
In configureSSLContext(): Skip verifying the context number?
Module simcom_sim7600
:
In GsmClientSim7600 constructor: Ensure the secure socket mux isn't out of range
In gprsDisconnectImpl(): Should CCHSTOP come before NETCLOSE? Is it needed in addition to NETCLOSE?
In getGPSImpl(): Can 1 be returned
In GsmClientSecureSim7600::connect(): Should we specify the client_type as 2=SSL/TLS?
In GsmClientSecureSim7600::connect(): verify CCHOPEN
In modemSend(): make sure requested and confirmed bytes match
In modemGetConnected(): I think this only returns the TCP socket connection status, not the SSL connection status
Struct TinyGsmA7672XTcpConfig
:
I think the number of TCP and SSL sockets are independent of each other and managed completely differently. That is, I think there can be two connection 0's, one using the SSL application on the module and the other using the TCP application on the module. Could someone who has a A7672x module test the real number of TCP and SSL connections that can be made at once?
Handle the different number of sockets for TCP and SSL in the code. Member TinyGsmModem< modemType, modemConfig >::streamClear () : Should this be protected? Member TinyGsmModem< modemType, modemConfig >::streamDump (int16_t expected_len) : Should this be protected? Struct TinyGsmSaraR4TcpConfig : Handle the different number of sockets for TCP and SSL in the code. Struct TinyGsmSim7000SSLTcpConfig : Handle the different number of sockets for TCP and SSL in the code. Struct TinyGsmSim7600TcpConfig : I think the number of TCP and SSL sockets are independent of each other and managed completely differently. That is, I think there can be two connection 0's, one using the SSL application on the module and the other using the TCP application on the module. Could someone who has a SIM7600 module test the real number of TCP and SSL connections that can be made at once?
Handle the different number of sockets for TCP and SSL in the code. Struct TinyGsmSim800TcpConfig : Handle the different number of sockets for TCP and SSL in the code. Class TinyGsmSSL< modemType > : create an SSLConfig trait type to control SSL behavior and limits, similar to TcpConfig. This would handle:
- the number of SSL contexts supported by the modem
- the number of SSL sockets supported by the modem
- whether the socket numbering is shared between SSL and TCP sockets or separate
- the SSL capabilities of the modem (e.g., whether it supports PSK, client certs, etc.)
Module ublox_cellular
:
In
restartImpl(): Verify delay timing here Module ublox_sara_r4 : InrestartImpl(): Verify delay timing here Module ublox_sara_r5 : InrestartImpl(): Verify delay timing here
Generated by Doxygen and m.css with templates from doxybook2 Updated on 2026-09-11
If you like TinyGSM library - give it a star, or fork it and contribute!