Hi guys,

I am currently in the 30 day trail. I have a few questions and wish for them to be answered with the technical answers and the not so technical answers.

For this product I decided to evaluate it against a few others. I work for a company and we are looking to upgrade the software.
I have a design plan....block diagram within an old program.....I have printed it off and recreating it within stardraw.

1 - The cable runs are problematic (this is by no means an insult to the program development) I just wish for someone to explain why connecting cable lines together is such an issue.

2 - Symbols are a bit limited and if you was not to renew the subscription service I am guessing you would lose the ability to add stubs to products.

3 Why can we not add just one terminal that has a node to a product? not a line or something like that but a blank hole so to speak that the cable connects to.

I like the program and it has great potential I just see the cable aspect as bit of problem, THIS COULD BE BECAUSE I AM MISS SOMETHING and I am prepared for that to be the case. 

Any Help or advice would be greatly appreciated.

I include a picture of what I wish to create and the issues I am having with descriptions.    (oh the blue dots is where I would like the cables to connect....why dose it not have connection points or snap to the line unless you want to go past it like underneath)

Hi Jay,

Thanks for posting further information. Yes, I think I understand what you're getting at.

First of all I'll say that multicores, currently, are not supported ideally and there is not a 'multicore object' as such. Improved multicore support is something we're looking to cater for in a future version, and that may well be the answer to your queries. Perhaps, also, what follows may well help explain why things are the way they are.

The design and conceptualization of Block Schematics in Stardraw Design 7 has evolved, so far, with these principles in mind:
1) It is a logical view, not specifically a 'physical' view, of connections between products.
2) It focusses on discreet signal levels, not the individual core/pin level. What I mean by this is that Stardraw Design 7's design for Block Schematics expects the user to show, for example, a balanced audio signal as a single coherent path, or Cable, but does not expect to show, in most cases, the individual hot, cold and screen cores in the foil screened twin cable (although you can, of course, do this).

So perhaps that's the disconnect between what you're experiencing and what, ideally, you'd like to see. Unlike the PCB and wire examples you mention, Stardraw's Block Schematics generally show that this audio, or video, or control, or data, or network, or power signal go from this thing to that thing, rather than that the blue core goes from here to here, while the blue/white core goes from there to there, while the orange core goes this way, and so on.

To restate, then, the imagined use case is that people are, on the whole, documenting logical signal paths rather than physical core paths.

I hope that makes some sort of sense.

Going further, then, the Pictorial Schematics Module is an ultra-high level view which is along the lines of 'this thing connects to that thing' while Block Schematics shows 'this signal path runs from this device to that device(s)' while maybe what you're seeking is a view that demonstrates 'this core runs from this physical point/pin to that physical point/pin'.

But overall i think we're more or less on the same page; most of what you want to do you can do today, and we hope to introduce an amazing multicore tool in due course. As to connecting Cables - we consider everything our licensees suggest and prioritize development based on what the market wants and what features deliver the most 'bang for buck', so nothing should be ruled out.

Regarding your follow up question about auto-updating changed products, there isn't a project- or drawing-wide auto-updater, but there is an accelerator: delete the UDP symbol in the drawing, it will return to the Available Symbols Palette, and when you drag that product back out of the Available Symbols Palette it will use the new UDP symbol to which you've made changes.

I hope this is helpful.

Kind regards,
Rob Robinson
Stardraw.com

+x

 

Rob Robinson - 9/27/2019 1:52:57 PM

Hi Jay,

Thanks for posting further information. Yes, I think I understand what you're getting at.

First of all I'll say that multicores, currently, are not supported ideally and there is not a 'multicore object' as such. Improved multicore support is something we're looking to cater for in a future version, and that may well be the answer to your queries. Perhaps, also, what follows may well help explain why things are the way they are.

The design and conceptualization of Block Schematics in Stardraw Design 7 has evolved, so far, with these principles in mind:
1) It is a logical view, not specifically a 'physical' view, of connections between products.
2) It focusses on discreet signal levels, not the individual core/pin level. What I mean by this is that Stardraw Design 7's design for Block Schematics expects the user to show, for example, a balanced audio signal as a single coherent path, or Cable, but does not expect to show, in most cases, the individual hot, cold and screen cores in the foil screened twin cable (although you can, of course, do this).

So perhaps that's the disconnect between what you're experiencing and what, ideally, you'd like to see. Unlike the PCB and wire examples you mention, Stardraw's Block Schematics generally show that this audio, or video, or control, or data, or network, or power signal go from this thing to that thing, rather than that the blue core goes from here to here, while the blue/white core goes from there to there, while the orange core goes this way, and so on.

To restate, then, the imagined use case is that people are, on the whole, documenting logical signal paths rather than physical core paths.

I hope that makes some sort of sense.

Going further, then, the Pictorial Schematics Module is an ultra-high level view which is along the lines of 'this thing connects to that thing' while Block Schematics shows 'this signal path runs from this device to that device(s)' while maybe what you're seeking is a view that demonstrates 'this core runs from this physical point/pin to that physical point/pin'.

But overall i think we're more or less on the same page; most of what you want to do you can do today, and we hope to introduce an amazing multicore tool in due course. As to connecting Cables - we consider everything our licensees suggest and prioritize development based on what the market wants and what features deliver the most 'bang for buck', so nothing should be ruled out.

Regarding your follow up question about auto-updating changed products, there isn't a project- or drawing-wide auto-updater, but there is an accelerator: delete the UDP symbol in the drawing, it will return to the Available Symbols Palette, and when you drag that product back out of the Available Symbols Palette it will use the new UDP symbol to which you've made changes.

I hope this is helpful.

Thank you Rob that was awesome :-)