cajunconfigurator

Hello All, I am using InTouch 10.1.301 and Archestra 3.1.301. I am attempting to use an archestra trend client with intouch historical data. I am not using the wonderware historian, rather the intouch LGH files archived on a network client machine. I also would like to use indirect tags to configure the archestra graphic and have built the custom properties to do this. My goal is to create a trend window using indirect tags, script naming the indirect tags for the pens when the window is called. As of right now, I have a very successful real time trend that refuses to load any historical data. The regular Intouch trend client loads the historical data without issue. TROUBLESHOOTING THUS FAR:I have set up the Historical Sources tab of the trend client to the LGH file share and set the UNC path. I have set up each of the Pens in the trend, and pointed their historical source at the name of the historical source in the historical sources tab. I have verified the historical source of InTouch is the same as the UNC path set up in the trend. I tried calling WW tech support and their recommendation was to use Memory tags vs indirect tags. This was the dumbest thing a tech support has ever recommended, but I went with it anyway. All this made me have to do is script the direct tag values to the mem tag values along with all of the dot fields AND have to create a "while running" script to update the mem tag value every second, because mem tag values are only updated when something triggers the value update. And it did nothing to pull in the historical data. I tried using direct tags and cut out the indirect and mem tags. This did nothing to pull in the historical dataI moved the historical source in both the trend setup and intouch setup to directory local to the Galaxy Repository. I found this article http://logicupdates.blogspot.com/201...endclient.html and I made another archstra symbol with the trend client, and configured it as recommended, no custom properties, pointed the pen directly at the direct intouch tag, and configured the historical source, also pointing the pen history at the source and directly to the intouch tag. ANNNDDDD its a stripped down real time trend with no history. I am getting very frustrated as all documentation and sources indicate this should be possible, WW tech support says it is possible, but I cannot get anything over tier 1 support on this version. Does anyone have any ideas?

Hello All, I have an older Total Control Quick Panel QPI2D100L2P 10.4 inch Monochrome that I am trying to retrieve the program on. The original programmer is unknown and we do not have a copy of the program. The screen has gone out on this panel.I am using quickdesigner on an XP virtual machine. I have the correct programming cable the 8 pin DIN connector HMI-CAB-C49-JWhen I connect to the HMI, The software "sees" that the HMI is connected and says "waiting for the Display to be ready" then times out and tells me "the display is Hung" and another message "Turn display OFF" when I turn it off the software gives me the message "Turn Display ON" then when I turn it on, the software goes to "waiting for the Display device to be ready" and just sit there. Nothing more. I have waited for 20 mins for it to progress and nothing. At first I thought maybe the Panel that I am working on is just bad. However I get the same indications on another, same model, quick panel that IS working just fine. I know this is older stuff. And ProFace Support (who took over making the replacements from TCP) wont support using quick designer on anything other than a Win 2K machine or older. Anyone have experience with these panels?

Is anyone experienced with Siemens 505 / FasTrack workshop 505? I have an old GE quick panel that has gone out and now must be replaced. Cant get the program out of it. No one has a documented copy of the PLC program, and no one has a copy of the Panel program. Have to rebuild the panel program from scratch for a new ProFace, but I need documented PLC program before I can even start that project. I have the FasTrack workshop 505 software and the hardware key. Uploaded the PLC Logic and made an excel csv all of the address comments from the drawings for the inputs and outputs. Luckily the P&ID drawings also lists the "internal memory" addresses the inputs are mapped to. So about a 3rd of the memory bits and words are addressed, and the analog instruments reference the scaled values in the PLC program (the V addressed). Additionally I have documented all of the X and WX and WY and C bits and V word addresses that I can map directly to inputs or outputs, and documented a bunch of the analog scales in the SF section. What I can not seem to figure out is how to cross reference effectively, and how to view the data tables. Does anyone have any advise for this undertaking? I am at the point of pulling my hair out trying to figure out how to effectively cross reference. I have about 900 rungs that have NO user comments because they are all memory bits and words that are filled from operations that I have to sort out. I have done this plenty of times in S7 and Logix 500 and 5000. I am confident in my ability to understand the logic if I can figure out how to view some of these values that I know are setpoints. But since I cant tell what the data table values are and the outputs are going to memory addresses that are not commented, I can know that Compressor Cyl1 Suction Temp is the A that should be > or = to B, but not knowing what that B value is makes it so that the output of C3498 which crosses to a rung with 17 other AND components both NO and NC, I know this is all going to some sort of most likely a permissive, but permissive for WHAT?  If anyone has some tips on setting this thing up to view things more effectively, or how to display the data tables, and not have the ladder view return to network 1 every time I switch views, That would be a huge help. and how do you make the ladder networks wrap? RS Logix does this automatically, I remember in S5 having to do something with the view to make that work. But I cant figure it out with TI 505.       

