E1.20 RDM (Remote Device Management) Protocol Forums

E1.20 RDM (Remote Device Management) Protocol Forums (http://www.rdmprotocol.org/forums/index.php)
-   RDM General Implementation Discussion (http://www.rdmprotocol.org/forums/forumdisplay.php?f=4)
-   -   Frequence min responder (http://www.rdmprotocol.org/forums/showthread.php?t=1238)

Cyril January 10th, 2016 04:57 AM

Frequence min responder
 
Hi

Someone can discuss about the minimal frequence necessary for the mcu ? I code a rdm responder fully fonctionnal but I have to work in 16 MHz but I don't understand why it don't work with 8MHz ...

Thank you

Have a nice day
Cyril

hamish January 10th, 2016 08:26 AM

485 IO Interrupt driven buffering
 
Quote:

Originally Posted by Cyril (Post 2980)
Hi

Someone can discuss about the minimal frequence necessary for the mcu ? I code a rdm responder fully fonctionnal but I have to work in 16 MHz but I don't understand why it don't work with 8MHz ...

Thank you

Have a nice day
Cyril

Hi Cyril

Two main factors that determine what clock speed is required to meet the requirements of RDM.

First, IMO, set up interrupt tasks for buffering IO/485 data, thus allowing you to run other processes without missing packet data.
Built in to these interrupt driven task should be the response timing to meet the responder requirements of the standard.

Second, consider how to handle your responses when saving data to non volatile memory. Either you will have to assign the data saving to another task and then respond ahead of the save task completing.
or
Alternatively, (not my preferred answer) employ ACK timer to allow time for the data save to complete before completing a response.

I have a myriad of responder implementations running on an 8MHZ clock, running several other processes with ample resource.

Hope this helps.

Hamish

ericthegeek January 11th, 2016 10:28 PM

Quote:

Originally Posted by Cyril (Post 2980)
Someone can discuss about the minimal frequence necessary for the mcu ? I code a rdm responder fully fonctionnal but I have to work in 16 MHz but I don't understand why it don't work with 8MHz ...

The only hard requirement is that whatever clocking architecture you use, it must be able to run the UART at 250 Kbits/second. UARTs vary, but typically need a clock at 16x or 32x the baud rate.

Beyond that, it depends on the CPU, and how efficient your software is. MHz is really meaningless as an indicator of processor performance.

Cyril January 13th, 2016 08:59 AM

Thank you a lot for your advices.
Cyril


All times are GMT -6. The time now is 12:42 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.