MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Beuwolf_1

  • Rank
  • Birthday 11/13/58

Contact Methods

  • Website URL http://
  • ICQ 0
  • Yahoo Grey_road_ogre

Profile Information

  • Location NW Wisconsin
  • Country United States
  • Interests Mostly outdoor oriented, kayaking, motorcycles, camping, and road trips. Anyplace I can get away from a phone.
  1. Simple problem but driving me nuts!

    Thanks for the help. The multiply by 100 got me to thinking. After that it was all downhill from there. I knew I was missing something simple and that got the ball rolling. Thanks again for the assistance. Even the Boss thought it was a cool idea. LOL
  2. I know I must be missing some thing but what I'm looking for is a bit of sample code or insite into an IBOX that will allow me to enter a time, Hour and Minute, for an operation to start and a time in Hour and Minute to stop. I need it to automatically start and stop if the times are changed. I have no problem with the start and stop I have now but my boss would like it to sequence correctly in real time if the schedule is changed. I am using an equals on start and preset hours and minutes to start and stop. But if the start time is set earlier or later, you need to wait till the next start time for it to correct. He would like it to monitor the presets all the time and start and stop as the presets change. While the screen capture isn't clear it should give you an idea of what I'm presently doing. If equal to hour and minute start time, latch the output. If equal to hour and minute stop time, reset the bit. Once its latched, changing the times require it to complete what it has first and then go. So if anyone has an idea or example or an instruction set I have missed, I sure would appreciate it. Thanks in advance
  3. Horner PLC's

    We have used quite a few of them as multi function process controllers for things like temp control and fan controls. We haven't had a failure in the five years or so we have been using them. The language is a bit crude and hard to grasp at first but for the price, not bad over all.
  4. Has anyone tried the new Click PLC yet

    Thats the problem I think is the fact that the drive takes a five digit numbering, and the Click is six digits. I tried to use hex addressing with no results. Also I am using a FA-ISOCON to convert the RS232 to RS485, and not sure if thats working or not or if the drive isn't getting the info cause of the number issues. Any help would be appreciated.
  5. Has anyone played with PLC Direct's new CLICK PLC? Seems pretty cool, but not sure how to do addressing in modbus. I sure wish things were more transparent when it comes to modbus addressing. Any info would help.
  6. Barcode Scanners

    Well from past experince with bar code scanners and readers, they will allow an external trigger to let them read the right code, or they can be configured to accept any code that it "sees" as long as that code is legible. I've used scanners to configure machines by product, and prefered to have it do the scan when the product is presented.
  7. Hmmmmmm. I guess I'll stick to my lowrider. The old shovel head ain't that fast, but its plenty reliable, and compaired to the bikes that seem to be the center of attention, a lot slower too. But while ya'all will get there a lot quicker then this old biker, I sure hope I look a lot better while I'm on my way. lol As far as the Bike VS the Robot, I also think I will stay with the two wheels. But I gotta give credit to the programmer who did manage to make a robotic vomit comet.
  8. Another Modbus application

    Well, according to the rest of the world, this shouldn't be this difficult. But I did manage to get the reads to work, now just need to figure out the madness to the addressing of the writes. Seems like in order to do what I would like to do requires way too much overhead in the program. It sure would be nice to be able to do some indirect addressing but thats no possible with this guy.
  9. Another Modbus application

    I am attempting to use the Modbus link on a Lenze AC Tech SCF series drive with an Automation Direct D06 with a D0-DCM module in slot 4 of the plc. I am using port 2 on the DCM to attempt to communicate with the drive but am having absolutely no luck. I plan on using TB1 as my start/stop command thru an external relay fired from the PLC but wish to set the speed of the drive thru the Modbus link, and also read back speed, current draw and any faults the drive might have during operation. I have never had the pleasure of doing any Modbus stuff in the past and was wondering if anyone had any examples of programs that might be addapted to the Lenze drive. Normally I would attempt to sweat this out in the wee hours of the night with no one to bother me, but unfortnately, time is of the essence
  10. TC connections, best practice?

    Just had to ask if it was a feed back problem with grounding. We've had Type J TCs give strange readings due to stray voltage differences between grounds. Just an idea that I though would be worth mentioning.
  11. Vacuum application

    The cups we have used are about four inches in diameter, and last a long time, the biggest issue with wear is when the board is still moving when the cups try to engage. I would suggest looking at some of the standard type industrial cups. There are a lot out there and a wide variety to choose from. I would go with the type that has the steel backing tho, since those do last a little bit longer.
  12. Vacuum application

    The dwell time I was thinking about would have been about a half second is all. That doesn't seem like much but it is enough time for the cup to conform to the surface of the board and get its grip. Some people make the assumption that a cup is suckin the milisecond it makes contact with the target and don't give it a chance to develop a solid grip. Two seconds is way plenty of time to do your operation. I would think that a bellows style cup would probably be a good choice as well for this application just cause it can conform to a lot more profiles then a solid non-bellows style cup. Hope this helps. Beuwolf
  13. Vacuum application

    I've done a lot of vacuum applications within the wood working industry. We made machines to lift sheets of plywood into forming machines prior to becoming kitchen countertops. There is no problem with suction at all, but as others have said, filter it before it enters your vacuum generator. The other thing you really need to remember is have enough dwell time for your vacuum to generate prior to the lift, and also ramp the speed slowly. The best way is to have a series of cups, one to lift one end of the board first, and that breaks the "suction" between the boards themselves, and the rest to actually do the lift and carry to position. We averaged one sheet of ply about every 30 seconds, and while that seems slow, that was on a rotating selection system that allowed different sizes and thicknesses, and we seldom had a sheet fall.
  14. Mechanical Press Two Hand Controls

    I assume that its a mechanical press. Either way if you check the OSHA regs, it says that what ever you use for a "safety monitor" should be fail safe, and that pretty much dictates a redundant processor. Besides the anti-tiedowns, there has to be a brake stop monitor as well. Guarding and such is pretty well stated that it has to be interlocked, and cannot be operated with the guards removed, unless you provide a "bar mode" in your monitoring that allows the clutch and brake to release so that the setup operator can manually move the press for set up of shut heights and such, without the motor in operation. This is only for smaller presses, and larger units require blocking anytime the guards are removed. Before investing a lot of effort in design or development of press controls, it might be wise to check out the commercially available units just for liabuility purposes alone, and then install what ever control for feeding that you may need. Beuwolf
  15. Trying to self teach

    Well lots of "data" that an HMI has on display is either static, or dynamic. Static displays such as text or graphics are stored in the HMI and displayed only on the operator's screen. Dynamic information is stored in the PLC. Anything that changes with the machine that is displayed would be dynamic. There are two forms of dynamic info on a HMI screen. One form of info would be your temperature set point. You enter that and it is written to an address you assign for the plc to look, the other is information written to the HMI from an assigned address, such as the actual temperature of your cooling process. Inside the PLC "junk" is always stored in binary, but the development software usually allows you to display it in what ever format you desire, ASCII, binary, hex, decimal, octal and what ever else someone has thought handy. Where the fun starts is how you want the HMI to interpret or write stuff. Some of the more programmer friendly HMI's allow you to enter ASCII strings as text, and some of the more stone age units require you to enter the ASCII strings as segments of ASCII Code. Just remember that no matter what, PLC's and HMI's only do what you tell em to do. Not what you wanted them to do, so take your time and just have fun playing with stuff. I think most of us learned by examples, thought, experimentation, and picking apart other people's programs, and I know I still have favorite subroutines I have "found" or written myself over the last ten years or so. Hope that helps a lil bit