Jump to content

Damian

UniStream & UniLogic Beta
  • Posts

    534
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by Damian

  1. Can you please explain what is meant by "cascade control mode"? On Comm 2. Are all devices RS485? Or is one device only RS422? Also an option to consider, getting a CAN to serial converter since it does not sound like you are using your CAN port.
  2. Hi Tim, Sorry, I was going from memory and confused SB7 with SB15. Realized it as soon as I hit send. One thing I have noticed in the past. The very first time you initiate a Modbus function it seems to take appreciably longer for it to process than normal. After the first process, it then seems to be consistent. I wonder if your first call of the RHR or PHR is taking over 100ms and stuffing everything up thereafter.
  3. you should not need to add the modbus offset 40000 or 400000 to the Red Lion. Just use the address direclty. The largest modbus mapping address is under FFFF, which is 65535. So you should be fine
  4. Hi Tim, A curiosity with the first PIC you have on your post. You are using the N/C of SB7 on your RHR function. I would expect the N/C of a pulse to literally be on for most of the 100ms and pulse off for a very short amount of time (say 2.5ms). Or more clearly, it seems your are sending your RHR and your PHR almost simultaneoulsy. Emil .... Cara ....... It would be nice if the software gurus put some sort of graphic indicator on the function blocks themselves that tip you off if the function is of the type that should only be initiated with a transition. Maybe like a little pulse mark on the input. Would save a lot of confusion, especially for new users. D DOH!!! sorry .... I got SB7 confused with SB15
  5. Cara, thanks for the tip! and the rest............... This will give you close to max comm speed as it relies purely on handshaking and does not utilize timers.
  6. Oh NO! Anything but cute!! Will it have any new features or will it strictly be a V570 with a bigger screen? Need a BETA tester??
  7. Emil, your too rigid! Star topology can work just fine if all the nodes are very close together and baud rates are not that high. I've done this a few times in the past to avoid trying to daisy chain RJ45 or RJ11 connectors that don't repeat the signals on another set of pins. Generally if your devices are all mounted next to each other on the same panel and each leg is kept to a couple feet max (which is a common situation) you will not experience issues.
  8. oops, sorry. Didn't notice the distances before. Across slave 1 and across slave 9.
  9. Are you running your cable from drive to drive in series, or are you branching out to all the slaves from the master in a starlike topology? If you have all the devices linked "in line" then you need just to have the resistors at the extreme ends. If you are doing a star topology (generally not recommended) then it can get complicated. Are these devices all short runs, or are they long distances?
  10. or maybe not ........... looks as though I have uploaded my quota for today
  11. I use this structure for all my modbus comm routines (RTU or TCP) and have never had issues Looks like I will have to continue the rest in another reply. 500k limit
  12. As a general rule of thumb, RS232 is not recommended over 50 feet.
  13. Windows XP Pro SP3 (All the latest security updates) Dell Precision (With Intel Centrino Duo) Visilogic 8.6.1 Kaspersky Antivirus
  14. Network 2: Split this up into two nets. It is bad practice to have multiple rungs in one net. Try removing the "underscore" from the PLC name (just to rule it out) Regarding SI145, Unitronics has some documentation missing. Status 14 also means initialized to TCP master Maybe better not to make MB5 a set coil. This only allows you to try the connection once. Make sure the Device ID of your slave device is set to 2 (as is in your config block) Try using socket 2. It's defaults more closely match what you are doing. Where is your RHR function??? You should post your Slave code as well. When you are viewing Online are SB142 and SB143 on?
  15. If I understand you correctly, I think the answer to your question is you will lose any precision after the decimal place. To maintain the precision to the left of the decimal, take care to perform the division last.
  16. to keep the precision while still using Long Integers, you could also just multiply the first ML by your precision (ie, 10000) prior to dividing.
  17. Sounds like you had a ground loop that the screened cable may be squelching. How close is the switch to both devices?
  18. Why wouldn't "elaspsed time" have anything to do with the RTC?? When the start condition happens store the RTC in a variable. Now have a Subtraction function block that takes the current value of the RTC, subtracts the Start value, and places into another variable (your elapsed time). That is the most accurate elasped time you will be able to get.
  19. Hi Emil, Are we still looking good for the schedule on this?
  20. Sounds like you should consider creating a loop and using indirect addressing. If you have to do virtually the same thing 100 times over than it is to your benefit to organize it such that you can just re-use the same block of code as if it were a function.
  21. Hi Emil, I disagree with you on this one. I like short simple nets as well, but I often find myself constantly creating the dreaded "S-loop" to be able to be able to finish one simple train of logic. If Writing one rung per network is good practice (as most of us probably agree), it would seem that Visilogic has too much vertical network area in proportion to the horizontal area. Even with the smallest function blocks, I can only have three in series and still have enough room at the right to place a coil without having to make a loop. Yet, Visilogic leaves room to create up to six parallel rungs in one network all tall enough to contain function blocks. As a side note. Most software dynamically modify the wires for you as you build code. RSLogix as an example. Once your net gets too wide it automatically does the S-curve for you. This tends to be much more efficient to program from a "development time" standpoint. I feel like I waste a lot of time in Visilogic drawing wires as if I were using Autocad, instead of just entering logic. Maybe something R&D can chew on for the "next generation". In this day and age, if something that can be automated has to be performed manually, we're just wasting time and money.
  22. Could you post a pic of the before and after so we can understand what you mean?
  23. Have you done a cross reference to check if you accidently created a duplicate coil elsewhere?
  24. Hi Frosty, Glad to hear you found a workaround. For future reference, the value you were using with a PNP output was too big. This is a snippet from the Uni documentation: You can use certain outputs as High-speed Outputs (HSO) via PWM (Pulse Width Modulation). When you select a High Speed Output in the Hardware, the Select Operand and Address dialog box appears three successive times, allowing you to link operands for the following values: Duty Cycle The ratio of the "on" period of a cycle to the total cycle period. This value may be from 0-1000, and is expressed as a percentage. If, for example, the constant 750 is stored into the Duty Cycle operand, the duty cycle is equal to 75.0% This means that the pulse will hold a positive state during 75.0% of the total cycle. Frequency (F) Note that F=1/T, where T is the duration time of a complete cycle. Frequency settings differ from npn to pnp output type. npn: You can use a value of 0, or a value from 8-50000Hz ( 50kHz). pnp: You can use a value of 0, or a value from 8-2000HZ. Other frequency values are not supported.
×
×
  • Create New...