[Howard Bray]

G’day Mike

Many thanks for that. Very helpful.

regards

-H

[Howard Bray]

Hi again

Back onto this problem ….

Can you tell me what is the compiler that sits behind the online IDE? More specifically, what are the option settings?
We can now get a successful build, however the .bin file is about 30K smaller that what the online version creates and – more importantly – it doesn’t work. The Bootloader does it’s thing and then the unit does nothing. The feeling is that it’s either some optimization issue that’s got memory mapping confused, or there’s something missing from the linker.

Any advice or suggestions will be greatly appreciated.

-H

[Howard Bray]

Hi Mike

thanks for the reply.

Can you please advise which version of GCC that’s on the wiki page we should use and can you suggest the build options? We plan to use a ST-Link with the design and would *really* like to use the emBitz enviroment.

Many thanks

-H

PS EmBitz is the new name for EmBlocks.

• This reply was modified 9 years, 2 months ago by Howard Bray.

[Howard Bray]

I have just found https://developer.mbed.org/users/mfiore/code/mDot_test_rx/
I found it as a link on Mike Fiore’s page. So much useful information, if only it compiled. There’s a problem with no overloaded function bin2hexString matching the call.

I’m puzzled as to why it’s so hard to find a working example of receiving data on an mDot. I know I’m not the only one asking, but no one has an answer.

• This reply was modified 9 years, 2 months ago by Howard Bray.
• This reply was modified 9 years, 2 months ago by Howard Bray.

[Howard Bray]

I think we’re zeroing in on the problem. My understanding is that the data_str is filled by the receiver as it’s referenced by the vector ‘data’ passed to recv(). Basically the same as the send but in reverse.

If I could find an example of the mechanics of this, it would be a great help.

[Howard Bray]

Hi Jason

Just prior to your response, I saw the mention of the receive windows. Probably as you were writing your post, I was changing my test to wait 5 secs before asking the receiver. Same result – the receiver says something has come in, but length is zero.

—————
else
{
pc.printf(“successfully sent data to gateway\n”);
}

data_str.clear();
osDelay(5000);

if ((ret = dot->recv(data)) != mDot::MDOT_OK)
{
pc.printf(“failed to get – %ld: %s, %s\n”, ret, mDot::getReturnCodeString(ret).c_str(), dot->getLastError().c_str());
}
else
{
pc.printf(“revc says something from gateway\n”);
if (data_str.length() > 0)
{
for (std::string::iterator it = data_str.begin(); it != data_str.end(); it++)
{
data.push_back((char) *it); // return it from binary to character
}

pc.printf(“successfully got data from gateway : %s (%d)\n”, data_str.c_str(),data_str.length());
}
}

[Howard Bray]

Hi Jason

Sure did. I have a small test program that sends a ‘*’ to the conduit every 10 seconds and checks the receiver after a 500mS delay (not a blocking wait). If I do nothing, I see the ‘*’ at the conduit (love the Node-RED!) and my loop reports No Packet Received. If I send something from the Conduit, my loop reports that the receiver got something after the next send, but the length is zero.

thanks

-H

[Howard Bray]

Hi Mike

Yep, the Connect example explains a lot and I’m now finding my Conduit, setting parameters, connecting to network and sending stuff. The Node-RED is an excellent testing tool.
Is there an example of receiving strings on the mDot? I’m having lots of trouble as it seems that there are timing factors that I’m not aware of.

The in on https://developer.mbed.org/questions/61950/Receive-data/ is helpful, but a 5 line example might clear up everyone’s misunderstanding.

I’m getting back an MDOT_OK but length is 0.

There’s some important factor that I’m missing here …

many thanks again.

• This reply was modified 9 years, 2 months ago by Howard Bray.
• This reply was modified 9 years, 2 months ago by Howard Bray.
• This reply was modified 9 years, 2 months ago by Howard Bray.
• This reply was modified 9 years, 2 months ago by Howard Bray.
• This reply was modified 9 years, 2 months ago by Howard Bray.

[Howard Bray]

I’m also having trouble at the mDot end using the mBed library. The linked page (above) is great from the conduit PoV but it’s the mDot end I can’t receive. Tx is OK. I cannot find any examples of code that use the library, only examples using the AT terminal.

PS I’ve just come across: https://developer.mbed.org/teams/MultiTech/code/mDot_LoRa_Connect_Example/

Very helpful, just hard to find.

[Author]

Posts