NWMUDS:PullPacket: Difference between revisions

From 3dbrew
Jump to navigation Jump to search
 
(9 intermediate revisions by the same user not shown)
Line 9: Line 9:
|-
|-
| 1
| 1
| u32 NodeID which was used with [[NWMUDS:Bind]] by this device.
| u32 [[NWMUDS:Bind|BindNodeID]].
|-
|-
| 2
| 2
| OutBufSize >> 2
| 4-byte aligned MaxOutBufSize >> 2
|-
|-
| 3
| 3
| Output buffer size
| MaxOutBufSize
|}
|}


Line 47: Line 47:
|-
|-
| 3
| 3
| u16, source NodeID. Same as the input dst-NodeID when this device is a spectator.
| u16, source NetworkNodeID.
|-
|-
| 4
| 4
Line 57: Line 57:


=Description=
=Description=
This receives a broadcast data frame, while connected to the UDS network. The first 0xE-bytes of the actual data-frame data is a header parsed by NWM module, the data following that is the data written to this output buffer.
This loads a previously received ''individual'' data frame from state, while connected to the UDS network. This includes all frames received from a node before the node disconnected. The input size must be >= frame_size, otherwise error 0xE10113E9 is returned.
 
The MaxOutBufSize_wordsize is clamped to 0x172(aka 0x5C8-bytes), but this field isn't really used after that. Instead it just uses MaxOutBufSize, without a size limit.

Latest revision as of 22:00, 27 April 2016

Request

Index Word Description
0 Header code [0x001400C0]
1 u32 BindNodeID.
2 4-byte aligned MaxOutBufSize >> 2
3 MaxOutBufSize

The following is located 0x100-bytes after the beginning of the above command buffer:

Index Word Description
0 (OutBufSize<<14) | 2
1 Pointer to the output buffer

Response

Index Word Description
0 Header code
1 Result code
2 Actual data size
3 u16, source NetworkNodeID.
4 (OutBufSize<<14) | 2
5 Pointer to the output buffer

Description

This loads a previously received individual data frame from state, while connected to the UDS network. This includes all frames received from a node before the node disconnected. The input size must be >= frame_size, otherwise error 0xE10113E9 is returned.

The MaxOutBufSize_wordsize is clamped to 0x172(aka 0x5C8-bytes), but this field isn't really used after that. Instead it just uses MaxOutBufSize, without a size limit.