DSP Robotics Support

Hello Gang,

Say, do any of you have any technique for keeping modules with many line in some king of order. Especially , if you have a single connection that has 20 connections or more and then several more in the same area with just as many . Sometimes I can not even see through the jumble of wires to put my next wire on and sometimes I even get it on the wrong node. I have one module I was working on got so bad, I have just given up on it. We should be able to assign colors of our own to the wires. Any ideas would really be a GREAT help.

Thanks mush, BobF.....

Here are some recommendations, hope they help:

Try to design your modules more self-contained so each has fewer connections. I know, sometimes you just can't.

I often have modules with many connections following some kind of systematics, like 64 consecutive frequency bands or so. Then I would have another module with 64 connectors in the same order face to face, so the connections would run parallel. But sometimes that is not quite possible.

Tidy up your schematic, set Options/Advanced/Link Curvature: Straight, and run connections horizontally or vertically.

Wireless connections help tidy up a spaghetti schematic, however use carefully because debugging can be a pita.

Consider using a data bus.

Hi Martin,

Many thanks! Those are all great tips. Yes, I just need to slow down a little and take some more time and let my eyes rest a little. Like you said more parallel and horizontal lines and not so many zig zagged and crossed ones.
Say, do you have a good example of using data bus?
Thanks again, BobF.....

Have a look at this image. It shows the top layer of Apex, my font to sprite font converter.
https://dl.dropboxusercontent.com/u/11182740/Flowstone/Apex_top_layer.png

I prefer straight connections, as you can see. Also, I make use of wireless connections. But only do this if you exactly know the wiring. In other words, don't start wireless, rather replace existing connections with wireless connections where it makes sense. Also, keep a consistent and unique naming definition. A wireless module output called "width" won't help you much later on, particularly when you have like 20 modules that deal with all kinds of widths. So be precise from the beginning. "projectname_osc1_send_area_width" is a much better name.

Another thing that helps might not be noticed. If you have a closer look at the schematic you will see that I collapsed all views. I don't need to see the graphics that are already displayed on the main view panel. Saves a lot of space, makes the schematic easier to maintain and makes it possible to work with less layers. Apex' depth is 2 layers only (with an exceptional third layer for the engine module).

tulamides picture is a perfect example of how to build up a straight forward structure of a complex schematic, its tidy, the flow goes always from left to right, and you have useful single modules connected wireless,

one of the most important things is to make useful modules, dont just put things in a module when it starts to get big, create logical building blocks which maybe can be used in other schematics too, every module content should easily find enough place on a 15" screen without scrolling and with clear, straight forward connections, it should be a logical structure easy to follow..

personally i also seperate GUI from stream, to keep everything in place and not having 25 knobs scattered in the main audioprocessing module, like this i get some main modules in the first level (GUI, audio processing, modulation, midi) and then break it up level for level...

specially if you have values with lots of targets it makes sense to use wireless connections, for example some modulation source..

you can have a look at one of my user examples where you can see how i build up my schematics
viewtopic.php?f=3&t=2197

restructuring and tydiing up complex schematics is time intense but it really worth it also debugging is much easier with a good structured schematic, always try to work this way, it will help you a lot in the future,

its one of the most important things in programming - make things reusable, keep things simple and tidy, also if it is a complex big thing break it down into small and simple modules, methodes or functions..

Hey Guys,
Many thanks! I believe these examples will really go a long way in helping me. Thank you so much for responding. I am also sure many others will benefit from your information tips and schematics as I will. I may even go back and try finishing a module I started some time back that I just gave up on as it had so many connections.
Much appreciated, BobF.....

BobF wrote:Say, do you have a good example of using data bus?

Didn't notice it until now. No good example, but find the simplest example of how to use a bus below.

Hello Gang,

In my never ending quest to make schematics cleaner I came up with this idea. Now this is NOT a real project that I am working on at all and is just for demo-ing the idea. By combing an input and output primitive into a module I can make cleaner looking schematics. Now this is a little over kill of course, but I just wanted to show that it does seem to work just fine.

Is this ok, or does anyone see problems with this idea?

Many thanks!
Later then, BobF.....

Hi BobF

Not sure if the concept would cause issue ...

I wonder, would a 'Wire-Less' connector be easier to work, and cleaner schematic ?

BobF wrote:

Bobs1-1ExpanderTest.fsm

Hello Gang,

In my never ending quest to make schematics cleaner I came up with this idea. Now this is NOT a real project that I am working on at all and is just for demo-ing the idea. By combing an input and output primitive into a module I can make cleaner looking schematics. Now this is a little over kill of course, but I just wanted to show that it does seem to work just fine.

Is this ok, or does anyone see problems with this idea?

Many thanks!
Later then, BobF.....

Looks like you've solved your own daisy-chaining idea!
I like this as opposed to wireless because it's easier to see the signal flow immediately.

Cheers

Spogg