Jump to content

Joe Tauser

MVP 2017
  • Content Count

    2,008
  • Joined

  • Last visited

  • Days Won

    187

Joe Tauser last won the day on January 12

Joe Tauser had the most liked content!

Community Reputation

289 Excellent

About Joe Tauser

  • Rank
    Moderator
  • Birthday 02/06/1964

Contact Methods

  • Website URL
    http://www.jtauser.com

Profile Information

  • Gender
    Male
  • Interests
    Antique Radios!

Recent Profile Visitors

20,460 profile views
  1. 1. Start by looking at the Modbus programs in the Examples. Then read about the Modbus protocol - http://modbus.org/docs/PI_MBUS_300.pdf - so you know what it is you are trying to accomplish. 2. Post a link to the modbus information for the VFD you're trying to talk to. 3. Determine what the physical connection to the drive is - RS485, RS232, or Ethernet. Then figure out how to wire it. 4. Try writing a program yourself based on all the above. 5. Post your code and ask specific questions. Do NOT ask for an example specific to your application. We're here to help, but it's up to you to figure it out. Joe T.
  2. Modbus is a standard protocol. Unitronics just implements it, albiet starting the data address pointer at 0. Otherwise it's the same as everybody else's. I spent a day with a customer last week with a similar problem - he had 9 devices on an RS485 network and one of them just wouldn't talk to the Unitronics. I had no problem talking to it over the same network with my Modbus simulator program on my PC. My simulator allows monitoring the network traffic with time-stamping to .001 second resolution and I was eventually able to determine that the problem child was taking longer to respond than the other sensors. We fiddled with the timeout and retries on the Modbus config block in the program and got it to work. If you want to post your program we can have a look at how you've got Modbus set up. Also post a link to the Modbus table of the device you're trying to talk to with the program. Joe T.
  3. That's an easy one to overlook. I've gotten in the habit of assuming a new software revision includes a firmware revision, but you're not reminded by the software to check it. Joe T.
  4. Well that's irritating. Your solution, however, is clever. Pretty has nothing to do with it. I have done similar hackulations using the tools available to me to overcome the limitations of this and other brands of PLCs. All that really matters is it works. Make sure your add some comments to that ladder code before you save it off so you can remember what you did when you look at this a year from now. Good job! Joe T.
  5. When I opened this it says it was made with UniLogic v1.23.25. You need to update your UniLogic to v1.28.26 - this is what I saved it in and there have been some improvements to the Message Composer since your version. I edited your Message "test message" and embedded REAL data types with tag names T1 through T6. You already had the 20h spacers in there. Let me know if it works. I did not load and test it in a PLC, so I'll need you to report what happens with this code. Joe T. incubationSystemV4forum JT.ulpr
  6. I've always used Port 1 for OS updates. Any reason why you can't do this? Joe T.
  7. It looks like your delimiter is a space character (20h). You'll need to build your message to look for this. Post your code so we can see more. Joe T.
  8. You'll need the Ethernet port. If you have a router visible from the outside Internet you'll need to port forward port 20256 in the router to the IP address of the Samba. The USB port is for programming only. It's doesn't have the capability to be a master and drive an external device such as a WiFi stick. Joe T.
  9. The V700 has a different way of interfacing with Ethernet, as it has 8 sockets instead of the V1040's four. Open the Help and search for V700 - the first topic is how the Ethernet is different. You'll have to change how you monitor socket status. Take a look at this and let us know what questions you have. Joe T.
  10. Start simple. 1. Delete the "Coils Periodic" entries in your Modbus table. I'm not sure what this is doing. 2. In your "Registers Periodic" table, enter 43 as the address for your Speed tag, delete your Temperature SP entry, and add an INT tag for Motor reading address 34. Note that this will return the number 0 or 1, and you'll have to do something in your logic to change that into a coil for your display. 3. We'll worry about writing to the drive after you get this working. Post your code if you have more questions. If we can look at your program we can see things that aren't on the screen shots. Joe T.
  11. Be careful what you wish for.... Joe T.
  12. A "telegram" in SiemensSpeak is just a Modbus data packet. The UniStream will handle that for you. I think you're confusing coils and registers. The table you posted lists registers. A coil is a single bit and typically has an address of 0000x, while registers are numbers and have the format 4000x. FC 3 reads a register. FC 6 writes a value. Once again, the table in the UniStream will handle selecting the proper Function Code. Tell us exactly what you want to read and write from/to the VFD. I'm not sure what you mean by "ECHO" - does that mean write from the PLC to the VFD? Joe T.
  13. Looks like the USB-COMi-M is replaced by this- http://www.vscom.de/usb-com-plus-mini.html I don't, either. Whatever you find needs to say "isolated" somewhere. Joe T.
  14. Thank you for posting your code. There are many example projects that install with VisiLogic that will be helpful to you. Look at Help->Examples to see what's there. 1. In the Master you are continually calling the Modbus commands, which is like beating a kid with a stick to do the dishes. Every time he goes to pick up the brush you whack him with the stick again and knock it out of his hands. Use a positive transition and check the busy bit before calling the command, which will trigger it only once. 2. Command 5 (Force Coil) is exactly that; force the bit to a given state. The bit in the Slave doesn't turn itself off again unless you write logic to make it so. 3. Using SB1 (Always 1) when turning a bit on remotely and SB0 (Always 0) is more clear when you're trying to drive the bit to a known state. 4. There's no logic in the Slave to actually control O5. I added logic to drive the bit and to act on the bits from the Master to control the output and then turn themselves off after a short time. You've got to truly think like the PLC - it will only do what you tell it. I followed your lead with the separate ON and OFF bits in the attached files, but a better solution is to modify one bit in the Master and send that when either button is pressed. I'll leave this to you as an exercise. Your baud rate is pretty high, too, at 115200. I'd dial it down to 19200 on both sides. Load these programs into your PLCs and let us know what happens. Joe T. SLAVEMODBUSTEST JT.vlp MASTERMODBUSTEST JT.vlp
×
×
  • Create New...