Stats

  • State Not Answered
  • Replies 3
  • Subscribers 41
  • Views 3211
  • Members are here 0
More Content

Workspace and livebom possible problems with a corporate firewall

gvellet

Hi,

I am testing the workspace and LiveBOM feature in Orcad capture X. I am having problems. Workspace cannot update the cloud file. And Livebom freeze often and cannot get more than a few part data. I suspect that my corporate firewall is blocking some of the communication link with those tools. Is there a list a URL /port number that need to be whitelisted in a corporate firewall to support properly Orcad X new features?

Thank you,

  • Jeet
    0

    Which hotfix of 23.1 version you are using?
    I tried the same on 23.1.S004 and I am able refresh all the files by selecting Refresh icon in File Manager. Whenever I invoke Live BOM it shows me the updated schematic design data.

    Is this is a design specific issue or this is reproducible with all the designs while publishing to shared Workspace or Viewing Live BOM when connected with a corporate firewall?

  • gvellet
    0 in reply to Jeet

    Hi,

    I was using 23.1S003. I have just updated to 23.1S004 and the problem has changed. The workspace file update is now working. But with Livebom, it is missing more properties than before, even the reference designator field is blank. I checked in Orcad Extended Preferences that the live bom properties are correctly mapped to my Schematic properties.

    To use Orcad, I have to connect to my corporate network to access the license server; therefore I cannot test outside my corporate network. The issue is seen with all design; small or big. 

    Since the feature is working fine on your side, I suspect that the livebom problem is caused by the firewall of my corporate network. My I.T. department can re-configure the firewall if we know the URL & port number that need to be opened. 

  • gvellet
    0 in reply to Jeet

    The problems are fixed and it was not a firewall issue.

    For the problem#1 with workspace not uploading. I think it was triggered when I opened capture using an Orcad X standard license instead of  the Orcad X Pro license. It jammed something in capture that never recover even when using again an Orcad X Pro license. To unjam it, Ii workspace config I switched library CIS from local to cloud. Save and exit. Then went back in workspace config and switched back to local library. After that, the workspace background upload started to work again. My guess is since my workspace was created using a Pro license, trying to access the same workspace with a standard license is messing up thing. Quite annoying and when it bugs there is no messages to help understand that there is a problem.

    For the problem#2, it was triggered  after updating from 23.1S003 to 23.1S004. The LiveBOM config file "C:\SPB_Data\cdssetup\workspace\config\orLiveBOMConfig.json" got corrupted somehow.  Strangely when browsing the liveBOM config everything look fine. But after re-entering every field mapping manually, the livebom rows were showing useful information again ( manufacturer, manufacturer number, reference designation, description, etc.

    I have seen too many issues with the new features in Orcad X capture and Orcad Presto. I believe that Orcad X is not mature enough, I will waste too much time on unexpected bugs poping up. I will wait for a half a dozen hotfixes before trying it again.

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.