MeriCummins

It seems that the back-up battery went dead on the PLC. I tried to U/L an original copy of the project in hopes that operand settings/values would be included. It appears that is not the case. In addition, I also had exported the existing operand file from this project however, received an error when attempting to write them to the PLC using the Remote utility. It did populate the remote utility as can be seen however generated the error. See screenshots below It appears as though it may be writing the operand descriptions. I did save BOTH separately for the operand DESCRIPTIONS as well as the operands themselves back when I exported them for future reference. It is rather unclear as to saving a project file includes the operands as well as the data within. Additionally, by writing the operands to the PLC-does this embed them within the vlp file? It appears though they are dealt with completely independently afa storing within a project file. The battery backup is what seems to store these values during power down soley in RAM; which I find is very strange-if true.

Additional info. ...further investigation reveals that the Delta Servo drive controller is set to Master in the PLC logic. Additionally there are various subroutines which are labeled such things as PID gains, Alarm limits, segments etc. These look to be just discrete items which are strictly a name. Though a single string is exists which includes the four channels for the delta controller-there does not seem to be any data tables either where these values might otherwise reside. Also, I do not see the operands values that are missing as populated with load on start-up option checked. These are leading me towards thinking the PLC is calling sub routines from the delta controller and potentially is where these default values reside stored in registers...Since they also are not stored in the operand file which was U/L from the PLC a year ago...Just theorizing...??

I have a condtion where the Visilogic program appears intact with various MI values still intact however; there are other settings (ie Control loop gain settings, alarm limits) which have been “saved” and ALWAYS reloaded as defaults settings upon re-boot. Just recently these user variable values have been reset to 0. Additionally, we no longer are reading some sensor signals on the Visilogic HMI screen which are being supplied by an external PID controller via networking (Delta RMC 150 motion controller). Separate channels Emerson / Control techniques Control loop gains which have now been “lost” or cleared are not channels which the Motion controller is even being used for-so things like alarms for other channels also having been reset or cleared seems to indicate that it isn’t just information associated or used by the Delta controller. The delta servo controller is being communicated with through LAN network switch to the Visilogic 1040 HIM/PLC is 7.0.1 (vlp file last saved date 2/20/2013) Current Vision PLC config: O/S: 3.6 (03) Boot: 2.2 (07) BinLib: 0-3.10 (02) Factory Boot: 1.3 (06) These “other” cleared PID gain control loop setting are used for additional (multiple) separate Emerson/Control Techniques Freq. drive units and are being communicated with the Unilogic PLC via canbus.) I have a copy of the original VLP and also was able to export the operands directly from the PLC a year ago however, upon opening this prior saved operand file-it looks like there are no actual variables (ie numeric settings) stored associated to the operands. Shouldn’t the operand file exported using the Remote utility contain these user input (default) setting values that can be re-loaded. It appears I can try to use the visilogic Remote utility to check the communications with the Delta motion controller real-time to determine if the reason I am not longer seeing these certain signals is due to a communication problem. It looks like the comm settings in the PLC for the motion controller are intact but I do not know what they were originally (if they have been changed) and whether they have been reset as well potentially. Thanks for any assistance! It appears as though there is communication happening via between the PLC and the Motion controller via network indicator lights but just a cyclic watchdog interval blink-not fast as if data is being tx/rx’d

