pcmccartney1

Generally speaking, Rockwell controller execute from left to right, then top to bottom. I do caution you that not all function blocks execute in one scan of the code.  Specifically, the COP.  Having gone round and round with RA Tech Support, eventually deciding to use the CPS rather than COP.  Not as important for your example as there is little to copy.  More important when copying large arrays or UDTs.  

Worst case scenario, use a one second timer's done with a one shot to ADD block them compare the add to 8 hours or 8*60*60=28800.  Which, to Jeremy's point, is well within the capabilities of any of the timers in any of the platforms from Rockwell. 

Forgive me, but you stated that the ACSII value comes in HEX and represents a whole number value in mm, so why do you need a floating value? Either way, you can create some test code in the PLC and find the right combination the yields the known value and works over the entire span/range of expected values.

FTView ME is able to log data to files.  These files can be to internal storage or external storage (either CF Card or USB). Alternately, a PC with RSLinx (acting as an OPC Server with a configured topic) could have an excel spreadsheet configured with VB to make HotDDE pokes of tags from the database.  Kind of like a real time dashboard. There are many examples in the forum .   Try looking at Sytech or Crystal Reports, these are fairly inexpensive packages for doing what you are asking. Personally, I use Sytech's XLReporter.

The short answer is no.  FTView wants the file and folder structure that is presented to you.  There are others here with more detailed explanations, but there are many background processes running that are creating and assembling directories that can not be changed. The Displays folder is organized alphanumerically.  Consider renaming your displays (yes, I realize that you will need to examine every navigation button and every "Touch") by process area or station.  Make use of cross-reference, find and replace tools to make this a quicker process. Reduce the number of similar displays.  Rather than having many copies of the same display with different tagging, create on display and use parameter files and parameter passing.

The 78 is indicating that an "expected" node or nodes is (are) not communicating with the scanner.  The scanner is configured with the fore mentioned RSNetworks for DeviceNet software. As far as finding the nodes,  the RSNetwroks is the best tool.  Without it, then the  PLC program might be well documented enough to point you to the faulted nodes. Will's absolutely correct, there is more than likely nothing wrong with the scanner or the configuration.  More than likely there is a physical problem with either the wiring or the device has truly failed and needs to be replaced.  The majority of DNet devices have a set of rotary switches for setting of the node address.  You'll need to follow the truck cable and check every device's physical address to locate the faulted nodes, then diagnose the problem. Again to Will's point, is it possible that the nodes have been decommissioned and removed?  If so then the DeviceNet scanner will need to have those nodes removed from it's internal scan list.  It is possible to write code to "deactivate" these nodes from the active scan list in the DNet scanner via explicit messages.

Red Lion has free software on their website called Crimson 3. Tons of native drivers to various PLC platforms and protocols. Is the PLC a MicroLogix, SLC, Compact or ControlLogix? The obvious difference is in the native tagging scheme versus the old B3 or N7 file structures. Not aware of any conversion tools, you'll have to recreate on your own.

As a SI, I actually think about y'all and make decisions on platforms and software that you already have, are intimately knowledgeable on and can support.  While technology continues on at an ever increasing pace, just seems the tried, true and proven get discarded for new, fancy, end all be all, full of promises, short on delivery platforms. Just seems that the Micro850 was rushed to market with an "Alpha" rev software software and even in the years since, no remarkable improvements have been made. I won't deny that it's a viable choice for an OEM, but generally I'm not interested in taking a leap of faith on unproven and less than widely accepted platforms just to save a few hundred dollars on hardware and lose several thousand on the programming, debug and support. Sorry for the run-on sentences, but I was typing a stream of conscientiousness.

Further to Will's point of it being trial and error,.  You can set everything correctly for your assembly instances and sizes, but need to verify the Comm FOrmat, by default it is Data-INT, but your device might need another format.

Michael & Will are certainly on the right track.  Still confused as to what type of PLCs and what type of Panelviews are currently deployed. Food for thought: Assuming the furnaces, the PLCs and HMIs and control scheme are nearly identical.  Consider merging the ME apps into one application and do parameter passing.  This would mean only the addition of a ME & Runtime license to the control room PC.  The engineering PC could maintain the RSLogix and the PVs (either ME or PB32), as well as the Control Room PC HMI application.

