4652 views|7 replies

564

Posts

0

Resources
The OP
 

I have one or two communication questions. [Copy link]

1. Can I read the values of multiple discontinuous addresses during a modbus read operation? 2. The communication speed is 1Mbps, the carrier cycle is 8K, and 7 words can be sent per carrier cycle. The chip uses SSI (serial synchronous interface) for communication. Is there a related module that supports conversion to USB?

This post is from MCU

Latest reply

If you use Modbus, you can only follow the ModBus specification. No matter you have one master and several slaves, you should treat it as one master and multiple slaves. If your system is just one master and one slave and they are all designed by yourself, and do not need to be compatible with other ModBus devices, then there is no need to use ModBus.  Details Published on 2017-12-15 16:11
 

1w

Posts

142

Resources
2
 
ModBus is a one-master-multiple-slave network protocol. Each terminal corresponds to an address. Of course, it can only communicate with one terminal node at a time. Only the broadcast mode is one-to-many for the entire network, but that is not "reading". As for the USB support issue, it depends on your serial port hardware. If it meets the standard serial port (RS232), it will have it, otherwise it will not.
This post is from MCU

Comments

我没说明白,在一主一从的情况下,modbus是否会支持随机地址的寄存器访问? 比如正常通信格式:头码+从机地址码+寄存器起始地址+寄存器数量+校验 现在换为:头码+从机地址码+寄存器起始地址1++寄存器起始地址4+寄  Details Published on 2017-12-14 19:42
 
Personal signature上传了一些书籍资料,也许有你想要的:https://download.eeworld.com.cn/user/chunyang
 

4005

Posts

0

Resources
3
 
No, non-continuous addresses can only be read multiple times. The 03 function has only one starting address, so it is impossible to support non-continuous addresses. I don't know that
This post is from MCU

Comments

03支持连续操作,但是不知道支不支持任意多个地址读操作? 如果自己定义通信协议的话,是否可以满足上述要求?  Details Published on 2017-12-14 19:43
 
 
 

564

Posts

0

Resources
4
 
chunyang posted on 2017-12-14 11:13 ModBus is a one-master-multiple-slave network protocol. Each terminal corresponds to an address. Of course, it can only communicate with one terminal node at a time. Only the broadcast mode is one-to-many...
I didn't explain clearly, in the case of one master and one slave, will ModBus support register access with random addresses? For example, the normal communication format: header code + slave address code + register start address + register number + checksum is now changed to: header code + slave address code + register start address 1++register start address 4+register start address 7+register number + checksum. Is it supported?
This post is from MCU

Comments

Explicitly not. The 03 read instruction has a clear format and is standardized.  Details Published on 2017-12-15 16:11
Explicitly not. The 03 read instruction has a clear format and is standardized.  Details Published on 2017-12-15 10:22
 
 
 

564

Posts

0

Resources
5
 
huo_hu posted on 2017-12-14 11:28 No, non-continuous addresses can only be read multiple times. The 03 function has only one starting address, so it is impossible to support non-continuous addresses. I don't know...
03 supports continuous operation, but I don't know if it supports arbitrary multiple address read operations? If I define the communication protocol myself, can it meet the above requirements?
This post is from MCU

Comments

You can do this yourself, but it cannot be called modbus  Details Published on 2017-12-15 10:24
 
 
 

4005

Posts

0

Resources
6
 
This post was last edited by huo_hu on 2017-12-15 10:26
sanhuasr posted on 2017-12-14 19:42 I didn't make it clear, in the case of one master and one slave, will modbus support register access with random addresses? For example, the normal communication format is: header code + slave...
Clearly no, the 03 read instruction has a fixed format, which is a national standard, you can look it up.
This post is from MCU
 
 
 

4005

Posts

0

Resources
7
 
sanhuasr posted on 2017-12-14 19:43 03 supports continuous operation, but I don't know if it supports arbitrary multiple address read operations? If you define the communication protocol yourself, can it meet the above requirements?
You can do this yourself, but it cannot be called modbus
This post is from MCU
 
 
 

1w

Posts

142

Resources
8
 
sanhuasr posted on 2017-12-14 19:42 I didn't make it clear, in the case of one master and one slave, will modbus support register access with random addresses? For example, the normal communication format is: header code + slave...
If you use Modbus, you can only follow the ModBus specification. No matter you have one master and several slaves, you should treat it as one master and multiple slaves. If your system is just one master and one slave and they are all designed by yourself, and do not need to be compatible with other ModBus devices, then there is no need to use ModBus.
This post is from MCU
 
Personal signature上传了一些书籍资料,也许有你想要的:https://download.eeworld.com.cn/user/chunyang
 
 

Guess Your Favourite
Just looking around
Find a datasheet?

EEWorld Datasheet Technical Support

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews

Room 1530, Zhongguancun MOOC Times Building, Block B, 18 Zhongguancun Street, Haidian District, Beijing 100190, China Tel:(010)82350740 Postcode:100190

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京B2-20211791 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号
快速回复 返回顶部 Return list