Conrad Preen
-
Posts
1,262 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Conrad Preen
-
-
@CharlesD generally I'd agree that supporting import / export is a good idea. Finding the resources to implement it all can be a bit challenging...
Updating large numbers of device definitions will need scripting.
Conrad
-
1
-
-
@ChollyO I will check on that and file a bug if necessary.
-
@KAAC cutting to the chase a bit... you have a bunch of device data in a worksheet and you want to create as an end result is a bunch of device definition symbols (with default graphics) in a Vectorworks document saved to a place of your choosing. Would that summarise your needs?
The reason I ask is because I can see such a utility being helpful in content creation generally. That kind of exists internally so we could tidy that up and release it.
Regarding your questions:
1 - yes that sounds good
2- That would be created by the Migration Manager when you migrate the user folder database. Effectively it's doing the workflow I'm asking you about above. Which leads to a sneaky thought that you could add all your device data in the old database format and migrate it to create a bunch of device definition symbols.
3 - That's right both are created. I would always share the device definition because that gives you the 3D symbol that will be used in layout equipment items plus the device builder data. If you like to have special graphics in your schematic devices then you might share the red symbol too. It's up to you.
-
1
-
-
@KAAC Thank you for your specific comments! I will do my best to address them below.
"We have a lot of devices to build in CC and my decision for the team is whether to start working in 2025 or 2026." Use the latest version every time. Software never goes backwards.
"VW 2026 - removes the 'Save To Database' option". Not exactly. If we are talking about the Device Object Info Palette buttons, we have merged the functionality of the 2 buttons into 1. Since in the new scheme of things we don't have a database as such but are saving to a record attached to a symbol both buttons would logically be named Save As Symbol! So it made sense to have just one button doing both.
The old text file database was a temporary measure to integrate the online community device sharing that had been part of ConnectCAD prior to the acquisition by Vectorworks. It was far from ideal. If you wanted both nice 3D symbols and shared device data these had to be kept in sync manually. Now if you want to share a device definition with a colleague all you need to do is put a 3D symbol in a shared folder. It's a lot easier.
I agree that locating the symbol+device definition in the Resource Manager for a given schematic device's make/model could be made easier. But that is more to do with the Resource Manager than ConnectCAD. Believe me we are pushing in that direction. Being deeply integrated in Vectorworks sometimes means we have to move the whole ship along with us. However, don't forget that symbols+device definitions are just rubber stamps for creating device instances. Editing the record will not change your schematic. That's by design.
Could Vectorworks handle workgroups better generally? For sure! There is a lot more to do there. We are working with our colleagues to improve this.
Vision for the future: Integrate the Device and Device Builder tools into one tool. Be able to edit device instances in the device builder dialog as a mode of this tool. Improve socket placement tools to apply same naming rules as device builder. Review all tools to ensure that sensible context-aware defaults are applied. Timeline depends on whether resources are free to develop and test.
"is there a plan to add the ability to create devices directly via the device builder when 'Save As Symbol 'is triggered?" No. This will be integrated into the Device tool.
"Are devices created in 2026 available to choose and place on the page via the device builder?" Yes. The Device Builder in 2026 looks at symbol content, not the old database.
"In 2026 when creating devices from a worksheet does CC look for pre-built device availability only in the pre-2026 text file device database or also in the local file for symbol devices created in 2026. Does it look in the workgroup at all for devices?". It uses exactly the same code as the Device Builder. It looks for symbols in: open documents, user folder content, workgroup folder content and application folder content. The old database file is not used any more.
Hope I've helped a bit. I'm aware that change can be unpopular but this was something we had to clear up.
Conrad
-
1
-
-
@Antti Eronen Thank you for sharing your opinion. Of course there are further steps to be taken on this journey. Reading your comment multiple times I do not see any mention of specific issues. This Did You Know thread is my humble attempt to have one place forum where you can find stuff that you might want to know. So let's continue this conversation on a separate thread please.
@KAAC relying to you here
Conrad
-
1
-
-
@KAAC @Antti Eronen I'm starting this thread to continue discussions relating to the new device definition workflow and keep the Did You Know thread as a how-to repository.
-
If the speakers are a separate locations I would either put a drop for each speaker, or just skip the drop point altogether and draw a cable path going from one speaker to the next.
Drop points are handy for the case when you don't know what your equipment will be but you still have to specify ducts and cabling.
Best
Conrad
-
You will be able to define which signals are compatible with a given signal type. i.e. an input (or I/O) with a particular signal type will accept incoming signals on its compatibility list. The scope here is just to suppress unwanted warnings in the Status palette.
-
I think you've answered yourself in a way. There are limits to how much ConnectCAD should 'know' about what you are doing. Its job is to help you design, not act like some annoying back-seat driver. The sheer constantly expanding and changing range of options mean that this stuff is what designers get paid the big bucks for. So for me signal compatibility comes down to telling ConnectCAD that a particular signal type mismatch is OK. That's as deep into the weeds as we go.
C
-
1
-
-
For half-rack items we can't use our new symbol paradigm because the mounting 'ears' need to be drawn dynamically. Cleanest solution I think is to define half-rack items as though they were none-rack, and put them in a 2-slot rack frame in rack-tray mode. That way they'll snap nicely and you only need one symbol. In terms of reporting the tray is almost like a side-by-side mounting kit which is something manufacturers love to charge for anyway.
My 2c worth
Conrad
-
1
-
-
Hi Charles,
This is one of those where a fairly simple script can do wonders.
We can discuss how to do this.
Conrad
-
@Liz Gubler What you are picturing there looks to me like a classic case of a device with option cards.
The best way to handle this is to define the cards as adapters. On the schematic you define the main device with a socket for each card slot (signal type proprietary = $$$). Name them for example SLOT1, SLOT2 etc. Then use the Adapter tool to place adapter cards on the slot sockets you just created. On your layout drawing you create an Equipment Item of the correct number of rack U high and give it the same name as the schematic device that represents it. Now rotate the Equipment Item so you can see the back of it, and use the Adapter Slot tool to draw the physical slots on the back named SLOT1, SLOT2 etc. When the schematic slot sockets match the adapter slot names the adapter type will be displayed automatically in the slot on the equipment.
Conrad
-
@Bluetones Well let's see...
In 2026 we have changed the way we store library device definitions. They used to be stored in a text file and now we attach a ConnectCAD Device Definition record to symbols instead. This is similar to the way Spotlight defines lighting devices - they have a 3D symbol that models the physical light, and a Light Info record that carries all the data for that particular model.
In ConnectCAD we now do the same. Our library now comprises 3D symbols for each model with a ConnectCAD Device Definition record attached which has all the information needed to create a schematic Device or an Equipment item. The 3D symbols define device types. Device and Equipment objects are instances of these types.
The device type acts like a rubber stamp for creating Devices and Equipment. If you edit the rubber stamp previously created instances are not affected. This is intentional. It saves you from unintended consequences in complex drawings. The flip side of that is that making global changes is more involved. That makes sure that you view such changes in context rather than discovering a problem during installation.
When you want to create a variant of a library device now, the process starts with importing the original device type symbol or duplicating it if it's in your document. Then still in the Resource Manager right-click on the duplicate, and select the context menu Edit Device Definition. In the dialog you can make any changes you need and change the model number to something new say "MyWidget". Then when you save the device definition you can use it in the Device Builder and the Equipment Item tool to place instances of your variant of the library device. So basically it's the same duplicate-modify workflow but in the Resource Manager instead of in the drawing.
The key thing about this change is that it makes sharing device definitions as simple as sharing a symbol. It also opens great possibilities for the future.
Conrad
-
2
-
-
-
@CharlesD I'm still a step ahead it seems 🙂. Signal compatibility is in development as we speak. When the source and destination signals are different but compatible error indications will be suppressed and the circuit will take the source signal type.
Agree with your point about content. It's a question of resources.
Connector compatibility. Connector types multiply constantly so this would become another thing to keep up to date. I think most designers know this stuff anyway.
Conrad
-
1
-
-
@ZaPD I don't think it's a problem to add this as an option in that dialog. I will file an enhancement request. Can't give you a time frame right now. Conrad
-
1
-
-
This is on our list to do something about. The proxy arrow really needs to act as a proxy also for attached records and that would seem to make sense in other contexts where proxies are used. We'll look into it, and thanks from raising the question!
-
1
-
-
@Bluetones Just to cut to the chase here, if you like do PM me the file(s) in question and a the steps I need to take to reproduce the problem and I will have a look at it.
Conrad
-
@Greg Abel I can reproduce this in Vectorworks 2025 but it seems to be all working in Vectorworks 2026. What version are you using?
-
Yes please migrate first! Copy-paste between different Vectorworks versions is quite a stretch!
-
@ZaPD I get it from the perspective of readability. But, my worry is that there's isn't a clear rule for when to ignore the intermediate device (e.g. jackfield) and what to consider as an intermediate device. The last thing I want is a plethora of checkboxes that change the rules in mysterious ways.
I will think about it. And please feel free to offer suggestions.
Conrad
-
-
-
Updates only affect the application folder.
-
1
-
Data tag linked to an equipment item itself associated with a device
in ConnectCAD
Posted
@mobrist hello! here's an idea that might get you close to what you want without scripting.
If we're talking about stand-alone equipment (not rack mounted). You can place your equipment on a your layout drawing, draw the cable paths linking each equipment to wherever it gets its signal from, run Analyse Cable Routes and then Create Cabling Sheet. This will give you a sheet layer with a viewport showing the layout with the Equipment and annotations that list the cabling on each route.
If your adjust Create Cabling Sheet to only place arrow-style annotations I think that's quite close to your goal. Try it and let us know.
Conrad