Search the Community

Showing results for tags 'query timeout exceeded'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 4 results

  1. Consule timeout connection servo driver

    Hello everyone, Can you help me to solve of my problem? I have one type of servo driver Matsutame ALX series. Driver is using controller of MITSUBISHI. I need to change data point using my console, but when i try to connect to the driver, console always display message "Connection Timeout" . Maybe you have the same problem of me, please advise sir. Thank you.
  2. I have been working on a PLC project that requires sending ASCII commands/queries to an external pressure transducer using the Micro 850 PLC (2080-SERIALISOL module) via serial port communication (ASCII protocol) and in response the PLC would read pressure readings from the transducer. I was able to write a ladder logic program that reads ASCII code from the transducer and converts it into string and inversely converts string output from the computer to ASCII and sends it to the transducer. However, I am uncertain as to how I should send the command string from my computer so that the external transducer receives it, recognizes it after the <cr><lf> is encountered and sends a pressure reading. Any suggestions as to how I can type in commands from my computer and receive responses from the transducer?
  3. FactoryTalk SE - VB Script

    Hey guys,   I am looking to query a database through FactoryTalk SE.  I will be scanning packages, and using that bar code to find a lane assignment from the database.     My question has to do with where the VB script will reside in the FactoryTalke SE program.  I want this script to run at all times.  I see that each screen has a "VBA Code" but I am assuming that these will only run when the screen is visible.   Where does this have to be stored in order to run all the time?   Thanks In Advance!
  4. I have an application in the Visu+ Scada System, from Phoenix Contact, which makes a query in the SQL Server 2014 database. While the database was empty, queries were made perfectly, after 4 months the database grew up absurdly and then stopped running the query, returning the following error: Query timeout exceeded. I have a general table with 210 variables being written every 20 seconds. The query is made by updating the parameters in another single row table, it generates a trigger that copies the requested query to a third table and it is plotted on a chart in the supervisory system. The error occurs when Visu+ sends the parameters to be updated in the second table, returning "Query timeout exceeded.". However, when I update directly through SQL Server, it updates, generates the trigger and performs the requested query. Could someone help me solve this timeout problem, please? Thank you very much in advance!!