0% found this document useful (0 votes)
74 views1 page

Questions:: Without Being Polled

The document discusses packet transfer formats between a controller and slave devices and asks questions about the format used. It asks if the format is variable based on ASCII characters or fixed with a defined packet structure including device ID, function, arguments, payload, and CRC. It also asks about further code changes and flow details needed for slaves and expresses doubts about using a variable ASCII-based format due to potential collisions from unsynchronized transmissions and less efficient transmission compared to a fixed format.

Uploaded by

Asad Malik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
74 views1 page

Questions:: Without Being Polled

The document discusses packet transfer formats between a controller and slave devices and asks questions about the format used. It asks if the format is variable based on ASCII characters or fixed with a defined packet structure including device ID, function, arguments, payload, and CRC. It also asks about further code changes and flow details needed for slaves and expresses doubts about using a variable ASCII-based format due to potential collisions from unsynchronized transmissions and less efficient transmission compared to a fixed format.

Uploaded by

Asad Malik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Questions:

1. Is the packet transfer between controller and slave based on:

a) Variable packet format (ASCII BASED) (for e.g INFO: ID +12 bytes ID in ASCII + \r\n)

OR

b) Fixed packet format (RS485 message type (ID_Device + Function + Arguments + data payload +
CRC) = 26 Bytes?

2. Information about further Changes and Sequential flow details of the code to be implemented for
slaves.

Doubts to be confirmed:

1. The slaves transmit initially the build ID and size of ID, without being polled, this could result in
collisions.
2. The transmission between slaves and controller would not be very efficient if variable packet format
based on ASCII characters is used, causing excess transmission delays as compared to fixed packet
format.
3. In the latest version of slave code, if we consider variable Packet format based on ASCII, error
detection is not used, i.e CRC (cyclic redundancy check) is not used.

You might also like