Reliable Compiled Code Size on NI700 32 MB model
jdonachiue@shaw.ca
Posts: 57
I am not onsite and I do not have the same model NI700 to test with...
Any insight will be greatly appreciated.
Thank you in advance.
THE INFO
NI700:
FG2105-03 • 32 MB SDRAM (not upgradeable)
• 16 MB Flash chip (not upgradeable)
• 512 Kb of Non-volatile SRAM
I have generic code and it compiles to:
//#define SYS_HAS_32MB True;
When this is Commented out Compiled Code Size is:
998665 Bytes
#define SYS_HAS_32MB True;
When this is Un-Commented Compiled Code Size is:
534924 Bytes
THE QUESTION
What Compiled Size can I reliably run on a 32MB System with 2 Duet Modules?
Any insight will be greatly appreciated.
Thank you in advance.
THE INFO
NI700:
FG2105-03 • 32 MB SDRAM (not upgradeable)
• 16 MB Flash chip (not upgradeable)
• 512 Kb of Non-volatile SRAM
I have generic code and it compiles to:
//#define SYS_HAS_32MB True;
When this is Commented out Compiled Code Size is:
998665 Bytes
#define SYS_HAS_32MB True;
When this is Un-Commented Compiled Code Size is:
534924 Bytes
THE QUESTION
What Compiled Size can I reliably run on a 32MB System with 2 Duet Modules?
0
Comments
One way you could test is to put it on another master first taking note of its memory shown using an empty program and the doing the math to see how much is used by the running program. If it fits it'll work.
I will set things up for a minimal runtimne memory usage and adjust when I get to site.
What level Memory would Duet Modules reliably run in?
Thank you again.
Not trying to be coy but the answer is basically the same: it depends...
For example a duet module that controls a simple device will probably use less.
Typically the lowest duet memory I set is 8. But I'm typically up around 12~24
I have some install with way more but they're running quite a few duet modules.