You'll want to add limit logic that turns on and off a output coil tied to the physical output on the MicroLogix1400.

Ok, since you have v10 installed on both PCs and the file won't open on the Win7, I suspect that the install of RSLogix5000 went poorly on Win7 machine. Have you been able to open any other files on the Win7 machine?  Specifically, v10 files?  If not, then uninstall and reinstall RSLogix 5000 v10, verify you licensing is correct, then try to open the file. Barring any further success, I suggest you call RA TechSupport.

Now what versions to do you have installed on your Win7 machine?  You will need v10 to open the file. From the picture, I would say your RSLogix 5000 might not be installed correctly, remains to be seen.

You will need to add the PF525 as another drive under the 1768-ENBT and suggest you use another IP address. Doing so will create the tag database for you.  The registers do differ in both the inputs and outputs. Generally, you should be able to do a tag replacement through your code.  Those that give you an error, you just need to get the actual tag. Remember, if you use any of the PF400 tags in your HMI, you'll need to change these also.

Thanks for the correction Ken.  Didn't realize the Lite limitation on data serving.

Gromit,   Not an exact answer here, but... For serial numbers, this should be ok.  My reasoning is that integrator, like my self, have multi-seat licenses that are all under the same serial number. RSLinx Pro vs. Lite, should work fine, Lite is just limited on the number of connections. RSView32 app conversion, absolutely can be converted to FTView ME or SE.  The website has plenty of documents on the the conversion process.

Not sure it's a solution, but run the compare tool between the two programs.  Be sure to go through the database to see the differences in settings in all tags.  Most importantly, the Axis tags. Are both CPUs at the same firmware revision?  Any possibility that the L73 version doesn't have the correct motor database associated with the program?

Having just done this last week, you need to do exactly what the dialog boxes are telling you to do. Put the project on a Win XP 32bit machine and run the first part of the conversion "Export". Move the project to the Win7 64 bit machine and run the second part "Create FactoryTalk View Database in new format". At this point you should be able to open your project in FTView.   If you don't have an XP machine, then you'll need to post your "Legacy" project and one of us can do the first part for you.

Looks like Anybus has one for DNet Master.  Not that I have ever used it, but Anybus tends to be very solid with all of the various products and interfaces I've ever purchased from them. http://www.anybus.com/products/products.asp?PID=103&ProductType=Master%20Simulator Also looks like they have one for Profibus.  Hard to tell if it's the same platform as DNet, but probably a different adapter.  Not sure about CC-Link

I think you need to go offline and change the number of expansion modules to equal 0, then download again.

Even as a service, the RSLinx should appear in the tasktray as an icon that you can double click on to pull up the full GUI. Say that doesn't work, you can goto Start/Rockwell Software/RSLinx/RSLinx Classic Launch Control Panel and turn off the "run as a service" then the GUI should appear.

You must create the mer at the firmware level of the PV+ you plan to run this application on. You'll need to shutdown the PV+ current application to get to the configuration screen and then navigate to the location that tells you the firmware revision level. Then create the mer at that level and then download

Wow, never even hear of this one before.  I looked it up on AB's literature website and found a manual, please see attached. Appears to be a fixed IO version of a SLC.  Probably a forerunner to the eventual ML series.  It has 24 Digital Inputs @115 VAC and 16 Relay Digital Outputs.  You could add a 2-Slot expansion rack and add additional IO.  Just for giggles, I opened up RSLogix500 (v8.40.00 CPR 9) and started a new project and found the L40A as a valid controller type. 1747-um009_-en-p.pdf

This might be totally unrelated.  I've always had trouble with the BOOTP server.  I traditionally always use DF1 via RSLinx on the older CompatLogix.  On the newer CompactLogix styles, you can use USB.  If forced to use BOOTP server, I have always found it to be a two part effort.  First time to set the IP, close out BOOTP Server, restart BOOTP server, find my new IP and disable the BOOTP successfully.

Generally, no, the PLC cannot generate and excel spreadsheet.  It is usually the domain of the HMI or third party reporting packages like Crystal Reports or XLReporter. The PLC is monitored via RSLinx Classic or Enterprise to see events or triggers that then generate the report.