Jump to content

Joe Tauser

MVP 2017
  • Content Count

    1,910
  • Joined

  • Last visited

  • Days Won

    179

Everything posted by Joe Tauser

  1. OMG. This is near and dear to my heart. Behold, the latest iteration of the JTA ILD Tester- "ILD" stands for Initial Loft Deflection Test and was developed by a customer / manufacturer of nonwoven material (think white fluffy stuff in cushions) and is based on the ASTM IFD test used for foam. I incorporated a 25/65 test into the program if they want to test foam, too. This was developed to be a production tester to test samples several times a day. It's not as accurate as an H-frame tester, but super rugged and a hell of a lot cheaper. Accurate to 0.1 pound and 1/8 of and inch. The first iteration used a V120 back in the day. It's come a long way. Joe T.
  2. If you're going to go shopping on the Evil Empire's website, this would be so much easier- https://www.automationdirect.com/adc/shopping/catalog/relays_-z-_timers/electro-mechanical_relays/slim_interface_relays/kpr-sce-24vacdc-1 Joe T.
  3. 1850 RPM should give you a frequency of about 31 Hz. If you're getting a frequency of 190 then you're getting more than one pulse per rev. That prox has a frequency response of 900 Hz, so it's very possible that when you're running the prox is triggering a couple of times and you can't see it without a scope. The thing to consider is resolution. The PLC can't do fractional frequency, so you'll have to multiply the frequency by 60 to get RPM. Which means your RPM display will jump by counts of 60. This may or not be OK. If your setup is repeatable and you always get 190 Hz at full speed, then you can take advantage of that and multiply your frequency by 9.73 to get RPM, which will give you about 10 RPM resolution. A better way may be to run the 0-10V pot signal into an analog input and read that instead (assuming the pot is separate device and not built into a drive). Then you have 16384 counts to play with and will be able to display RPM much more precisely. Let us know how your motor is controlled. Joe T.
  4. There can be only one answer. I've said many times that empirical data is the best data. If kpetro put 0 in and the linear block worked properly then the spec sheet is misleading and the scaling is spread over the whole 15 bit range, not starting with the 4 mA offset like we're used to. I configured a remote I/O drop with that module. You can choose what your input will be: I haven't personally used this module, but we can deduce that the module takes the configuration into consideration and returns 0 counts at 4 mA. Allen Bradley does this on their CompactLogix I/O, so it's not out of the ordinary. It would be nice if it were documented better, but I have a feeling that Unitronics is relying on the manufacturer for this. Joe T.
  5. OK. Set your com parameters 9.02 to mode 4 - 9600 8E1. For some reason Even works better than Odd if None is not available. Cut off the end of your com cable on the PLC side and put a new one on- This is in the Visilogic Help if you dig deep enough. PLC VFD 2 2 4 4 3 3 You also don't need to put the "4" at the front of the Modbus address. This is implied as it's a holding register. Confusing, yes. And Unitronics starts counting at 0, so you need to subtract 1 from the register you want, so for frequency you need address 8450. Also confusing. I've hacked the program a bit. Let us know if it works. Joe T. MODBUSTEST_JT.vlp
  6. Take a look at this post- Download a look at the program I attached called Jazz Stage Example. This should help you start to form your sequence - you'll be stepping through a timer-based sequence where you move different setpoints to your PID block. How are you controlling the air pressure? Start your program and then post it here with questions you have. Joe T.
  7. Your "Timer Scale" UDFB had INT8 data types in the Function In definitions. You were calling it with numbers larger than 256. Stay away from this data type unless there's a really good reason to use them. Stick with INT16s and INT32s. Joe T. TestMachine JT.ulpr
  8. What is the size of the USB drive you used to update the firmware? It needs to be at least 8 GB. Joe T.
  9. Look into the DataXport utility. The data you broadcast must be in a Data Table, and it will automatically read and send the data in .csv format. The downside is you have to run this on a PC somewhere, but it uses the PC's email capability. Joe T.
  10. I realized you are asking about running an RFID reader into a UniStream. I looked at the V700 demo program and it's reading data from the RFID reader as UDP RAW data. Vision is very different from UniStream on how it interfaces to external devices. Getting back to your question, I have connected barcode readers to a UniStream using RS232 and it wasn't much trouble. I did have to get an RS232 com module for for the UniStream. So probably the next thing to do is for you to pick out an RFID reader and we'll help from there. Joe T.
  11. I opened my program on my office desktop running 9.8.80 and Win 10. It worked OK PM me your program and I'll take a look. Joe T.
  12. I've seen that behavior on Win 7 on an older laptop. This is probably the most dense screen I've done on a V1210- I'm still running 9.8.65. Between static and dynamic elements it has about 250 items. If you click between items it jumps right to them, but if you click a blank space it takes about 5 seconds. This on my low-end Dell Optiplex 990 desktop. My laptop is a different story. It takes 10 seconds to jump between elements on this program. One thing that came to mind is I always put a cheap graphics card in my desktops - I never use the on-board video as that uses system RAM. On this box I've got a 2 GB AMD Radeon R7 240, which was about $50 at MicroCenter. On a laptop you don't have that luxury. Also, Visilogic is still the latest revision of a Visual Basic program. It's old and heavy when running on a modern OS. Are you running 32 or 64 bit Win 7? I'll try editing this program on my computer at the office, where I have 9.8.80 installed for forum questions. I do have a graphics card in that one as well. Joe T.
  13. I have one of those demo cases. This is the RFID reader it uses- https://www.promageurope.com/products/rfid-readers-and-writers/rfid-readers-20cm-gp20-30cm-gp30.htm It sends the data to a V700 via ethernet. I'd ask Unitronics at support@unitronics.com for the UniStream Demo Case V700 program to get sample code. Joe T.
  14. You're going to have to make a stepping program to address each slave separately. This is going to be a bit of a beast. Since you have to read and write each slave and they are Unitronics PLCs, I'd make use of the special Modbus Read/Write Mixed Data function. A couple of questions- 1. Have you made a mapping spreadsheet showing what registers in each slave will go to / come from which registers in the V1210? If you haven't, do that first. 2. Have you started the program for the V1210? All you'll need in each slave is a Modbus Config and a ScanEX block. If you can post the programs you've done so far we can hack it up and try to help. Joe T.
  15. The PLC starts scanning at the top of the program on power cycle. Which implies that all the outputs should be off initially based on your logic. However, one of my T-shirt sayings is "Empirical Data is the Best Data", and I believe your observation. It sounds like the output memory area is not getting cleared on a power cycle. I would send an email to with the contents of your post to support@unitronics.com. Please let us know what they get back to you with. We're mostly volunteers here. Joe T.
  16. I'm running 6.6.43 on win 10 and printed to PDF using the Microsoft Print to PDF printer as a test. It worked OK. Joe T.
  17. You got the Protocol Send right. You can create a string data type in a data table that will make your life much easier. Just right-click on the column header and define the string length. It looks like you've already figured out that you can rename the column. Double-click on the cell to edit it - remember to save. Retrieve the data with a Data Table Read Row into an integer array Then load the array into your Send block and trigger it. If you want to post your program I can poke at it for you. I'm always happy to help those who have put some effort in. Joe T.
  18. The servo is a soon to be released product. Sunit must have gotten his paws on one of the beta units for this project. That information wasn't supposed to be publicly released yet, as Unitronics doesn't want people hammering them with "When can I have it? When can I have it?" A salesman will sell a new product regardless of whether he can actually get it. Joe T.
  19. As a final comment, what I put out is just that - math. Your final results may vary. Don't order 100 pieces - start with something like 5. <rant> Define "quite expensive". Is this data kind of important or very important? I think management is freaking out over the overall cost of the project and struggling to get the cost down and pointing to a large dollar line item without quite understanding what's involved to roll your own sensor. When I was a young man I tried rolling my own 4-wire ohmmeter that was an integral part of a wire plating process. The short version is we tried to make my circuit work for a month in production only to determine that what I had come up with was not accurate enough nor could overcome the inherent noise in the process. We had to buy a $5K meter that worked in the process right out of the box. So often I see a company hire a young engineer and put him in charge of something that is really out of his league. "Oh, he's and engineer! He can figure it out!" But what's missing is the crusty old engineer to give him guidance. So he comes up with a process controller / monitor that is based on an Arduino or a Raspberry Pi. And he thinks he's a genius, just ask him. And then he goes and gets another job and nobody has a clue how it works. Consider the value of your time and how much damage you will cause if this doesn't work or is flakey. Also consider who gets to maintain this thing. If you built it, you are married to it. If you do go forward with this be sure to document the shit out of it, including ordering spare parts and writing a calibration procedure. That's what professionals do. </rant> Joe T.
  20. I love browsing aliexpress. So many bargains! Delivery time? I forgot to look at that! I do think that adding Modbus to this mix would overly complicate the code. But it is an option. @cleman84 - I'm a Dwyer dealer and I use and recommend those CCTs all the time. When the first came out I put them on my old-tyme Fluke 760A meter calibrator in AC current source mode and found them to be amazingly accurate for the price. But as you found out - AC only. As far as making your Honeywell sensors work, I see the CSLA2DG 150A sensor you've chosen has a 16.2 mV / amp output assuming one pass of the wire through the core. Cranking the math gives you a 2.43V change for 150A It also has an offset of Vcc/2, so when you apply 12 VDC power it will have an idle output of 6 VDC. There's a reason the DC transducers cost a bit more - you really need to amplify the output signal and remove the offset to come up with a standard process value. Or not. I've never tried the Raw Value configuration and the E3XB datasheet says something about frequency when you select this. I'd use the 0-10V range in 14 bit mode. This gives you 1 count per 1.63 mV, so you'll get about 10 counts per amp. Also take into consideration that the A/D will "chitter" a couple of counts all the time. Plus +/- 0.4% full scale error, which works out to an uncertainty of 66 counts, or 0.6 amps on a 150A full scale device. Just make sure your eyes are open before you jump into this project. Joe T.
  21. The STRUCT block was specifically designed for packing various data types into a chunk of MIs for UniCAN. Look at the Help on it. Joe T.
  22. I'm guessing your baseline is DC transducers in the $150 each range. Those are raw sensors and you're going to have to build a circuit board for them. And come up with a dedicated 12 VDC power supply. And test each one's output with a known meter at several points to calibrate them and set up your program. But yes, they should work. Give yourself a couple of days to do it. Joe T.
×
×
  • Create New...