Joe, You wouldnt be able to measure the voltage out of the Mini DIN side for me would you? I am considering building a new cable, but it has that TTL board in there. I am just wondering what logic level the TTL is using? I know the PC port puts out about 13VDC for the RS232, I am assuming that the TTL is likely at 5V, but knowing GE it could be something really weird and super proprietary.   

Joe, I fired off an email to proface tech support (who have been amazingly helpful throughout this ordeal) to ask about the readings we are seeing. That drawing is actually for the GPW-CB02, they told me over the phone the CB02 is the same as the HMI-C49, but I am emailing just to confirm again.  When I did work as a Navy contractor on submarines, and did ALOT of troubleshooting RS232 and RS422 communications I used to carry a little kit with a DB25 pin breakout box, and would use the 25 to 9 pin converters to bring signals to the bob. We also built all the cables with the crimped and pushed in style d sub headers, and the backshells were all screw together not molded. I am really missing my little kit with the break out box and the female and male pins right now. 

So I used some of the fluke clips and made some tiny leads out of stretched open paper clips, put the cable in a soldier "third hand" station with a magnifying glass, made sure there are no jumpers in the dsub side and the first two pins I touched had continuity. All in all I got the same readings I got before. 3 pins, continuity across them, and continuity on each to the mini din backshell.  I am going to say that this cable has to be a problem. Thank you much for all the help. 1000 points to you kind Sir. How do I give you some reputation or +1 or something? 

Joe, thank you very much, I am going to get some pin extenders and check it again. If I find the same as we did before I am going to call it a bad cable. The cable I have here is a HMI-CAB-C49-J. Which is the same as the HMI-CAB-C49, shipped with the TCP quick panel junior.  If you want to ship me yours, Ill trade you. I have a semi-trainable operator named Ronoo. and I'll throw in a $100 walmart gift card?  

Joe E no I am not sure that they arent supposed to be we are assuming. The pins  1, 4, and 6 per this drawing (sent from ProFace,) have continuity together and have continuity to the mini DIN backshell If you wouldnt mind checking your cable that would be amazing. the drawing shows the jumper placement on the HMI port side for a tool port test. but referencing it to the mini din side of the cable those are the pin numbers with continuity.   

Joe E. That is a really good Idea to build a separate hard drive with an XP. Unfortunately real quick is not a word when you are in the middle of the Gulf of Mexico and you need parts. I screwed my laptop pretty badly yesterday after partitioning. The MBR got hosed and UBCD was not able to fix it. Luckily I am smart enough to have made an image of my drive before I started partitioning. It took forever to image and recover using macrium, but think god I took the time to image it. We also found the HMI-CAB -C49 cable I have here has shorts across three pins and all three are shorted to the backshell of the mini din connector. So we pulled the panel and put it on the boat going in for an RMA repair.  Russ, I agree. I almost always use the native serial port on this machine. Working across a VM makes that a bit hairy that is why I use the USB / Serial. In this case the issue had to be the cable. I am still not sure if the quickdesigner will work across a VM but I will let you guys know. 

Joe E, Thanks for the info. I am using the physical serial port, and I have a prolific USB / Serial. I installed the Prolific Drivers on the VM and using the USB adapter is transparent to the software, as the drivers add a COM 3 port, and I just pointed the quick courier (upload software) to the com 3. Based on the Tech Support recommendations I have stopped using the dongle and just gone to using the physical port. But I am not so sure that the virtual handling of the physical port across the VM is not what is causing the problem.  I built a win2K pro VM last night, as the ProFace USA Tech Support (the only people offering any support for these) recommended. got the same indications. They seem to think that the problem is with 1) the tool port on the HMI or 2) the com port is being taken over by another software.  I doubt its the tool port, because I am trying to connect with the same indications on 2 HMI's. So you know basic troubleshooting is... whats common? the com port.  I am thinking that I am going to have to build an XP partition on my laptop, or a Win2K partition and try that way 

I use the RedLion N-Tron and Sixnet managed switches, not sure if either do port address translations. but they are reliable and easy to get.    http://www.redlion.net/products/industrial-networking/ethernet-solutions/managed-ethernet-switches