Worms get deeper!

I am quite surprised that this is the first time you have seen this. I use mainly Omron PLC's and have found words swapped on Modbus RTU from Nemo power monitors (Italian). I have also used Device Net extensively and found information read from an AB Powermonitor 3000 by explicit messaging was received with bytes swapped and words swapped.
With the Device Net trick, "Praise The Lord" I knew what information I was looking for and it did not take long to work out what had happened (only about an hour pulling out what little hair is left). The "Swap Byte" function worked a treat - just specify how many words and it does it seamlessly. Swapping words is a little more difficult as, despite Omron's huge function list, the latest PLC's do not appear to have a swap word function. "Move" and "Transfer" used extensively.
The Modbus RTU one took a little longer. Finished up using a serial port protocol analyser called "PAT". Very good. Then figured it out.
The following "Beerchug" indicates the next port of call.
beerchug
 
JRW,

So whats the winder consist of? Is it a center wind application or surface winder? Is is a Siemens 6SE70?

It's a dual spindle turret paper re-winder with a pair of Simovert Masterdrive VC's on each winding spindle. There's a simovert VC for the turret index motor, as well as a Simovert MC drive as an outfeed nip drive.

Does it have a tech. board? T300 of T400?

The winders have, I think, T400 boards for the coiling application. The documentation I have (OEM supplied) and can find on the website is vague. Apparently, the T300's are no more--that's why I think we have T400's--that's the documentation I find on the web site.

I am sure- if you knew something about Step7,you would never use AB again.

I know this about Siemens--the simovert manual says the drive supplies 32 bits--4 bytes--of status to the profibus--The PLC reads 3 words--2 from the drive--one from the technology board--After you get past the little/big endian thing, the drive documentation is OK but the tech board documentation is very very unclear about what the 16 bits from there represent.

I've used SFC12 on applications where a piece of equipment had to be detached (it had a few drives and ET200S I/O). The operator would press a button on the screen, then detach the folder section. The SFC would "turn off" the slaves- thus the OB's would not be called. Presto- no red lights.

My system uses the Et 200's also. The problem is, that they only interrupt the power to 4 of the 16 outputs at once. If I use the SFC12, I kill all 16. No can do--need the others. I could simply wire and program the Position LS's into the ladder and interrupt the output coils there, but this steps on the Hardwired interlock--which is the crux of the thing here--they wanted a hardwired interlock to the solenoids, and they got one--but their ill concieved method causes a failure indication. I thought that maybe there might be a way to mask, or ignore, the individual faults from any given node of the Profibus, but can't find anything in the books to support anything along that line.

I plan to install a pair of 4 pole relays and interrupt the power to each solenoit at the output end of the module, rather that at the power supply end. I guess I should disconnect them all before I do all the wiring, first, to see if this method causes some kind of "open output device" alarm on the module. If that's a problem, I'll do somethin else. As Senator Howard Baker said once as he sat at the Nixon Watergate hearings " As we say down there in Tennessee, there's more than one way to skin a cat.

On the detached equipment application. We've done a little of that. I have a piece of equipment, a folder/gluer, which utilizes 2 seperate pieces of support equipment, feeders, at different times. Both feeders are controlled by the main machine's PLC. Both feeders have different features with different control schemes and different types of devices that "share" I/O and wiring in/to the main controller. Both feeders connect to the main machine via the same electrical connector plug--one feeder or the other. There is logic to control each feeder in the PLC. The PLC recognizes which code to run via a jumper on each of the feeders connector--it knows which one is plugged in at any give time. If the operator wants to change feeders, he just unplugs, rolls out, rolls in, re-plugs, and the controller takes care of the rest. This system was done in house with AB--not siemens, software--not hardware, well concieved ideas--not "lets make it work and get outta here" attitudes.
 
Swapping words is a little more difficult as, despite Omron's huge function list, the latest PLC's do not appear to have a swap word function. "Move" and "Transfer" used extensively
Bob:
Here's a few pages on the SWAP and XCHG functions in the current Omron instruction set.
 
Thanks Jay but I have used them both extensively. Quite used to the manuals, all 3 inches oe so of them. Have been using and/or selling Omron for 15 years or so. Love the "SWAP" byte function - start word and how many words entered and it is all over. Would like to see "XCHG" set up the same way instead of having to write an "XCHG" function for every pair of words that need to be swapped.
Love the digital library that has been released in Australia. Do not know if you have it over there yet. If not, contact Omron Australia for a copy. It gets better every issue.
I hear from people in Oz that you are a bit of a guru. Quite a compliment.
Regards
Bob
beerchug
 
Last edited:
Nutin' but worms!

I have worked with Profibus extensively in the past couple of years. I have seen the byte swapping quite regularly. Basically it is a difference in processor families used in the devices and masters. those processors that run on a Intel base format and those that mimic the Motorola format read in opposite directions, Intel reads from right to left and Moto. from L to R. therefore MSB and LSB get swapped. First practice I have inherited is to "ring out" the I/O on the network to make certain which slaves swap bytes and which don't back at the master.

Profibus standards have not implemented specifics as to weather the master should "clean up" the incoming data.

I hope this offers some insight. It's not really wormie just a difference between product vendor hardware. banghead

Regards.
 

Similar Topics

Well pardner, I can't speak for Alaric, but I is often wrong. Not this time, though. (Actually, I was kinda feelin' ornery and did my post partly...
Replies
36
Views
22,972
How much detail do you go into in your schematics? I've seen schematics where every termination is labelled, every cable line is explicitly...
Replies
8
Views
5,385
Programmers of all type PLC's: We are presently wrapping up a project to replace DC drives on a paper/plastic web handling machine.This project...
Replies
21
Views
11,332
Just an FYI. This may get pulled but I am going to state it anyway. This forum is open, very open, it leaves alot of things open for those that...
Replies
4
Views
6,939
Back
Top Bottom