Search waiting | Matsusada Precision

Searching...

FAQs

Application software does not work properly.

Category
Product Support FAQ

If you are experiencing issues with the PSS2en or CD-BC software, please refer to the following troubleshooting examples.
For more detailed information, please consult the product's instruction manual.

No communication port is displayed.
With a USB interface, you need to install the USB driver.
With the "-LMi" communication option, you need to install the VISA library.
The software cannot find the power supply during a port scan.
Possible Cause
  • The power supply unit is not turned on.
  • An incorrect COM port is selected in the software.
The communication test fails or does not complete successfully.
Possible Causes:
  • The main switch of the power supply unit is turned off.
  • The COM port number is incorrect.
  • The UNIT number of the power supply unit is incorrect.
  • For the -LMi option, ensure the command type is set to 'MTP' and the header setting is 'With Header'.
The sequence programming does not execute as intended.
Possible Cause
  • The "Use" column of the sequence is OFF.
  • Operation time setting is incorrect.
  • Protection value is not set correctly.
  • There is a mismatch between the connected load and the power supply's output settings.
No program execution records (logs) are saved.
The "Record" field in the sequence programming settings is not checked.
Before contacting us, please also check the following:
  • Does the issue persist when using a different communication port?
  • Does the same issue occur on a different computer?

Please have the following information ready before contacting us via the "Product Inquiry" page.
This information is crucial for us to assist you effectively.

  • Software name and Version
  • Power supply unit to be controlled (model/series)
  • Connection details (e.g., communication port, cable, adapter used)
  • Computer manufacturer, Model name, and Operating system
  • Detailed description of the issue
  • Frequency of the issue (e.g., always, intermittent, only once)
  • Relevant files from when the issue occurred (e.g., condition files, result files, communication logs)

Related FAQs: