leon
Minnow
Posts: 1
|
Post by leon on Nov 24, 2023 1:47:23 GMT
Hi all:
I'm having a problem with an RDE instruction.
I'm getting a reply from the RDE device 0x89 when I use the RDEOperationInit command.
The Request data for the RDEOperationInit command is as follows:
The ResourceID has been obtained from the RDE appliance
OperationID = 32770（0x8002）
OperationType = OPERATION_READ
SendDataTransferHandle = 0x00000000
OperationLocatorLength = 0x00
RequestPayloadLength = 0x00000000
OperationLocator = NULL
RequestPayload = NULL
Could it be that I have made a mistake or that I have misunderstood something?
Thank you.
|
|
|
|
Post by garyliu on Dec 5, 2023 6:39:50 GMT
It is valid Operation Init cmd for the info you provide.
You may check with the vendor of your device.
Here is my operation init cmd example to READ resource ID 1 for your ref and I get response successfully from the RDE device in our project:
1 0 0 0 0x00 0x80 1 0 0 0 0 0 0 0 0 0 0
|
|
|
|
Post by malbolge on Dec 5, 2023 19:47:48 GMT
Hi all: I'm having a problem with an RDE instruction. I'm getting a reply from the RDE device 0x89 when I use the RDEOperationInit command. The Request data for the RDEOperationInit command is as follows: The ResourceID has been obtained from the RDE appliance OperationID = 32770（0x8002） OperationType = OPERATION_READ SendDataTransferHandle = 0x00000000 OperationLocatorLength = 0x00 RequestPayloadLength = 0x00000000 OperationLocator = NULL RequestPayload = NULL Could it be that I have made a mistake or that I have misunderstood something? Thank you. It looks good. Check that OperationFlags is all false too. Check the other fields too, like OperationLocatorLength (0). Run an OpEnumerate to see if created an operation and if yes, run an OpStatus on it. I'm guessing it didn't - failing to instantiate an operation at RDEOpInit should generally result in no operation being created, but who knows - maybe you can get some more data from it. It's pretty weird for a READ operation to return unsupported. If a resource is missing, it should return a different opcode. If the operationID is wrong, there's an opcode for that. Maybe the device isn't very smart about transports and it's failing to send the whole Resource over the transport? Try a different ResourceID, something easy and lightweight like a Collection. Maybe you forgot some step of negotiation like NegotiateParams / RedfishParams? Finally, see whether the device isn't returning an annotation payload. |
|
