Search waiting | Matsusada Precision

Searching...

FAQs

Troubleshooting application software issues

Category
Product Support FAQs

If you experience issues with the PSS2en or CD-BC software, please refer to the troubleshooting steps below.
For detailed information, please consult the product's instruction manual.

No communication port is displayed.
For USB interfaces, ensure the USB driver is installed.
For the "-LMi" communication option, the VISA library must be installed.
The software cannot detect the power supply during a port scan.
Possible Causes:
  • The power supply unit is turned off.
  • An incorrect COM port is selected in the software.
The communication test fails or does not complete successfully.
Possible Causes:
  • The main power switch of the unit is off.
  • The selected COM port number is incorrect.
  • The UNIT number setting on the power supply is incorrect.
  • For the -LMi option, ensure the command type is set to 'MTP' and the header setting is 'With Header'.
The sequence program does not execute as intended.
Possible Causes:
  • The "Use" setting in the sequence list is disabled (OFF).
  • The operation time setting is incorrect.
  • Protection values are not set correctly.
  • There is a mismatch between the connected load and the output settings.
No program execution records (logs) are saved.
Ensure the "Record" checkbox in the sequence programming settings is selected.
Before contacting support, please also verify the following:
  • Does the issue persist when using a different communication port?
  • Does the same issue occur on a different computer?

Please prepare the following information before contacting us via the "Product Inquiry" page.
This information allows us to assist you more effectively.

  • Software name and version
  • Power supply model number
  • Connection details (e.g., communication port, cable type, adapter used)
  • Computer specifications (Manufacturer, Model, and Operating System)
  • Detailed description of the issue
  • Frequency of the issue (e.g., always, intermittent, occurred once)
  • Relevant files (e.g., condition files, result files, communication logs)

Related FAQs: