This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Allegro 17.4 always reports new files as created in 17.2

Jason T over 1 year ago

Hello. I am using Cadence 17.4 tools. When I open a package symbol (.dra) or board file (.brd) in Allegro that was created in an older version of the tool I get a message like this one (as expected):

"The design created using release 17.2 will be updated for compatibility with the current software..."

If I create a symbol or board file from scratch in the 17.4 tool then open it later, I get the same message. (always referring to version 17.2 which is the previous version I was using here).

So far this has not caused me any problems, but I would like to understand why it is doing this in case I have something setup incorrectly.

I only have version 17.4 installed. I am not exporting to a downrev version when I save (i.e. not using File->Export->Downrev design…) and in User Preferences->Drawing I don’t have anything selected for database_compatibility_mode. What else might I check?

FYI here is the tool version information that I see after selecting Help->About Symbol:

OrCAD PCB Designer Standard 17.4-2019 S012 [10/26/2020] Windows SPB 64-bit Edition

Thanks -Jason

RFinley over 1 year ago

In User Preferences, search for the variable "databse_compatibility_mode". I think its in "unsupported" folder.

It looks like you have it set to only export 17.2 from 17.4.
Cancel
Up 0 Down

Cancel
Jason T over 1 year ago in reply to RFinley

Thanks for the reply. If I go to Setup->User Preferences and select the Drawing folder there is a database_compatibility_mode field. It is blank, but if I click on the pull-down arrow it shows a 17.2 option. Since the field is normally blank I assume that I am not selecting that option. If I select the List All button there is no entry for database_compatibility_mode. I don't see anything that looks relevant under the Unsupported folder.
Cancel
Up 0 Down

Cancel
RFinley over 1 year ago in reply to Jason T

The first time I tried it, I cleared the 17.2 option but didn't click "apply"

Worst case, check your pcbenv/env file. Look for a line in the bottom section that says:

"set database_compatibility_mode = 17.2"

remove it. Save your env file. Restart Allegro.

Allegro will startup with a new board and warn you that it will be saved in 17.2 if this variable is still set.
Cancel
Up 0 Down

Cancel
sfrederick over 1 year ago

See the following article on Cadence Online Support:

A .dra file saved using 17.4 release gives a message that it is created using 17.2 release when opened in 17.4
Cancel
Up +1 Down

Cancel
Jason T over 1 year ago in reply to RFinley

Hmm, I see no such setting in the env file (C:\Cadence\SPB_17.4\share\pcb\text\env).
Cancel
Up 0 Down

Cancel

Stats

Allegro 17.4 always reports new files as created in 17.2

Community Guidelines