mutiple ar connect one io-device error #169
Labels
bug
Something isn't working
Comments
|
Thanks for your report, we will look into this. |
Closed
pyhys
pushed a commit
to pyhys/p-net
that referenced
this issue
Mar 17, 2021
CMSU and CMWRR should be per AR instead of per device. Implement modulediff when another AR owns a submodule. Verify that PPM data have been set for a submodule, regardless of owning AR. The output data frame ID from the PLC should be unique per device, not per AR. Adapt sample application to be able to handle multiple connections. Future work is needed for one input subslot to be able to send data to multiple PLCs. Closes rtlabs-com#131 Closes rtlabs-com#169
pyhys
pushed a commit
to pyhys/p-net
that referenced
this issue
Mar 24, 2021
CMSU and CMWRR should be per AR instead of per device. Implement modulediff when another AR owns a submodule. Verify that PPM data have been set for a submodule, regardless of owning AR. The output data frame ID from the PLC should be unique per device, not per AR. Adapt sample application to be able to handle multiple connections. Future work is needed for one input subslot to be able to send data to multiple PLCs. Closes rtlabs-com#131 Closes rtlabs-com#169
pyhys
pushed a commit
to pyhys/p-net
that referenced
this issue
Mar 24, 2021
CMSU and CMWRR should be per AR instead of per device. Implement modulediff when another AR owns a submodule. Verify that PPM data have been set for a submodule, regardless of owning AR. The output data frame ID from the PLC should be unique per device, not per AR. Adapt sample application to be able to handle multiple connections. Future work is needed for one input subslot to be able to send data to multiple PLCs. Closes rtlabs-com#131 Closes rtlabs-com#169
hefloryd
pushed a commit
that referenced
this issue
Mar 26, 2021
CMSU and CMWRR should be per AR instead of per device. Implement modulediff when another AR owns a submodule. Verify that PPM data have been set for a submodule, regardless of owning AR. The output data frame ID from the PLC should be unique per device, not per AR. Adapt sample application to be able to handle multiple connections. Future work is needed for one input subslot to be able to send data to multiple PLCs. Closes #131 Closes #169
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we have two siemens plc s71200 ,connect one io-device ,error happend(one connection is ok ,the other is wrong)
information:
Connect call-back. AREP: 2 Status codes: 0 0 0 0
[15:22:09 DEBUG] CMDEV(1078): New state: PF_CMDEV_STATE_W_CRES for AR with AREP 2
[15:22:09 DEBUG] CMDEV(1078): New state: PF_CMDEV_STATE_W_SUCNF for AR with AREP 2
[15:22:09 INFO ] CMRPC(628) ERROR: 219, 129, 61, 0
[15:22:09 DEBUG] CMRPC(1279): Create CONNECT response: ret = -1 error_code=219 error_decode=129 error_code_1=61 error_code_2=0
[15:22:09 DEBUG] CMRPC(1190): Connect response args_length = 0
[15:22:09 INFO ] CMRPC(1285): Connect failed - Free AR!
[15:22:09 DEBUG] CMRPC(535): Free AR 1
[15:22:09 DEBUG] CMRPC(1291): Created connect response: ret -1
we found the wrong place:
int pf_cmsu_start_req(
pnet_t *net,
pf_ar_t *p_ar,
pnet_result_t *p_stat)
{
int ret = -1;
uint32_t crep;
switch (net->cmsu_state)
{
case PF_CMSU_STATE_IDLE:
.......
case PF_CMSU_STATE_STARTUP:(here error happened)
p_stat->pnio_status.error_code_1 = PNET_ERROR_CODE_1_CMDEV;
p_stat->pnio_status.error_code_2 = PNET_ERROR_CODE_2_CMDEV_STATE_CONFLICT;
ret = -1;
break;
we also want to know how to use the io-device when wo have mutiple ar,do we need modify gsdml?
The text was updated successfully, but these errors were encountered: