Stats

  • State Not Answered
  • Replies 6
  • Subscribers 8
  • Views 307
  • Members are here 0
More Content

Display project pulse version in SYSCAP title block and in pcb editor.

RJ202412171240

Hi,

I am using Allegro X 24.1; System Capture, PCB Editor and are saving both schematic project and layout in Pulse.

I want to display which pulse commit I am looking at on my schematic title block - I have been doing this in other software that has revision handling and it is very practical both during actual design work and when sharing and discussing projects to know which version are currently shown.

It seems like it should be a simple enough variable to fetch from the system with something like $PulseVersion or similar.

I have done my own workaround by creating my own custom variable called PulseVersion and then run this TCL "script":

modifyCustomVar -name "PULSEVERSION" -type "Project Defined" -value "[dict get [dict get [pulse::getVersionDetails] Attributes] displayRevision]"

It will return current pulse version like "1.0" or "4.2" or "1.33.7" depending on your current commit version.

But its a manual step that in my opinion should be automatically updated when commiting. Has anyone found a better way?

I would love to have a similar solution in pcb editor also, but have not even managed to do a manual workaround in there yet :/

Best Regards

Parents
  • RJ202412171240
    0

    In the best of worlds, I shouldn't have to generate a variable by myself.

    What I really want, is an easy way to fetch and display a variable that already are in the system.

    When I hoover over the project, I can see the pulse version like in the attached image.

    Best would be if I could just fetch that variable somehow and add it to the schematic page.

    Is this such a unusual thing to require from a built in version control system? To me it seems like a very basic function and also a core necessity for the usability of a revisioning system.

    Are any other using cadence pulse, and if so, how are you using version control?

    Edit:
    In PCB editor this numbers can be found when clicking the pulse icon, entering "Allegro pulse status". Like the image below. This show that also this system have the variable somewhere and should therefor be readable somehow, right?

Reply
  • RJ202412171240
    0

    In the best of worlds, I shouldn't have to generate a variable by myself.

    What I really want, is an easy way to fetch and display a variable that already are in the system.

    When I hoover over the project, I can see the pulse version like in the attached image.

    Best would be if I could just fetch that variable somehow and add it to the schematic page.

    Is this such a unusual thing to require from a built in version control system? To me it seems like a very basic function and also a core necessity for the usability of a revisioning system.

    Are any other using cadence pulse, and if so, how are you using version control?

    Edit:
    In PCB editor this numbers can be found when clicking the pulse icon, entering "Allegro pulse status". Like the image below. This show that also this system have the variable somewhere and should therefor be readable somehow, right?

Children
  • CadAP
    0 in reply to RJ202412171240

     

    Please command axlPulseGetDesignStatus to get the design version status.

  • RJ202412171240
    0 in reply to CadAP

    Thanks, that will put me on the right track.

    I guess that I need to learn SKILL and do some script that masks out the design version and put it into a variable/property somehow if I want to be able to document the version of the board in the artwork.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.