modbus not working on ML1400

TimD

Lifetime Supporting Member
Join Date
Aug 2007
Location
New Hampshire
Posts
235
Hi All,

I have modbus comms working to many devices using ML1400's and the NC01 adapter.

I have one flowmeter in particular from Toshiba that refuses to talk to my 1400, but talks to Modscan on my laptop just fine.

Of course, my port settings are set up OK on both PLC and Logix end. I'm reading an integer value from register 40001 just fine in Modscan, but when hooked up to PLC, reading nothing but time outs.

I've swapped A and B and changed all sorts of things in my MSG block and port settings to no avail.

I've never had this much trouble communicating to a device before. Toshiba tech recommends me buying a RedLion converter box of some type to help get the signal into the ML1400... I am not sure of that...

Anyone have any ideas?

Thanks!
 
Error is simply "Message timed out in local processor"

I will try simulating a slave device now.
 
I tried the Modbus simulator, however, I only have a USB to RS485 adapter and the software seems to support DF1/232 serial so I'm not getting any results back. I can't see where to simulate a node address and the help says nothing. So, trying a "1" is no help.

My Modscan and USB adapter act as a Master and read data from the flowemeter just fine, however, the ML1400 refuses to read anything no matter what I try. It's frustrating.
 
Last edited:
Check out the link posted by sfindley above. The link I posted is to a modbus slave simulator.

post your file if you can.
 
Yes, I looked at the post, and my channel settings are correct (No Handshaking)

My file is a simple two line program, a timer (TON) that cycles every 4 seconds and triggers a MSG read.

The MSG block is set up like:
Channel: 0 (Internal)
Modbus Command: 03
Data Table Address: N7:1
Size in Elements: 1
Data: 16bit

Message Timeout: 2
MB Data Address: 1
Slave Node Address: 2
Modbus Address: 40001

..keep in mind I have been changing things to see what sticks like 16 or 32 bit and number of integers, etc... Yes, the slave node address is 2

And I've got VFDs on different ML1400 Processors talking modbus just fine...
 
Last edited:
I had the exact same problem..check out the settings for your ML1400 and make sure you have "no handshake" like the description in the thread I posted
 

Similar Topics

hi all i test the HC900 modbus (master) read function by connecting s1 port to my notebook with rs485 usb converter. in the HCD, i monitor the...
Replies
1
Views
4,158
Is there a way to address floating point variables with Modbus/TCP? FYI: Using Quantum 434 12U (Unity Pro XL 3)
Replies
6
Views
3,944
Hi all, Currently having trouble getting a speed reference to write over modbus to an Omron M1... I can successfully write a run command and...
Replies
2
Views
36
Apologies for not being the best IDEC programmer. I recently was doing some inspections on a site that had 3 FC6A IDEC processors. The issue is...
Replies
0
Views
51
Good morning fellow sea captains and wizards, I am being asked to do the above and obtain 4 values from each slave, I know about the MRX and MWX...
Replies
26
Views
323
Back
Top Bottom