Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 03/24/2018 in all areas

  1. 1 point
    Download a blank program, cycle power, and then try the USB port. If you can communicate with the PLC it's OK. If you can't it's not. Joe T.
  2. 1 point
    Perhaps you have port numbers confused? Without seeing your program I can't tell. Your exercise (!) is to put the original comms element(s) relating to just one comm setting back into your program and see which lot upsets things. This should point you to your answer. Please let us know! cheers, Aus
  3. 1 point
    Further to my comment above about fundamental comms settings in your user program, remove all comms type elements from your program as a test. Download and see what happens. cheers, Aus
  4. 1 point
    How much does this little gem sell for? Joe T.
  5. 1 point
    Yes, but will giving the code a dose of Dimetapp make it go to sleep and behave? Joe T.
  6. 1 point
    I gave up on the Decimal formats in the Protocol block long ago. They're just not consistent in their behavior, as you've seen. I catch the whole string in a Stream variable and then use the String functions to find locators such as your "kPaa" string. Once you find a pointer to that location you can search backwards for the space, which will give you your numeric string length. Then extract the numeric string to their own MIs and convert them to a number using the ASCII=>NUM function, which works quite well. This sounds more complicated than it is. The nice thing is you can examine the output of your string manipulation code at each step. I have found it to be way more reliable. Joe T.
  7. 1 point
    According to tech support, there was a bug in Visilogic 9.8.31 with the Com FB that they fixed in 9.8.64. I got the explanation that it was not possible to choose RS485 in the older version but that it now is fixed. It seems as if the bug was present in 9.8.64. I tried the same thing with 9.8.65, and now it is again possible to choose RS485. Also programs made in version 64 that showed a grayed out RS232 com init setting, do show RS485 again in version 65. /Peter
  8. 1 point
    Joe, This has been bothering me for a while, so I dug a little deeper. I found the actual problem I was having was that I had a column with Boolean data type labeled as a machine Mode On/Off. The front slash character was the culprit. The warning states which characters may be used. The front slash is not one of them. Looking at your table, I see #, and parentheses ( ), all of which are not allowed. When I shortened all of my column names to 8 characters or less, the front slash apparently got deleted when I did that, and the warning went away. Column length had nothing to do with it. Sorry I led you astray.
  9. 1 point
    I agree with Joe and am glad to see him asking the Creators. However, if it is always 5 digits you could cheat a little bit and pretend the decimal point you could do at the "thousands mark" is a comma. Just a little bit of division/maths beforehand. Even having the dec point might be a good enough separator for now, giving that little bit of extra clarity. Depends what country you are in. I quote from something copied from a site and have underlined the important bit: Great Britain and the United States are two of the few places in the world that use a period to indicate the decimal place. Many other countries use a comma instead. The decimal separator is also called the radix character. Likewise, while the U.K. and U.S. use a comma to separate groups of thousands, many other countries use a period instead, and some countries separate thousands groups with a thin space. In Aus it is getting hard to keep up with constantly changing norms, seemingly dictated by what is PC or trendy at the time. Used to be commas, but supposedly it is now the thin space. cheers, Aus
  10. 1 point
    I made a CNC router for my son. I would not look at a PLC for that task. Take a look at the Mach card and Mach 4 software is about $200. You'll have a easy to program machine without the pain.
  11. 1 point
    Break your logic up into two rungs. I have regularly seen problems with HMI calls interfering with the rest of the logic in a single ladder rung. There is no reason not to place the HMI call in the next rung, also preceded by MB151.
  12. 1 point
    I haven't looked at your program. Something FYI. In case you don't know, Visilogic has an annoying quirk....when in online mode it shows elements of an uncalled sub in red (powered). This can be very confusing. There are many solutions to this, the best I know of from another forum member (can't remember who...sorry) was to set up a simple count at the top of each sub. If the count is progessing, the sub is active. cheers, Aus
  13. 1 point
    UPDATE: I found that SI104 (socket 1) was not set in my SAMBA program, guess I'm thinking of some of the V430's I had tried setting SI 10x values. I set power up value D#10000 for SI104 (10 sec). I'll see how that works out. bad thing is the socket freeze doesn't happen often (can be weeks or months). For some reason I had the impression that SI101 thru SI110 did that for you: SI 103 TCP/IP Connection Keep Alive (Socket 0) Units of 100 msec Note- When value is ‘0’, the function is disabled Enables the PLC to disconnect if there is no communication from the connected device. When TCP/IP connection is established (SI 145-148 = 6) check data transport (SDW 14 – 21). If no data transport occurred during the defined time – perform ‘Socket Init’. Data Transport counter is SDW 38
  14. 1 point
    Talked to Dan at US tech support - he suggested SD File Utilities -> File Status function block The "A" output bit MB 39 does what I need. I just call this function before I write the data line to see if I have to call a another Write Line for the header first. Joe T.
  15. 1 point
    Looked at the data sheets - all these are RS232 devices only so you'll need a port multiplexer- Google "RS232 port multiplexer". You're going to have to add code to select which port you're using. I'd also add an Ethernet card so you use the other serial port. The tricky thing is going to be your barcode reader. It just returns a string of the barcode and doesn't tell you which port it came from. This is another reason to use both ports instead of one - you'll know from the scan block which reader triggered it. Since you are using a dedicated output device (printer) and a dedicated input device (scanner) it may be possible using both ports to only connect the TX line to the printer and the RX line to the scanner using custom cables, one on port 1 and one on port 2. Use the Ethernet port for programming. This is not a trivial application. Joe T.
  16. 1 point
    There are multiple ways to do this, but there's not a simple System Bit to disable the touchscreen. Either create a blank HMI screen with no buttons that displays during the time you want to disallow button presses, or use the disable bit on all buttons that are on screen and activate that bit during the disallow time. I will often have functions that are only available with proper login and will hide or disable elements when the user isn't logged in.
  17. 1 point
    I couldn't pass this up. Joe T.
  18. 1 point
    Looks like this is always the case with energy meters. You use "Struct" block under Vector -> Struct for merging those two registers into a float. There is an explanation for struct block in help file. After that use math function blocks for floats to extract the values if you need them converted to int.
  19. 1 point
    Cool. I've been round and round with the Server/Client quandary in my Modbus TCP adventures in figuring out Master and Slave. One way works. The other doesn't. Joe T.
  20. 1 point
    That is the official Unitronics USB->serial converter available from your distributor. You can use any converter that has the Prolific PL2303 chipset. A bit of Unitronics history - when the V570 first came out it had that USB port on it covered by a sticker. It was supposed to be supported by a future Visilogic release but that never happened for that particular hardware revision. Joe T.
  21. 1 point
    Hi Ljuba; See also my response for the JAZZ. In Visilogic, Right click on the display, select fonts and select a font to use. On the left there is Select All and all the characters will show up with Blue background ( the standard fonts will not allow a Select All, so add a new font ) Maybe there is an easier way, but this is what I have tried : On the screen, to display the 'special characters' (0x80 -0xFF -- 128-255) use the Display ASCII String and imbed the special characters in the MI Vector. The Programming display will not show them , but when downloaded, the characters will be displayed. ( note 2 characters per MI, enter as HEX because it is easier to decode the 2 chars in Hex than as an Integer) also the entry is invereted ab (0x6162) is entered as ba(0x6261) in the MI. 0x just means Hex Format This may not be the best solution, and if there are better solutions from others, please contribute. We all learn. Dan
  22. 1 point
    Hello Mick When working on your modbus example did you use a comport init and instead of using the powerup bit using another condition that forces the comport to a certain workmode? Try to go to info mode by keeping your finger on th screen until the info mode screen apears. Password to aces the items in infomode is 1111. When in infomode bring the plc in stop mode and then test if communication between visilogic and the samba is working again. In the visilogic communication menu you Will find an option to check the os from the samba. If the samba returns that info to visilogic the your communication is working again. Or you can try to watch the status of your logic online. In the helpfile from Visilogic you Will find more detailed information about info mode. Kind regards Henny
  23. 1 point
    I've frequently found that direct saving to virtual drives can be problematic, and not just with VisiLogic. Because of that, I always save locally then copy to the virtual drive later.
  24. 1 point
    If those are just single contacts and not really complex structures of them, I use this type of ordering them: You can easily combine several contacts in one parallel rung, but it does get fairly messy fairly quick... Good luck!
  25. 1 point
    This type of error is caused by a fault within the logic. An unlikely sequence of events or a faulty FB within the program could potentially cause this issue. To review the code within VisiLogic you can use the Ldr code to search for the subroutine that causes the issue. This feature can be found under the Edit menu, then selecting Find Subroutine by Ladder Error Code. This error may also be generated by a fault in the O/S. I would recommend either updating or reinstalling the operating system within the controller.
×