DSP Robotics Support

Excuse me for flooding the board a bit, just getting a few things cleared.

How are primitives made?

If someone can point me in the right direction or provide a bit of info, it will be appreciated.

Primitives are hard coded in the FlowStone program code. There is no sdk available for developers, but you can make modules yourself using whatever resources you want, including primitives, Ruby, DSP and Assembler. You can even embed dlls created in other languages.

Cheers

Spogg

Thanks for the follow up.

Spogg wrote:Primitives are hard coded in the FlowStone program code.

I guess that's why Flowstone has great backwards compatibility.

Dlls and assembler are interesting concepts. AFAIK, assembler used to be the fastest response but now a days it's negligible.

I've been reading and exploring a bit, and correct me if I'm wrong that the DSP "Code" module can dump assembler code. Not sure if it will really benefit usage in builds to program in the DSP "Code" then migrate to assembler.

I'm new to programming but have been poking at it since I was a kid.

On another note:
I fought with triggering the "Wave Player" for an hour or two before giving up and just using a different example schematic from the forum, I didn't even use the final algorithm. "Learning Curve".

DSP code is compiled into assembler before it’s run. But no compiler is perfect at optimising code, since it follows generalised processes.

Some people extract the assembler once they have the DSP version working (from the S output connector using a string text prim), then edit the assembler code to make it more CPU efficient, and finally paste the optimised code into an Assembler code box.
Optimising in assembler can make huge differences to the CPU cycles used, depending on the complexity of the code of course.

We have a few clever souls here who can even write directly in assembler too.

Cheers

Spogg