Skip to content
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

Support need for TCP : +RECEIVE missed event #50

Closed
gxnt-samir opened this issue Mar 18, 2021 · 7 comments
Closed

Support need for TCP : +RECEIVE missed event #50

gxnt-samir opened this issue Mar 18, 2021 · 7 comments

Comments

@gxnt-samir
Copy link

Hello @MaJerle,

I have send a request on TCP and expecting server to respond.

The server respond too but missed the first reveive to call the function callback.
I have marked the breakpoint in the attached log.

For simulation when i send dummy data from server the 2nd time, it hit the marked breakpoint.
I have tested manytimes and tried many approach. But it always miss the 1st response from the server.

Can you please support. In my real application the server is actually responding once. if missed the important data is lost.
Can you suggest any alternatives to track this receive buffer by application?

Regards,
Samir

Missed event breakpoint

@MaJerle
Copy link
Owner

MaJerle commented Mar 18, 2021

Hi @gxnt-samir more info would be necessary. We need to see 2 things:

  • Actual data from modem
  • Data visible by your microcontroller or computer. Are you sure that you are not missing any bytes received from the modem?

@gxnt-samir
Copy link
Author

Hello @MaJerle ,

Thank you for your response.

I am attaching the actual MCU - Modem communication log.
actual modem-mcu data

@gxnt-samir
Copy link
Author

As you can see, the +RECEIVE has been received from Modem interface with the response data, but this received data didnot triggered the event.

@MaJerle
Copy link
Owner

MaJerle commented Mar 18, 2021

Question is rather, did MCU really got these data from the modem? Or was there read data processing error? And is number of data received really 1460 bytes? Check all this first please

@gxnt-samir
Copy link
Author

This print is executed by the MCU at just before passing to lwgsm_input_process API. You can see my iostream write API just before it.

Uart Print of receive

@gxnt-samir
Copy link
Author

So, Yes the data is actually receiced by MCU, and its 1460 bytes. The image is croped so the data is not showing full. Do you have any way i can debug further. any specific function or value that can give me any clue.

@MaJerle
Copy link
Owner

MaJerle commented Mar 18, 2021

It is super strange. Would be good to see if you go in to input_process function.

@MaJerle MaJerle closed this as completed Jul 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants