Stats

More Content

OrCAD X Capture 25.1 – PDF Export in Variant Mode Produces Extra Pages and Error Message

Kevcsc

Hello everyone,

I’m currently using OrCAD X Capture 25.1, and I’m running into an issue when exporting a variant schematic to PDF. Every time I generate a PDF from a variant view, the output includes two extra pages, and one of those pages contains an error message that looks like below. 

The actual error is captured as shown: 
" ERROR: syntaxerror

OFFENDING COMMAND: ----nostringval----

STACK:

/JS

/JavaScript

/Subtype

-mark-

/Action

[0 0 0 ]

/Border

[0 1 0 ]

/Color

[748 61 604 1196 ]

/Rect

1/

SrcPg

-mark"

 

This only happens in variant as exporting the main schematic works normally with no extra pages or errors.

Has anyone seen this behavior before or know what might be causing it?

Thanks in advance!

Parents
  • AC202604093433
    0

    "syntaxerror" basically means that the file has a misplaced bracket.Due to very liberal approach to identifiers, most common error is "undefined" rather than "syntaxerror"

    I can check what exactly went wrong but I need a sample file.

  • NG202603188945
    0 in reply to AC202604093433

      What do you mean by sample file? If you try to export pdf with variant view enabled, it can be reproduced for me. And it is for any schematic. 

  • AC202604093433
    0 in reply to NG202603188945

    I know Ghostscript, PostScript and PDF but I don't have your software. Try to capture the PostScript file that your software is converting to PDF using Ghostscript. The software may have an option to export PostScript instead of PDF. If the exported PostScript has the same problem when it is converted to PDF, post it somewhere. If not, write a script that pretends to be Ghostscript but captures input files instead.

  • NG202603188945
    0 in reply to AC202604093433

    How do I get the .ps file? It just deletes ... Or I am not getting what you want me to do. For me it looks like orcad issue, as lower version of build does not have issue. 

  • AC202604093433
    0 in reply to NG202603188945

    Yes, it is orcad issue and we are trying to diagnose it. Orcad generates incorrect PostScript file that it feeds to Ghostscript. If we figure out what is wrong with the file, we can take corrective actions: tweak Ghostscript or file a well-founded bug report against Orcad.

    Orcad probably has an option to export *.ps files. Save this file and give it to me. Either post it somewhere on the net or email it to alex at coscript dot biz

    If Orcad cannot export *.ps, we will try to capture it in other ways.

Reply
  • AC202604093433
    0 in reply to NG202603188945

    Yes, it is orcad issue and we are trying to diagnose it. Orcad generates incorrect PostScript file that it feeds to Ghostscript. If we figure out what is wrong with the file, we can take corrective actions: tweak Ghostscript or file a well-founded bug report against Orcad.

    Orcad probably has an option to export *.ps files. Save this file and give it to me. Either post it somewhere on the net or email it to alex at coscript dot biz

    If Orcad cannot export *.ps, we will try to capture it in other ways.

Children
  • NG202603188945
    0 in reply to AC202604093433

    Can you give me your email? Or how do I share. I can share the .ps file. 

  • AC202604093433
    0 in reply to NG202603188945

    My email in the slightly obfuscated form is in my previous message.

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.