Jump to content

Robin P

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Robin P

  • Rank
    Advanced Member

Recent Profile Visitors

2,922 profile views
  1. Instead of writing your results to a CSV file, have you thought of writing them to a networked database (e.g. MySQL or SQL Server). The target database table would have the same column structure as your data table, and can be made available to any networked user. Unilogic has inbuilt SQL handling, which replaces the CSV file writing process, and for end users Excel has add-ons for connecting to such databases. We do this successfully in a laboratory Unistream application.
  2. On upgrading my Unilogic program with compiler version 1.29.111, it now reports this error: 'The TCP Remote slave limit of 64 operations has be (sic) reached. (136)' The program previously compiled successfully with compiler version 1.29.26 and .34. I have 11 ModBus Remote Slaves on separate IP addresses, with 10 of which I request a single 64-register transfer, and the eleventh two 32-bit register transfers. If I remove all the Slaves and associated code, then the program compiles. If I then reinstate them it now compiles successfully! I have several versions of my program in d
  3. You could create a data table with a row for each sensor, and columns for current and stored values, and sensitivity criteria. You then write a loop to process the table at some suitable frequency, reading into the table the current value from the sensor and performing the same comparison calculation each time, but with custom values for each sensor. You can implement loops in ladder code using the Jump to Region function.
  4. It is my experience that if you make any change to the struct from which you generate the CSV file append, you must delete all 3 files of that name on the SD before the PLC can write again to it.
  5. I have successfully used Export Structs to get an XLS spreadsheet, shuffled its rows (fields) using Excel's Cut and Insert Cut Cells, then used Import Structs to overwrite the original struct. I recommend saving a copy of the file beforehand, and not attempting to add, remove or rename any fields from Excel. I did indulge in some renaming which imported OK, but got a Delegate Error on recompiling - which spells death to the ULPR I think. Renaming struct fields seems fine if done within Unilogic.
  6. Hello Ofir. I have a client system using a PID loop for temperature control. To investigate a separate problem (as in D Green's recent FTP post) I would like to download and run a new, different, temporary project; and subsequently restore the original. I believe however this will destroy the original retained PID AT settings, which I would like to restore, possibly from a file, to avoid having to run the (lengthy) PID Autotune again. Is it possible save the PID AT params to a file on the SD card, as it is with any user-defined structure using a data table? Thanks Robin
  7. I have a similar problem in loading UniLogic 1.18.41 on my laptop. Was there a successful resolution to Ruey Shin's problem? Regards - Robin Proctor
  8. I need some of my timers to resume from their last Current value following a system reset (which can happen following a software upgrade). If I just retain them they simply re-initialise. I think I can achieve this as follows: 1) Set the timer T to Retained. This just affects the Preset value. 2) In the main scan regularly store a copy of T.Current into a retained tag TC. 3) On the Ladder Initial Cycle (which happens following reset): 3.1) Store T.Preset into a temporary location TP 3.2) Store TC into T.Preset 3.3) Reset timer T. It's
  • Create New...