The modbus master query examples will be good ones to use. But you are absolutely going to need some kind of information from the manufacturer of the device describing the address number and meaning of all of their modbus registers. If they don't have it in some sort of general user's guide, then you need to see if they have some advanced manual or communications manual as a supplement. If not, you will need to contact them.
Well, the program allows you to look at many registers at once (Setup->Read/Write Definition) and then allow you to see what is changing when you take actions.
I had a PLC with many inputs and outputs, and no reference to what coils and registers they used. So I used this software to view many channels at once, and just started writing values and seeing what changed on the PLC and then just wired some inputs and saw what registers changed. Not sure how much is in your device or if this is possible, but it was trial and error that took quite a while. It is always ideal to just track down the manual for the device you are using, and I suggest you try your best to acquire that.
I downloaded the Modbus Poll and tried to connect to my device. I am getting a timeout error. This is the same error I get in labview when i connect to my device. Do you by chance know what the problem is? thanks
also could the fact that my serial cable is 200ft long contribute to this problem? thanks
Are you using RS-232 or RS-485?
If you are using RS-232, then yes, you definitely have a problem as it is only supposed to be good for about 50 feet. This could be a bit more or less depending upon your baud rate. If you are using RS-485, you should be okay as that should be good for about 4000 feet (also depending on baud rate)
When I have a MODBUS communication Issue the first thing I check is that the device and the modbus communication vis on the PC side are set to the same rate. By default the vi are probably 9800 and I have found that modbus devices many times have been set to 19200 Baud. This has cost me many hours so I always check this early in the debug process. I even have written an open vi that will test a querry at several popular communication speeds to autoset the rate (ie the rate with a correct querry is the BAUD I want).