search

nurhidayat86 / ERTS

1 stars 0 forks source link

Communication protocol #10

Closed nurhidayat86 closed 8 years ago

nurhidayat86 commented 8 years ago

Create reliable communication channel.

anggairawan commented 8 years ago

@nurhidayat86 @rviset The current protocol worked good enough. We are not sure about the speed (because of the large size) and also the ACK problem.

nurhidayat86 commented 8 years ago

Need to change len based on the msg_id, to supress the possibility of getting very large payload due to len identification error

nurhidayat86 commented 8 years ago

The ACK did not work for control input mode due to many bytes on the serial that wait for ACK (tested yesterday together with other team), However it is needed for the log msgs transfer from ESD to PC. Also the header file cannot be made based on the msg_id due to input device often generated random msg into the serial (dont know why), we got this event from the joystick w/o protocol (js sends so many random chars including esc), so we look for one very unique identifier that will never appear in the random msgs.

nurhidayat86 commented 8 years ago

DOne

nurhidayat86 commented 8 years ago

Yet to do: Ack