Jump to content

Jreese37

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Jreese37

  1. Well, in all fairness, I didn't know whether to shit or go blind either. Thanks a ton for your help with this, and everyone else who looked into it. I think I should be able to handle the rest of this project. I have 3 other sensors I want to read an analog signal on that same I/O.
  2. YAHTZEE!!! That program did it Joe!!! The only difference I can see right away is perhaps the Slave ID being 1 instead of 254 or 255? It is most certainly working with that program now :D. Thank you to everyone who took time out of their day to help troubleshoot this. I'm not the brightest crayon in the box, so lord knows I needed the help. Your help is truly appreciated!!! Oh, and the port # 503 for the local port?
  3. Here is the last configuration I came up with that would at least show the "connected" bit and allow Ethernet access from my PC. I get a 7, 4, and then 5 from MODBUS error status when trying to read the address. I'll keep trying to play with the start of vector to see if I can get lucky, but it appears to be the case that it just doesn't want to read. I had this set up with a Productivity, and Codesys PLC last night, and neither of them gave me any problems. I'm not necessarily ready to give up, but this is day three on this for me and it's driving me nuts! I appreciate all of the help from everyone who has looked into this with me. Modbus TCP Master.vlp
  4. They're all on the same subnet for sure. I was able to connect to the PLC on ethernet before I dropped this program in. I'm just now realizing that no matter what I do with this program, I can't reestablish ethernet coms PC to PLC, I have to use USB. I'm not necessarily sure what I did differently, but I started from scratch with the file Joe uploaded earlier, and set things one at a time to see which FB or INIT was bugging out, but this time, everything seems to be working but the connection to the remote IO device through modbus.
  5. Thanks for looking into this. Now that you mention it, I'm not able to connect over ethernet to the PLC from PC. I will look into this now. EDIT: Changed the TCP INIT to socket 2 and it connected?? https://drive.google.com/file/d/1wA1m4f5y2kEBsAVVMl19EIVy4T2lNRQh/view?usp=sharing
  6. Thanks for the prompt response, Flex727. So, after testing this file out, I never can get the IP to connect. I'm not sure what I could be doing wrong here. I've looked at this for hours today, and I'm not getting anywhere. I did go through and change the IP's and PLC name to what it should be. https://drive.google.com/file/d/1RxLUDuVis55Xx2KwndrEnFNHEZGELVv-/view?usp=sharing Does anyone happen to see what I'm doing wrong? Modbus TCP Master.vlp
  7. Thanks a lot for your time, Joe. I am only using one device as a slave, and at the end of the project, the goal is to not even need a switch in this panel. I only ever look to read values from the remote IO unit that I'm using. I hadn't yet encountered the connect/close FB in any of the documentation I had been looking over, thanks for including that with clear instructions. I'm a bit of a millennial and spoiled by the niceties of using autonomous configuration for things like this :D. I did some experimentation with the example files, and found that it wasn't quite what I needed, but wasn't sure why. Thanks for clarifying the difference in parameters between those models. I don't have access to this PLC currently, but I will this afternoon. I'm really jazzed to try this program out and see how it does. After working at this for a few days, I really appreciate the rapid response to my question and you taking the time to modify this file to show me what I was doing wrong. Could I ask you a couple of more questions just for curiosity's sake? This line in the comments says "Below, both Ethernet card initialization and MODBUS Configuration are done as Power-up tasks. Note that Socket 2 must be initialized, via the Socket Init FB, to function as a TCP Master. Network ID number MUST be 255!" I noticed that it is set to socket 3 in the demo file, and also set to client, along with the MODBUS IP CONFIG function block socket is set to 3. I had seen in some prior documentation that some were using different socket numbers there in the initialization rung. I was highly confused about how that could ever possibly work? Is that perhaps because they were using the USB port as MODBUS RTU coms potentially? According to this datasheet, am I using the correct MODBUS address to access the holding register that I can see in modscan? Turck TBEN-S2-4IOL I'm a bit confused as to how the hex conversion in Visilogic works, if I enter a 3 into the Start of vector box, and set to hex, it doesn't appear to be giving me the actual value for 3(0x0003.) Although I don't suspect this matters whether I enter it there as hex or decimal? Thanks again for your time, Joe. I appreciate your information and help.
  8. Hello, I'm looking at a small simple project with a Samba SM70-J. I'm running into quite an issue trying to figure out a modbus tcp connection. I'm able to see the device in modscan, and other PLC's as well. But I can't seem to get my configuration right in Visilogic. Would anyone happen to be available to help me troubleshoot this? The remote device is a Turck TBEN-S2-4IOL PLC is a Samba SM70-J with an ethernet adapter added. https://drive.google.com/file/d/1Zd_C7z2hyUnq0MS6XPUwR9KVwzaY_2A5/view?usp=sharing
×
×
  • Create New...