You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2024. It is now read-only.
(sysname='GPy', nodename='GPy', release='1.20.1.r2', version='v1.11-06dfad0 on 2019-11-30', machine='GPy with ESP32', pybytes='1.3.0')
Hello,
for my application I need to send long AT+CSIM commands (over 500 bytes) to the modem. Using lte.send_at_cmd with commands that size causes a crash. I followed the source code through the rabbit hole and found that the buffer behind this method is only 127 bytes big and a carriage return is automatically appended to the command here: https://github.com/pycom/pycom-micropython-sigfox/blob/Release/v1.20/esp32/lte/lteppp.c#L662 which hinders me from sending my command in several chunks.
Is there maybe another way to safely write to the UART without a carriage return being added?
Thank you!
The text was updated successfully, but these errors were encountered:
I am experiencing the same issue, we are sending long command APDUs to the SIM card via AT+CSIM and we run out of space for some commands. This issue is almost 2 years old now, could you please fix it?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
for my application I need to send long AT+CSIM commands (over 500 bytes) to the modem. Using
lte.send_at_cmd
with commands that size causes a crash. I followed the source code through the rabbit hole and found that the buffer behind this method is only 127 bytes big and a carriage return is automatically appended to the command here: https://github.com/pycom/pycom-micropython-sigfox/blob/Release/v1.20/esp32/lte/lteppp.c#L662 which hinders me from sending my command in several chunks.Is there maybe another way to safely write to the UART without a carriage return being added?
Thank you!
The text was updated successfully, but these errors were encountered: