Jump to content

AlexUT

Moderators
  • Posts

    837
  • Joined

  • Last visited

  • Days Won

    40

Posts posted by AlexUT

  1. 1. Open Device Manager and write/out/remember what is a COM port number assigned to connected V570 PLC.

    2. Disconnect USB-A/USB-B cable from PLC.

    3. Close VisiLogic.

    4. In Device Manager go to "Menu->View" and select "Show hidden devices".

    5. Right-click on installed driver and select "Uninstall device". In my case it is COM 5.

    image.png

    6. After finishing uninstall, run VisiLogic as Administrator.

    7. Open Communication Settings and change to last tab with USV icon.

    8. Follow steps.

    9. Connect USB-A/USB-B cable from PLC to PC.

    Windows should install driver.

    10. Check in Device Manager what COM port number Windows assigned to PLC.

    *Port number should be between 1 and 16.

    11. Use this COM port number for PC-PLC communication.

    12. Communication settings should be as follows:

    image.png

     

     

  2. What dificulty do you have>

    Be more specific, then answer will be fastest.

    1. What Windows Version do you use?

    2.What is a PC/Laptop model?

    3. Is there SSD installed at PC/Laptop?

    4. Did you unblock UniLogic installation file before running it?

    5. Does your PC account has an adminictrative rights?

    6. What happen when you run UniLogic installation?

    7. Other details.

     

     

  3. It is useless to use very high frequency for PWM.

    As you process is slow - it is recommended to evaluate UniLogic example \PWM\UniStream_070_PWM.ulpr

    *You have to download UniLogic Examples.

    In your case 0.1% for PWM should be equivalent to 2-3 scan times.

    Instead of 0.1% precision you can use 0.5%-1.0% precision.

    To do this, you have to  linearize 0-100 range to 0-1000 range.

     

  4. 1. If not stated PWM or other special output type - this parameter refers normal output.

    2. Switching time is exactly as stated in Data Sheet:

    image.png

    This means that after receiving ON or OFF signal from PLC, required state will be set after maximum 80 us.

    2. It is useless refering to frequensy, as output signal should do something.

    As output is managed by PLC, ON/OFF time will be dependent of scan time and other parameters.

    Scan time will wary from ~1 ms to 10s ms, dependent of project complexity.

    3. It is better to start by analysing project requirements.

    Then check if modules fit project requirements.

    4. Some modules has set of scenarios, involwing Inputs, Outputa, Timers, and some simple logic.

    5. US series PLCs (T42) has special Interrupt routine with fixed interrupt time.

     

    Hope this information helps to clarify I/O timing.

     

  5. There are number of separate entities:

    1. Jazz - has no support for SD card.

    But has special Memory Module for cloning.

    2. M90.Have no SD suport and no Clone option.

    3. SAMBA does not supporting SD Card and cannot be cloned.

    4. Vision PLCs can be cloned by use of SD card, but SD password should be set in ladder (to protect intellectual rights) and you should know this password (as Flex727 recommended).

     

    All PLCs can store in flash memory Ladder code of projects, but programmer may disable this option.

     

  6. Hi.

    There is a document at web site - "Version Changes & Bug Reports":

    https://downloads.unitronicsplc.com/Sites/plc/Unilogic/UniLogic_1.33.236_November_2022.pdf


    Following is printout from my Desktop computer:
    C:\WINDOWS\system32>sqllocaldb versions
    Microsoft SQL Server 2012 (11.0.7507.2)
    Microsoft SQL Server 2019 (15.0.2000.5)

    C:\WINDOWS\system32>sqllocaldb info
    MSSQLLocalDB
    UNILOGIC
    v11.0

    As you can see, I have installed 2 versions of MS SQL Server - 2012 and 2019. as I use multiple versions of UniLogic.
    But UNILOGIC database always is in version v11.0 for compatibility.


    Microsoft SQL Server Local DB 2012 used for all UniLogic versions before 1.33.xxx version.

    Starting  1.33.xxx version UniLogic installation install Microsoft SQL Server 2019 (15.0.2000.5)

  7. We prove that this happens at our computers as well.

    R&D will correct this.

    Until correction will be applied - please use RickL work-around, and do not close this window.

    For us is VERY important to simulate problem.

    Ther we can introduce problem to R&D and require correction.

    Fortunately, RickL recovered his operation sequence before crash happens.

    This halps us to make software more frendly.

    So, if you can simulate sequence of operations tor other crashes or problems - explain us how to simulate and we will require from R&D to fix problem.

    B.R.

     

  8. Probably I will surprize you by answer - 32-bit PLCs are not a right instrument to "to do about 500 to 1000 cycles to calculate the model" when yse 32-bit Float Point representation.

    Precision will be lost.

    You need a DSP for this.

    Now you have to decide how to continue.

    PLC can be used to manage machine, but you have to use other device for "to do about 500 to 1000 cycles to calculate the model".

    May be other Forum members have some ideas.

     

  9. Regarding Unitronics Software Activation - after Microsoft updates at  Registration Server Security Requirements changed.

    VisiLogic 9.8.95 and up already updated to fit these changes.

    Other VisiLogic versions require offline registration.

    You can check if Online refistration is possible by next "work-around":

    - In VisiLogic open "Help->Check for Update->Operation System".

    image.png

    If this test does not return error - online registration is possible.

    Best regards,

  10. When write to Unitronics Support, please add following information:

    1. Is your PC new from the store?

    2. What is a Windows OS version?

    3. Did you upgraded Windows OS last time?

    4. Is this a new UniLogic installation or existing one?

    5. Does this problem happens after Windows update?

    Best regards,

×
×
  • Create New...