---
title: "Segment ID issue"
url: "https://maker.wiznet.io/forum/14995"
markdown_url: "https://maker.wiznet.io/forum/14995/md"
type: "Forum topic"
category: "Wireless"
author: "Padmini"
created: "2023-08-02T10:33:23+09:00"
last_activity: "2023-08-02T13:38:02+09:00"
language: "en"
views: 242
replies: 1
source: "WIZnet Makers forum (https://maker.wiznet.io/forum/)"
---

# Segment ID issue

## Question

Asked by Padmini on 2023-08-02 in Wireless.

Continuing the discussion from [Regarding AT+CIPBUFSTATUS Response](https://forum.wiznet.io/t/topic/11135):

Hi Team,

Can you please respond to the above attached Segment ID Issue.

Thanks,
Padmini

## Replies

### Reply 1 by Padmini, 2023-08-02

Sometimes, we see the discrepancy in the segment ID sent Bytes .

**63676,64328,63675,15360,10**

Due to the below condition, we are not able to reset the segment ID when segment ID reaches its maximum limit (65535/ 2 Bytes)

*Only when next segment ID - segment ID sent = 1, can AT+CIPBUFRESET be called to reset *
*the counting.*

In this type of situations, what should be the expected action to reset the Segment ID count ?

---

Source: https://maker.wiznet.io/forum/14995