User Ratings

★★★★★
★★★★
★★★
★★
10
5
2
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • Simple and effective, as all software should be.
  • Hi, I have done some porting work on my macos and have getten some progress. Is there any way that i and merge my work to you great code?
    Reply from QModMaster
    Posted 2022-08-15
    Thanks a lot for your help. I've already merged your code to the default branch.
  • Very useful !!
  • Great! It's better if baudrate is editable.
  • Thank you for creating a useful tool. I wish I could copy the text in the Bus Monitor and ADU windows. It is my hope that you can freely copy and paste this content into a text editor.
  • RTU and TCP communicated with my device on the first or second try. Make sure your serial port configurations match.
  • Easy! Just downloaded and ran on windows 7 64 bit. Used COM4 fine at the first attempt.
  • No able to open comport other than default com port provided in application. I tried to give COM9, COM10, COM11 and it always ends up in error such as INFO 2017-06-03T20:41:51.322 ..\qModMaster\src\modbusadapter.cpp @ 39 "Connecting to Serial Port [COM10]..." ERROR 2017-06-03T20:41:51.322 ..\qModMaster\src\modbusadapter.cpp @ 50 Connection failed. Could not connect to serial port INFO 2017-06-03T20:41:51.322 ..\qModMaster\src\rawdatamodel.cpp @ 17 Raw Data Model Line = "Sys > 20:41:51:322 - Connecting to Serial Port [COM10]...Failed" , No of lines = 1 INFO 2017-06-03T20:42:30.593 ..\qModMaster\src\modbusadapter.cpp @ 39 "Connecting to Serial Port [COM10:]..." ERROR 2017-06-03T20:42:30.593 ..\qModMaster\src\modbusadapter.cpp @ 50 Connection failed. Could not connect to serial port INFO 2017-06-03T20:42:30.593 ..\qModMaster\src\rawdatamodel.cpp @ 17 Raw Data Model Line = "Sys > 20:42:30:593 - Connecting to Serial Port [COM10:]...Failed" , No of lines = 5
  • Userfriendly, works well except for one annoying bug... The TCP messages do not include the slave address, so this cannot work with modbus TCP gateway that had several slaves attached.
    1 user found this review helpful.
  • Sadly, the Windows GUI is unusable on a high-dpi display. Enabling and disabling scaling have no effect -- the controls are scaled properly, but are presumably positioned with hardcoded pixel counts -- they are too close together and can't be read. No obvious way to alert the developer.
  • Source code isn't available. qt.nokia.com/products is offline. Can you upload source code please?
  • Register on the site just to say thank you to the author! I got the device modbus-tcp to buggy implementation of tcp-ip, the device does not ping from windows xp, 7,8,8.1, but answered icmp sent from Linux and it gave hope to connect. tcpdump has shown that the device is properly considered in ip packet checksum. I spent 3 days in search of opportunities to set up the device, tried a lot of programs (modbuspoll etc.) until I found this program. And this program is able to read and write registers from the device!
  • This was the only Modbus Master that the TCP/IP protocol didn't hit my firewall. Even the OEM software couldn't get through! I think over time the features will improve but it's a great free program.
  • Very good so far. But there is a serious error in the "receive code" (at least for TCP): If 1 poll "times-out", but the response is still send by the slave later, the master will always be 1 packet "behind" and tell "illegal data". It will never process the additional (correct) 2nd packet while polling (it must be there, because transaction IDs are still in sync with wireshark). This makes the master unusable for slave-debugging.
  • I tried the QModMaster and see a very good alternative to comercial products. But I also see a lot of possibilities for improvement. Here my list of wishes: 1. Changeabgle scan rate from 10ms up to minutes 2. If function codes for register access are selected the number of register and not the number of coils should be selectable in toolbar 3. Support of functioncode 0x17 (read/write multiple registers, supported by libmodbus) 4. Scan rate, Slave ID and TCP Port should be changeable during scan mode (The current option to open more instances of the program is ok, but not effective for scanning a network) 5. RTU misses some baud rates: 300,600,14400, 128000, 250000 6. A delay time (0ms - minutes) between pools would be fine 7. Timeout setting directly in the toolbar 8. details on received slave exceptions
    1 user found this review helpful.
  • Great program. Wonderfully coded. Thanks a bunch.
  • Thanks for updates ;)
    1 user found this review helpful.
  • Previous
  • You're on page 1
  • Next