Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ean

  • Rank

Personal Information

  • Location
    United States
  1. When using the Device Builder tool, editing the device depth prevents creating a physical device. If I use the rack unit drop down it changes the width and height into feet and inches, but not the depth. Oddly, the width is slightly larger than 19 inches. Editing the depth field prevents one from creating a physical device. If one creates the device without editing the depth field it gets changed into feet and inches correctly. I have yet to try this whilst creating a new device from scratch. Ean
  2. I have noticed an oddness with the display of devices being different when in a rack object and when outside of it. When the device is within, or partially within a 2D rack, it shows make/model and is sized correctly. When a device is outside of the rack it loses its dimension and data. I will often put devices in the same room as the rack while not actually in a rack. This helps with getting all devices in the correct room for reports. (The rack elevation viewport is typically then cropped to show only the rack.) During the design phase it nice to seed how many rack units a device is before dragging it into a rack and to see the make model without having to look at the Object Info Palette. I imagine this has something to do with the 2D/3D representations of devices. I tried dragging a device into a 3D rack but nothing changed from the "outside the rack" representation of the device, or line up with a rack space. Clearly, I have a lot to learn about the 3D rack tool. Also, the rack unit value specified in the device builder does not appear in the OIP for a device in the Rack Elevation. Specifying it manually in the Rack Elevation does not change the behavior described above. Ean
  3. Naw have custom fields in OIP and reports, but couldn't show them on devices in the schematic--until I undid one thing. I hope what follows can help someone else, especially since the old documentation is now hard to find and current documentation is scant. I edited the CustomParams.text as shown in a document I found about migrating from 2019 to 2020. I'm not trying to migrate anything yet, just setting up from scratch. You have to delete the leading semicolon to uncomment the line and delete the text from the ChoiceList field if you want a text field. I left the tabs in place in the text to designate the choice list in case a missing field would screw anything up. Then, I updated the field names in the dev_rec. DON'T DO THIS! BAD! Then I added fields to the device report. I don't get why the fields are in sum mode, but I just copied and edited so they point to the correct fields. Then I copied dev_label_generic to make a new label adding new fields to a new label. If there is a way to make my custom dev_label the default I'd love to know it. I'll ultimately end up editing the default if I have to. At this point everything looks fine, but custom fields are not showing up on the device. I remembered that when editing the report fields the custom params name still showed up as user1, user2, etc. So I undid what I had renamed in the dev_rec record format then re-pointed the text labels at the correct fields and voila! The only way I could figure out how to label the fields as above is to actually type it into the custom parameter box in the OIP. This is a _terrible_ idea because it will then end up in the field of the reports! Better to make a legend device somewhere on the drawing. Now I've got to figure out how to customize the device in the 2020 version so that sockets don't interfere with all this data I've decided to add! Back to the forum! Ean
  4. Agreed. Easier to upgrade. Best practice to backup the files anyway. Agreed, it is better and getting more betterer. Okay, I just copied the entire connectCAD_Date directory from /Applications/Vectorworks 2020/Plug-ins/ to ~/Library/Application Support/Vectorworks/2020/Plug-ins. Sorry to be a nudge, it's just really helpful to specify complete file paths.
  5. Haven't got that far yet. Still trying to figure out where to edit custom params if not in the app folder. There used to be a ConnectCAD folder in Application Support -> [year] -> Plugins -> etc.
  6. Meanwhile, if I add the field as described above, will it a appear in the Device Builder interface? I'm going to try it out today, but am trying to avoid floundering overmuch. Thanks.
  7. Conrad et al, Will adding a custom device field as described above also place it on the Device Builder tool interface? One could do this in 2019 (and earlier) but I can't get it to work in 2020. It's really nice to put an IP address or whatever while building the device, have it show up on the schematics and in reports. I typically have two IP addresses on many devices (1 LAN, 1 Dante). Some devices create their own subnets too… Given the ubiquity of an IP address, I wonder why this field isn't already built in. Ean
  8. Yah, no, not trivial. Probably requires creating a couple of temporary circuit records to move the fields around in before writing it back. Then the whole GUI issue--is it a menu item or a button in the circuit info panel? On and on it goes. Thanks Conrad.
  9. Hi Conrad, Here is my thinking. If I've got a technician going through the cable list, it is much easier to read if all the ports in a single device are in the same column. If the direction of the drawing of the circuit changes, again I/O to I/O only, then the cable list gets disjointed and harder to read with ports from the same device jumping from source to destination. Sure, in this case there is no actual source or destination with signal going both ways, but it makes the generated paperwork harder to read and more likely to create errors in the shop or the field. At this point, it is easier to identify which cables are drawn "backwards" and redraw them, renumber them and generate the cable list again than to, say, modify the list then re-create the schematic. Being able to "flip" the cable without having to re-draw and renumber it would be an epiphany. Ean
  10. Super. That's great. Couldn't find this. Will search again. Thanks. Yeah, that oughta cover it! Yes, only I/0 to I/O. I offered up this idea a while back because it is easy to (while drafting madly or making later changes) get the direction of the drawing mixed up. This results in the cable reporting to be less pretty as a single device will end up as source or destination depending on this. It's much nicer for technicians to each socket on each device logically listed. Now, other users have noted that the circuit labels on the schematic are also changing position in the SDK version relative to which direction an I/O-I/O circuit is drawn. I offer the idea up again as it would now address multiple issues.
  11. Hi Conrad et al, I'm looking forward to using the new version, but sticking with 2019 for now and still waiting for a lull in the workload… +1 on bringing back the device label pull down in device builder. I rely on using custom device labels. +1 on having a complete list of changes. +1 on custom rack heights. The defaults only occasionally seem to match up with equipment racks from Middle Atlantic. I recently tried to add a new rack height in 2019, but couldn't remember the process so I went to the old connectCAD website to find the tutorial. I was redirected to this forum. Is the 2019 online documentation still available anywhere? Regarding the circuit label position changing with the direction of a cable being drawn, I have previously requested the ability to flip a line after the fact. Of course this only applies to I/O- I/O cables. When drawing the schematic and making mistakes or changes it's really easy to get the direction of the cables out of order. Flipping the direction of circuits like this would also clean up the cable reports. Thanks, Ean


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...