MI (Memory Integer) is the full scale for the RPM Display scaling (MI812) for an AC drive. I just discovered that I can access various operands through the front panel of the 1040A and apparently make a temporary edit. Currently, the drive FS parameter is (other MI's) 1775 in other operands (command). I have verified the exact error which appears due to this discrepancy (% diff between 1775 and 1760). So, can I use the front panel to temporarily edit this Mi value to see if it makes the correction I am seeking? THen if so, make the change to the project and download this edit.

Tried to include the quote above... to upload (PLC to PC) current operands -when I try to perform the function I get an error. The dialog box of upload utility comes up defaulted to a comma as separating character but says that "green" backfilled separator values are "recommended". When I try to upload them with the default selected comma type (.csv extension) separator character; I get an error that there is a type mismatch and it doesn't allow me. Appears as though the utility is auto. defaulting to try to save in excel format. I was able to upload operands after selecting the "H" character (green back filled value) as the separating character however, it is defaulting to saving in .xls format. The operands may not be affected-but I want to save the current ones before download the new project regardless. Secondly, my edited project will have a new value for a variable operand (MI) full scale-is THIS an operand? In which case will downloading the originals (if necessary) overwrite the variable within the project that I just edited?? I am presuming the operand file will need to be in .csv format to download if, in fact I need to-is this true?

Ok, what am I missing now 🤣 I un-installed 9.8.5 and was going to dl 9.4.0 What is it that I ought to do "first"?? Thanks!

Thanks -that's awesome Flex, I do not have online immediately available currently but Unitronics has been responsive so they shouldbe able to supply, but if I have an issue I will great of you to offer and I will get back to you if needed. Thanks SO much!! Best regards, Larry

Thanks for the details Flex, couple of things.. So, I can request a copy of 9.4 or find it on the website however, according to tech support the associated Db also needs to be same correct? If I go to the site to download then I don't think I have a choice or is this a non-issue with version 9.4? Thanks!

So, thanks again to all who suggested (what might be obvious to some more experienced!) best practices to employ. 1) I was able to verify signature log file to ensure my copy of project IS what was last uploaded to PLC so though I don't have the pw to ul/dl from the HMI directly to SD; I was able to at minimum flash the PLC (appeared as though it may have not been-but then it confirmed). 2) I uploaded the operands from the PLC to a PC for backup of current values 3) Received a copy of 7.01 from Unilogic tech support but it incorporates a database of 25 and my project was originally written with version 7.01 with database 146. If I understand correctly, I need to have the exact same database to be able to seamlessly edit then re-download w/o having to upgrade the firmware. I was also advised that I might find version swapper a little sketchy, I have never used it so I am not entirely sure how and what it's primary designated function / primary useage applications are. Any insight? My hope would be to use it to be able make a minor scalar value edit for a single channel then save project in the 7.01 version format, burn it and download it to the PLC without upgrading the firmware if possible. Would any changes REQUIRE me to save it to a newer version regardless? Thanks again!

Awesome Dan, THX!!😎 Looks like it is the same name and date on the PLC last loaded with a minor spelling difference so I have confidence my copy and the current running/loaded are the same. I will probably download what is currently on the PLC regardless just to be safe. Thanks to Flex 727, Ausman and Dan for you quick, knowledgeable and excellent assistance! Cheers all!!

Thanks SO much-all!!, that covers all of what I need I think! Yes, I have a copy that was saved which is what I attached, so that supposedly is the same as the one currently loaded in the PLC and running -no issues. WHen I mentioned "old" I was referring to this copy but opened by the 9,8,95 version of visilogic (ie same as copy version just fwd compatibly opened by newer visilogic). Original was referring to the code that is currently on PLC and running-so yes I think you understood correctly Ausman!!

I have complete test rig using Unitronics HW / Visilogic PLC controls with a project created 10 years ago and need to make a calibration / scaling change. There is no access to the original author or otherwise any support. 1) Tried to upload current project from PLC and get the error msg: option "Burn Upload Project" was not selected when the project was downloaded or -due to incomplete data in the PLC. When I open the old project message that it is older code but will be opened anyway with newer vers. (code 155)the creation version for HIM/PLC is 7.0.1 last saved date 20/02/13 I do have a VLP of the original PLC code from the machine mfr. that was created in 2011 (attached). There are other addl. concerns however, not really well versed enough to know how critical these may or may not be. Suggestions as to backing up what is actually currently in the PLC to ensure that it is the same as the (supposed) final copy that was provided by the machine mfr. Current Vision PLC config: O/S: 3.6 (03) Boot: 2.2 (07) BinLib: 0-3.10 (02) Factory Boot: 1.3 (06) There is a note at bottom which mentions Known issues: Version Incompatibility-certain versions have changes that may impact on the running of an existing application if you update the OS in the PLC. I merely want to make a very MINOR edit to a singular parameter scaling value then upload the edited version back to the PLC. I am looking to perform WITHOUT making any or updates to OS. 2) Will my recently downloaded version of Visilogic (9.8.95 bld 0) open the old project, allow me to edit, recompile and download it in to the PLC as-is without issue? It appears as though this should be no problem once I register. 3) Registration says is required to up/down load use remote access etc. Do I need to be connected to the PLC when registering or is the registration strictly to the PC? 4) Since it appears as though the option to "burn" project was not selected when created-what is the reason one would not want to "burn" is burning just flashing a PROM on the PLC with the PLC program to be able to extract etc straight from the PLC via SD or otherwise? I would think that I will WANT to select the option to burn when I upload the revised PLC program. 5) Are there any common pitfalls to avoid bricking the PLC? I have seen a couple forum messages and that is my biggest fear in trying to remedy a minor issue and losing complete function on this machine and not having any support. I am using Windows 7 Enterprise 64 bit SP 1 PC Sorry for the length and detail just want to throw out all the questions swirling around rn in my head-in one post. Thanks much for any assistance. Excuse my ignorance if some of these are obvious to the more experienced. Regards, Larry Meritor Gen4 Final 06-11-13 delta.vlp