Search the Community

Showing results for tags 'modbus'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • DAQFactory
    • Alarming
    • Channels, Conversions and general data acquisition
    • Graphing
    • Logging
    • Modbus
    • Networking: web, email, FTP etc.
    • PID
    • Screen Components and User Interface
    • Sequences and scripting
    • Serial Communications
    • General DAQFactory
    • DAQFactory and the LabJack
    • DAQFactory Express
    • DAQConnect
    • DAQFactory New Feature Requests
    • The DAQFactory Guru's Articles
    • DAQFactory Newletters

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 10 results

  1. Hi, I am having some issues with Modbus and a temp controller. I think I am ok with daqfactory but very new to modbus. In the past I have used my own comms protocol over rs232 but now trying modbus over rs485. I have an omron K3SC-10 usb to rs485 converter and used this with a Yokogawa temperature controller absolutely fine. I used Modbus ASCII, found the registers in the manual and used the standard daqfactory commands to read holding S16 for each register. Surprisingly easy! I couldnt get hold of another yokogawa temp controller so bought an equivalent Omron E5CC model. Its running Modbus RTU and I have SD and RD traffic so everything is working comms wise. The manual wasn't so easy to understand so this took a while. My problem is that I just get modbus timeouts when I try to read any registers, sometimes I got some random (to me) data but then it stopped. I think this is because it doesn't recognise the commands I am sending? I found the quickmod program that you made (screenshot attached) and i can see some of the data I want: 248 is 24.8 degrees C! I don't really understand the tag number and number of points? Is tag the register? Is number of points trying to read an array or a range of registers?? I'm very confused but think I am close. I've attached the temp controller comms manual. I don't really understand about 2 or 4 byte modes and if the registers are in hex or what!? I think I have got as far as I can now using trial and error and very basic understanding but now maybe I need to actually understand what's going on! I'm ok with rs232 because you send it a command and it sends something back, simple conversation. I think modbus is the same, but I don't really understand the conversation between devices and the upper, GUI level isn't working for me. Maybe it's simple and you can explain what I am missing or if you have a suggestion for some easy learning material for me? I need to read the temperature controller PV and setpoint and write setpoints and PID values. Cheers Steve E5_C_CommunicationsManual_EN_201404_H175-E1-08 (1).pdf
  2. I’m looking into the best way to disable a modbus device (multi-function power meter) to prevent timeout errors and data reading issues. Currently when a power meter is disconnected (circuit switched out) the data being pulled from other devices displays incorrectly. What I’m looking to do is condition a device being “enabled” by a digital input from the distributed I/O. So effectively when a power meter is shut down it doesn’t effect any other data? Is this possible? thanks. NHL
  3. Hi there, Thanks for the support i received in the past, I have a few years of positive experience with azeotech. In my current project i deal with a modbus device. Reading the registers works ok, I have a channel for each register I want to read and have them all set at 0.1s interval. Now, I also need to set some registers and I made a small sequence for that. the button ' zero displacement' invokes this sequence. the registers I want to set all have their own channel as well. This works but only sometimes... with reading every 0.1s I get lots of ' port locked' errors. I quess that i need to pauze the reading for a moment to make room on the bus for setting the appropriate registers. Could you give me a hint on how to solve these issues? Thanks, Koen for legacy reasons, I run this file in DAQfactory 5.87c DirksonWTB_22kN_v1.ctl
  4. Hello, I have been running Emotron VFD trough modbus with DAQFactory. All the basic reading and writing is working just fine. Now I´m having a problem converting Emotron floating point format to correct decimal values. I can read the value from 0 to 32767 with the U16 format but after that I don´t know how to continue reading the value. I need to read this value from 0 to 200000. Can I make this work trough "channels" ? Part of the Emotron manual attached. emotron.pdf
  5. I have a project with multiple modbus channels. I have timings and events for those channels, while I monitor, I can see Tx and Rx for all the modbus ID's but the channel is not reading thus not collecting data, not executing event code as well as the UI component displaying that channel is not getting updated, until I force read it using channel.read('channel_X'). I am facing the same issue with 2 recent project. I am currently using a sequence with While loop to Force read all the channels. Any help would be much appreciated. Thanks!!
  6. effman

    Modbus pooling

    I have to pool several different modbus RTU devices on single rs485 line. Baud rate is 115200. Pool time must be az short az possible. Is there any possibility to get info about finished modbus transfer? I mean some property to check each 25 ms to make the pooling as fast as possible? Or any other way to avoid delay() between modbus calls? Thank you in advance for support Tibor
  7. I have just started using DAQFactory and now DAQFactory Express (both Release 17.1 Build 2309) for monitoring a temperature controller via RS485/Modbus. I am impressed with DAQFactory (thanks to the developers for such a great product) and am slowly getting an understanding of how to use it after lots of attempts, reading and searching of the forum. I have been able to configure a new RS485/Modbus device in DAQFactory and successfully connect using a USB-Serial adapter to a Shimaden SRS11A temperature controller and retrieve the current temperature value. I have also configured a single channel and a logging set which work well. I am trying to add some error handling to manage serial port errors on the RS485/Modbus connection such as when the RS485/Modbus device is powered off, the USB-Serial adapter is not plugged into the computer, or a RS485/Modbus timeout. I am using the OnAlert() function to deal with these types of errors as they are not caught by using the Try/Catch approach in scripts/sequences. This is catching errors/alerts OK except I am observing inconsistent behaviour. I have an auto-start sequence called Main which sets the Channel timing to zero then does a device...initcomm() to see if communication is working. When I setup a test scenario where the USB-serial adapter is connected but the RS485/Modbus device is powered off, I sometimes get a timeout error, no error or an occasional error where DAQFactory cannot load the driver TriLogi.dll (I am not using this driver, my device is using the supplied ModbusRTU one). The fault is probably something I have or haven't done but I was wondering whether anyone has seen something like this before? Any help or suggestions are welcome. Thanks Paul
  8. I am trying to read register value from Banner DXM 100 controller. I created COM port serial connection- 19200,8, none, 1, 1000ms. When I am trying to read register 2 using Channel # as 2(also tried 40003), I am getting P-ModbusRTU 0010: Timeout error on every read and P-ModbusRTU 0014: ID Mismatch error after several reads. I am trying to read every 2 seconds with offset 0. Port monitor and channel details look something like the image below: I have tried 'n number of ways to read the register value, by changing- modbus ID(on the device and Daqfactory), baud rate, channel#, timing, offset, I/O type, device timeout(to 2000ms) etc. but no luck. Has someone encountered such issue before and can help me? Thanks!!
  9. Hi Guru, I am currently working on the Murphy 467 Controller to achieve multiple scheduling for my pumps. Controller: https://www.fwmurphy.com/uploaded/documents/pdfs/obsolete/00-02-0672.pdf http://irrigationautomation.iassys.com/wp-content/uploads/2014/07/Manual_467_IAS.pdf I am getting the following error when I try to run the scheduling part. Timeout and Port locked error are throwing up in my log. I am currently a new DaqFactory user. Let me know if I can assist you with any other information. Thanks!
  10. Hi, I'm having some issues I think with a conflict between 2 devices. I thought it was an electrical issue but i am now pretty sure it is daqfactory. I have a usb to rs232 connected to a flow controller and use a custom protocol to poll it via the virtual comm port as per the instructions in the manual, driven by 1 channel at a timing of 1 sec and add the parsed data to channels. This works great. I also have an arduino chip built into my embedded computer that is running a modbus protocol (although the chip is built in to the board, i think it also runs a usb to serial adapter chip). This also works great and i use a sequence to read some registers and put them in channels. To write to some registers i just use the modbus commands on the channel and set the channel. The problem I am having is that if i switch some valves on/off by setting the registers, sometimes the RS232 adapter to the flow controller will drop out and i have to unplug in order to then initcom(). I get a timing lag error. I think what is happening is maybe if the writing to the modbus registers happens at the same time as the channel timing talking to the flow controller, the flow controller comm port gets locked up somehow? I'm not sure if this is an accurate diagnosis. The modbus read doesn't seem to be affected but it is in a sequence with a try catch. I tried reading the flow controller in the sequence with the modbus, with both reads from the modbus and the flow controller on a 1 sec loop with 0.5 sec offset. They both have try catch and the data comes in fine. But writing rapidly to the modbus I can still get the flow controller to drop out. I was thinking to move the writing to modbus into the sequence also, so I can be sure it never sends data at the same time as the reads but I'm wondering if i'm going about this all wrong!? I don't understand how the two different devices can affect each other like this as it's a different device, different protocols and different ports??? Any ideas would be great Cheers