PJON acknowledge specification links update

gioblu · Jan 27, 2018 · 6fd4c1f · 6fd4c1f
1 parent 109b9c4
commit 6fd4c1f
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/specification/PJON-protocol-acknowledge-specification-v1.0.md b/specification/PJON-protocol-acknowledge-specification-v1.0.md
@@ -36,7 +36,7 @@ Channel analysis       Transmission                 Response
 |_____||____|__________|________|____|_________|____||_____|
 ```
 
-The graph above contains a standard packet transmission with synchronous acknowledge request where the character `@` or `64` is sent to device id `12` with `00000100` header. As defined by the [PJON protocol layer specification v2.0](/specification/PJON-protocol-specification-v2.0.md) the third bit from right up in the header requests to transmitter a synchronous acknowledge response. How the synchronous acknowledgement procedure works depends on the medium and the strategy used, see [PJDL v2.0](/strategies/SoftwareBitBang/specification/PJDL-specification-v2.0.md), [PJDLR v2.0](/strategies/OverSampling/specification/PJDLR-specification-v2.0.md), [PJDLS v2.0](/strategies/AnalogSampling/specification/PJDLS-specification-v2.0.md) and [TSDL v2.0](/strategies/ThroughSerial/specification/TSDL-specification-v2.0.md) specification.
+The graph above contains a standard packet transmission with synchronous acknowledge request where the character `@` or `64` is sent to device id `12` with `00000100` header. As defined by the [PJON protocol layer specification v3.0](/specification/PJON-protocol-specification-v3.0.md) the third bit from right up in the header requests to transmitter a synchronous acknowledge response. How the synchronous acknowledgement procedure works depends on the medium and the strategy used, see [PJDL v2.0](/strategies/SoftwareBitBang/specification/PJDL-specification-v2.0.md), [PJDLR v2.0](/strategies/OverSampling/specification/PJDLR-specification-v2.0.md), [PJDLS v2.0](/strategies/AnalogSampling/specification/PJDLS-specification-v2.0.md) and [TSDL v2.0](/strategies/ThroughSerial/specification/TSDL-specification-v2.0.md) specification.
 
 #### Asynchronous acknowledge
 
@@ -49,7 +49,7 @@ Channel analysis               Transmission                Response
 |__|________|______|___|______|______|__|_________|____|_____||___|
                        |RXINFO| TX INFO |       
 ```
-The graph above contains a standard packet transmission with asynchronous acknowledge request where the character `@` or `64` is sent to device id `12` with `0001111` header containing its packet id `99`. As defined by the [PJON protocol layer specification v2.0](/specification/PJON-protocol-specification-v2.0.md) the fourth bit from right up in the header requests to transmitter an asynchronous acknowledgment response and the presence of the packet id. The second bit from right up signals the inclusion of the sender's info necessary to send back an asynchronous acknowledgment packet when received.
+The graph above contains a standard packet transmission with asynchronous acknowledge request where the character `@` or `64` is sent to device id `12` with `0001111` header containing its packet id `99`. As defined by the [PJON protocol specification v3.0](/specification/PJON-protocol-specification-v3.0.md) the fourth bit from right up in the header requests to transmitter an asynchronous acknowledgment response and the presence of the packet id. The second bit from right up signals the inclusion of the sender's info necessary to send back an asynchronous acknowledgment packet when received.
 
 #### PJON™ recursive acknowledgement pattern
 In a scenario where there is no direct communication between two devices, a synchronous acknowledgement can't be obtained successfully, so an asynchronous acknowledgement packet has to be sent back from receiver to the packet's transmitter to inform of the correct packet reception.