Request response example about sub-iot-stack HOT 4 CLOSED

This is correct.

I was implementing this part when the new draft was discussed in the protocol action group of the alliance.

I’m implementing this draft now in the draft branch and I didn’t find time to implement the query in the master anymore.

The draft simplifies the querying enormously, since the discussions are now going on on what should be in that spec, I’m focussing my efforts currently in testing the draft.

Maarten

From: rith87 [mailto:[email protected]]
Sent: 01 September 2014 07:26
To: CoSys-Lab/dash7-ap-open-source-stack
Subject: [dash7-ap-open-source-stack] Request response example (#9)

In the example, I've observed that the requester receives a response from the responder but the response is empty (all 0's). I dug into it a little bit and noticed that trans_tx_query is not consuming the payload in the file template.

void trans_tx_query(D7AQP_Command* command, uint8_t subnet, uint8_t spectrum_id, int8_t tx_eirp)

{

...

switch (command->command_code & 0x70)

{

    // Response

    case D7AQP_COMMAND_TYPE_RESPONSE:

    {

        switch (command->command_code & 0x0F)

        {

            case D7AQP_OPCODE_ANNOUNCEMENT_FILE:

            {

                break;

            }

        }

        break;

    }

...

}

The same behavior happens on the rx side as well. Or am I misunderstanding the code?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9.

from sub-iot-stack.

not the best place to discuss this, but i noticed a lot more activity on master recently. we are looking to use a dash7 implementation but a bit worried about the maturity. can you speak to the completeness/testedness/etc.?

from sub-iot-stack.

OSS-7 does not implement the current draft standard (v0.2) completely at the moment, nor is extensively tested yet.
Version 1.0 of the standard will normally be voted in december. The draft branch is working towards implementing version of v1.0 of the standard, but not all functionality is complete yet (and may need more changes to comply with v1.0 final anyhow).
Most development will happen on draft and will be merged back to master once v1.0 is voted.
That said, we hope to invest more time in development beginning of next year (when v1.0 of the standard is final) to fully implement the standard and do extensive testing.
The alliance goal is that oss-7 should be the reference implementation against which other implementations should be tested for validation. So naturally this means oss-7 needs to completely implement the standard.

PS: a better place to discuss this would be on the mailing list (http://groups.google.com/group/dash7-ap-oss)

On 11/19/2014 08:32 AM, Daniel Myers wrote:

not the best place to discuss this, but i noticed a lot more activity on master recently. we are looking to use a dash7 implementation but a bit worried about the maturity. can you speak to the completeness/testedness/etc.?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-63602279.

from sub-iot-stack.

not relevant anymore after rewrite, closing for now

from sub-iot-stack.