Device definitions

[Conrad Preen]

On 3/7/2026 at 1:10 PM, fips said:

"Half-Width" Rack objects behave weird (I didn't notice anything strange before, but can't remember). Now the 19" lugs are in the symbol object. Personally I don't need such a detail level, the half width module could be without any lugs, but snap to both sides of a rack.

 

@fips and @everyone can't tell how much easier it would be for us NOT to draw those lugs. So please give this a thumbs up if you agree to "no lugs" !!!

[Conrad Preen]

On 3/8/2026 at 1:38 AM, Brian Lawrence said:

I am trying to do this as well. I have had success by replacing the ConnectCAD Devices DB file in my 2025 folder and importing from there. However, I would like to be able to import the file from another location for convenience.

Totally agree with you. I will have a look and see how we can do that.

 

Conrad

[spettitt]

27 minutes ago, Conrad Preen said:

 

@fips and @everyone can't tell how much easier it would be for us NOT to draw those lugs. So please give this a thumbs up if you agree to "no lugs" !!!

As long as the lugs stay for full-width, yes - no lugs for half width for me!

[Conrad Preen]

@spettitt Yes just to clarify, full-rack would stay with lugs.

 

The Vectorworks problem is that we would need a left-hand and right-hand version of the symbol if we include the lugs and that breaks the model. But when you think about  the real world, you always need to order a side-by-side mounting kit with half rack equipment - the number of times that has caught me out when I was in a hurry! So in many ways it would be better to have half-rack items without lugs and place a 2-slot rack frame to model the mounting kit. At least that way the mounting kit appears on the equipment report and reminds you to order it.

 

Conrad

[CharlesD]

@Conrad Preen I agree with your take on this for mounting kits. After you explained it to me last fall, I've been doing just that-- and modeling my mounting kits as rack frames.

I agree, the lugs break the model-- and as it stands I think there's less friction to get rid of them for half rack width items (but keep them for full rack width items)

[Micah Johnson]

 

On 12/5/2025 at 8:56 AM, EricSeipel said:

You can color me stupid, and i probably go about this the complete backwards way.... but i would like to get onboard with the "official" correct way assuming it makes sense and is just as easy...

 

Currently I have an excel file with the definitions of all my devices, and add more when needed.

I export that as Tab separated as "ConnectCAD Devices DB.txt" to the Database folder.

When needed i export my job from our inventory software, paste it into a worksheet and hit Create Devices From Worksheet.

Everything gets added and i connect the lines...

It was very fast to add a new device export and create devices instantly from a worksheet.

 

Is this STUPID, SLOW, WRONG, ETC ?

What is the correct way to do this going forward?

Do i need to add every device to a drawing as an object? Save a "Library" file? How does vectorworks know to create devices from that "Library" file?

 

The old way seemed intuitive, and this new way i either haven't found enough documentation or I'm just not getting it.

 

On 10/21/2025 at 5:50 PM, Conrad Preen said:

@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.

 

 

Hi @Conrad Preen / All,

 

I'm a new Vectorworks/ConnectCAD user trying to set up our company device library so we can build our first project.  I have a whole bunch of device info in a CSV and was trying to go down the "create device from worksheet" to populate a vwx with devices, and was then intending to 'eyedropper' the socket data onto my new devices so they all had power and dmx in/thru etc. in standardised places (and so I dont need to go an create them all one by one).  Creating the devices seemed to work fine but when I eyedroppered it wrote over their make and model as well as the socket info - obviously not helpful when trying to build our library.

 

From the above, it seems like other users are having success simulating a 2025 to 2026 migration and inserting the device data they want in the interim .txt file before importing it into 2026, and it seems this might be the best route for me also.  Problem is I only have 2026 installed, and the 2025 install manager doesn't seem to be working.  This means I dont have access to a template 'ConnectCAD Devices DB.txt' that i can populate with our device library so it can be imported.  I have tried just exporting my .csv as a tab delimited .txt file with the same filename, but vectorworks says "The specified location does not contain any recognised files that can be migrated. Please specify a different location."

 

So, couple of questions:

 

1. Can I get my hands on a 'ConnectCAD Devices DB.txt' example file without having to install 2025 so i can see the format (and/or clearer instructions if there's something else I'm doing wrong here)

2. Is my understanding correct that i will be able to import this file to build a library of devices to use that have their sockets populated?

3. Or (ideally) is the bulk import tool you discuss above now released/ready for use, and will that fill my need much more easily?

4. and finally, now that the device database and the resource manager/object files are combined, should we expect manufacturers to populate their downloadable libraries with device information over time? (the devices I'm using are in the libraries, but only as 3d/2d objects for sptolight, not -seemingly - devices for connectCAD)

5. Once my devices are nicely in there, ideally I'd like to be able to dropper graphics or socket info or other parameters independently - I'm sure I read somewhere this was possible at one point, but i can only figure out how to dropper the socket info AND the make/model together.  Is this a feature that exists?

 

Thanks in advance

[KAAC]

Hi @Micah Johnson

 

Are you using the Device eyedropper tool or the standard eyedropper.

 

TXT file attached so you can see the formatting but not sure if it will be much use for your purposes.

 

The quickest way we found to create devices was to use the device builder.

 

You can try a script to fill in the dimensions, power etc. for the devices you have created via the 'create devices from worksheet' command if you have this information in your csv file.

 

I know of no way  to create sockets from a script unfortunately.

ConnectCAD Devices DB.txt

[Micah Johnson]

4 hours ago, KAAC said:

Hi @Micah Johnson

 

Are you using the Device eyedropper tool or the standard eyedropper.

 

TXT file attached so you can see the formatting but not sure if it will be much use for your purposes.

 

The quickest way we found to create devices was to use the device builder.

 

You can try a script to fill in the dimensions, power etc. for the devices you have created via the 'create devices from worksheet' command if you have this information in your csv file.

 

I know of no way  to create sockets from a script unfortunately.

ConnectCAD Devices DB.txt 1.44 kB · 0 downloads

 Thanks @KAAC,  I was using the Device eyedropper, and all the info i wanted to eyedrop (ie. the sockets) moved across nicely; the only problem was that the make and model also moved across, so it wasn't useful for applying the same sockets to different products...

 

- and good to know there may not be a way to create sockets from a script so I don't bark up that tree.  I'll see what I can get going from the file you've attached and post back with the outcome.

 

Much appreciated!