Hi,
I am working with ESP 32 and 5.1.2 IDF , I am Communicating with 3 separate Mod slaves in RTU mode.
I am successfully reading first 7 values CID 0 to 6 and CID 8. But I am having trouble reading CID 7 & 9.
I (25838) MASTER_TEST: Characteristic #0 value = 40F3DB19 read successful.
I (26288) MASTER_TEST: Characteristic #1 value = 96552C6B read successful.
I (26738) MASTER_TEST: Characteristic #2 value = D7480784 read successful.
I (27188) MASTER_TEST: Characteristic #3 value = D7480002 read successful.
I (27638) MASTER_TEST: Characteristic #4 value = 00000000 read successful.
I (28118) MASTER_TEST: Characteristic #5 value = 441A3BE3 read successful.
I (28618) MASTER_TEST: Characteristic #6 value = 441A3BE3 read successful.
E (29018) MB_CONTROLLER_MASTER: mbc_serial_master_get_parameter: The cid(6) not found in the data dictionary.
E (29018) MB_CONTROLLER_MASTER: mbc_master_get_parameter(73): Master get parameter failure, error=(0x102) (ESP_ERR_INVALID_ARG).
E (29028) MASTER_TEST: Characteristic #7 () read fail, err = 0x102 (ESP_ERR_INVALID_ARG).
I (29458) MASTER_TEST: Characteristic #8 value = 441A0CB0 read successful.
E (29858) MB_CONTROLLER_MASTER: mbc_serial_master_get_parameter: The cid(6) not found in the data dictionary.
E (29858) MB_CONTROLLER_MASTER: mbc_master_get_parameter(73): Master get parameter failure, error=(0x102) (ESP_ERR_INVALID_ARG).
E (29868) MASTER_TEST: Characteristic #9 () read fail, err = 0x102 (ESP_ERR_INVALID_ARG).
I can read the specific values separately one by one if CID is 0
I am New to ESP , please advise!!
Modbus Cid error
-
- Posts: 211
- Joined: Fri Feb 01, 2019 4:02 pm
- Contact:
Re: Modbus Cid error
Hi @manas_frinso ,
I can just guess why it does not work on your side. I think it is just data dictionary configuration issue. Unfortunately, the information you provide is not enough to identify your issue. Please provide your Modbus r/w code and also data dictionary.
Note:
The CID order should be from 0 - last number without gaps in between. Please check.
I can just guess why it does not work on your side. I think it is just data dictionary configuration issue. Unfortunately, the information you provide is not enough to identify your issue. Please provide your Modbus r/w code and also data dictionary.
Note:
The CID order should be from 0 - last number without gaps in between. Please check.
Who is online
Users browsing this forum: Google [Bot] and 335 guests