hugheydarryl

Yet we lived thru the 60's and we are here to have a discussion.  Have you ever seen the OSHA approved cowboy?  The PLC is safety locked with safety signatures.  Not trying to make something unsafe ... but safety is #1 until it interferes with production.  Mention how much upgrades will cost and watch them turn a blind eye.    

I found that our machines were done completely with this mapping procedure.  I was able to accomplish exactly what I needed.  Thank you kindly! 

We have been doing this for about 10 years using an Omron area scanner on some of our machines.  These were new machines and were set up by an outside integrator.  We used physically wired outputs for zone switching and only use the checksum over ethernet to make sure the scan area had not been changed.  These scanners setup a tag in the PLC and it also set up a module defined tag that I can select to use in the safety PLC.  I would create a tag and select the type which allowed it to be read in the safety PLC portion. These scanners are wearing out and very difficult to get now and Keyence is able to supply us with new scanners that we can use in the same fashion with the wired zone selects and the same OSSD outputs.  When I set up the scanner it created the data structure for the PLC and it also created the module defined tag structure for the safety program .... however the safety PLC tags are not updating like the standard PLC tags.  I just figured ... I was missing some important step or possibly a setting in the scanner software itself.   I didn't set up the original scanners and just trying to keep the machine plugging along.  I am just trying to keep the same structure as what is there. The other option was to convert it all over to CIP safety scanners ... however I have not ever set that up at all. Thanks for info.    

I am installing an area scanner on a machine and have used the manufacturer EDS file to create data structure for the scanner.  The data file is created automatically as a controller scoped data file.  I have a safety PLC program and cannot access the data from the regular PLC program.  Is there a way to map the data from the PLC program to the safety program?

I am trying to load string data in some registers.  I am using the [ $MOV "20.job" R10700 } instruction. This moves the "2" into the first 8 bits of R10700 and the "0" into the next 8 bits of R10700.  The "." is then loaded into the first 8 bits of R10701 and the "j" is loaded into the next 8 bits of R10701.  So on and so on. I am needing the data to all shift 8 bits so that the first 8 bits of R10700 are empty and the rest follows. I tried the SFL instruction ... but it just removes the bits from the lowe byte. Any suggestions on how to fill my registers starting with the upper byte of a word or to shift all my bytes leaving the lower byte of the first word empty. Thanks,