Jump to content

Sremac

Members
  • Content Count

    19
  • Joined

  • Last visited

Everything posted by Sremac

  1. Small update: I used Version Swapper a lot of times with various Visilogic versions without any problem since!
  2. Dear Ausman, thanks a lot, I've tried your method with partial success. Also it's too complicated, I mean too error prone for an old guy like me... One new moment concerning W10 and Version Swapper: After fresh W10 installation I've had the same issue as described above, Run-time error 339, amiTapi .ocx components not registered/missing. I tried to locate the file amiTapi.ocx on my computer without success. But on the other laptop I've found it, made a copy to the USB flash and transfered it to c:\windows\system32 folder. Note 32-bit W10 version, otherwise on a 64-bit version
  3. So, what now? Please don't tell me to roll back to Win7 or, even worse, to use virtual machine...
  4. Joe, I suppose you're right about Microft world and stuff... Unfortunately, even if I explicitly run Swapper as administrator and upon registration of say VisiLogic V4.7.3. I explicitly run VisiLogic.exe in .../VisiLogic_V4.7.3./Main/ folder "as administrator" it still says: "Run-time error 339" - snapshot attached.
  5. No matter I run the application under administrator's account on my laptops with Windows 10 (both 32 and 64-bit versions), Version swapper would not function normally unless I specify "Run as Administrator" option as I start the program. Yes, it is possible to specify this option on a shortcut that starts Version Swapper, so it always runs "as administrator". But, still there is a big problem: even than some older versions would not run after being registered with Version Swapper, there are various error messages that says that some componenets could not be registered, that are missing or
  6. Very odd situation, for the first time in a decade using VisiLogic: Yesterday, after I finished my current project I burned "Upload Project" to the V570 and saved the file. My normal procedure is to make file backup, so I instantly used "Save as" within the same folder with _bak added to the project name. After that I performed verification with the OPLC, which returned all the check marks as usual. Furthermore, my normal routine includes synronising "Documents" folder with the one on a USB memory stick, which I also performed imediatelly. This morning i needed to change some small detail in
  7. Dear Eyal, thank you very much for that, a am going to try it ASAP. I always wait for Swapper version of my current VisiLogic before I switch to newest version...
  8. Can somebody explain how to register previous version with the swapper, please? BTW, when can we expect V9.5.0 Swapper?
  9. It seems that there is a mystery about exact functioning of a "secret" SB90 system bit... Reading this topic I am seriously concerned about a lot applications I've made without thinking of such a problem. I suppose that I just expected that the system itself was to recognize that something is missing from Harware Configuration and safely stop everything in such a situation. Now I am not sure how my system would behave... I strongly support the request of providing meaningfull way to control system behaviour in the situations when there is a problem with any expansions, Snap-in, wired, wire
  10. Dear Nacho, thanks a lot for the remark you've made, somehow I missed it while reading the Guide. On the other hand, this means that the unit actually produces 0-20mA in both modes, so one has to use linearization network (or some similar calculation method) to scale 0-OUTmax in 819-4095 units instead of 0-4095. Logical question is then why there is a switch in a Hardware Configuration menu, i.e. what really changes when I change it? It seems - nothing. Also, I don't expect output current to be dependent of the inverter input impedance as long as it is within specified range.
  11. It is the second time I have the same problem with AO6X analog output modules - although in the Hardware Configuration I choose 4-20mA option for the current outputs, they produce 0-20mA anyway! Norlmally I use it with an inverters set to 4-20mA frequncy reference. OK, I switched inverters to 0-20mA, but there's another issue - 20mA does not correspond with the value of 4095 in an assigned MI, but with 4080! Very odd behaviour, not a real problem to me becuse I made it work anyway, but I had to report it here. My best regards to all!
  12. Dear Ofir, thanks a lot for zour reply. I am sorry for my late response, but as soon as I posted I myself found out the workaround. But, there is an issue about it: since calculation is provided only once per OPLC cycle and there is no possibility to use interrupt subroutine, is this really a HSC? The only thing that you get by using it is that you don't miss a pulse shorter than a OPLC cycle time. Anyway, my application could "swallow" it, so now everything work as expected. Also, I suggest that there should be a short notice about that limitation in the hardware manual, so nobody gets as c
  13. Well, i consider myself experienced user on Vision PLCs. Now I am facing a problem that is blowing my mind! i use maximum loaded V570 configuration (Snap-in, 4 x DI16, 2 x TO16 and 2 x AO6X with EX-A2X adapter). I already use incremental encoder on my Snap-in module (A, B and Z pulse) emulating absolute encoder. But i need two more counts in order to determine some sync points on the other moving parts on my cartoning machine. So I connected just phase A of an incremental encoder to expansion DI16 module and in HW configuration make it work like a HSC. It counts up all right. But it doesn't le
  14. Well, i consider myself experienced user on Vision PLCs. Now I am facing a problem that is blowing my mind! i use maximum loaded V570 configuration (Snap-in, 4 x DI16, 2 x TO16 and 2 x AO6X with EX-A2X adapter). I already use incremental encoder on my Snap-in module (A, B and Z pulse) emulating absolute encoder. But i need two more counts in order to determine some sync points on the other moving parts on my cartoning machine. So I connected just phase A of an incremental encoder to expansion DI16 module and in HW configuration make it work like a HSC. It counts up all right. But it doesn't le
  15. Hay everybody! I am still waiting for the confirmation that the problem is solved. Tired of workarounds...
  16. For some time I get complaints from my customers that my PID controlled heater loops overshoot a lot at the beginning of the operation, and then functions OK. Talking about V570. PID is connected to a physical output driving SSR thru a PWM FB. At the begining of the heating cycle PID Control Value is 100% and PWM output bit is permanently ON, of course. But later on, as the temperature rises, CV naturally starts to fall (99%, 98%, ..., 57%, ...) but PWM output bit is still permanently holding ON state, without any blinking, so my SSR is fully open, providing 100% average power to the hater,
  17. I understand and appreciate Unitronics concept as constantly developing and upgrading. So every user is strongly advised to update VisiLogic regularly (as well as the OS), and to use Version Swapper for being able to fully interface with the applications created with some of the previous VisiLogic versions. Understood in this way, it seems quite natural always naming the latest version "current". Once you get used to it, it makes no problem at all.
×
×
  • Create New...