Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic adaption of pnet to multiple connections #382

Merged
merged 1 commit into from
Mar 26, 2021

Conversation

pyhys
Copy link
Collaborator

@pyhys pyhys commented 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 same input subslot to be able to send data to multiple PLCs.

Closes #131
Closes #169

@pyhys pyhys requested a review from olbjo March 17, 2021 10:44
@pyhys pyhys force-pushed the move_states_to_ar branch from d9b61d6 to df2aa5c Compare March 17, 2021 11:01
Copy link
Collaborator

@olbjo olbjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍
Great, some minor comments.


/* Send application ready */
os_event_set (p_appdata->main_events, APP_EVENT_READY_FOR_DATA);
if (pnet_application_ready (net, arep) != 0)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There should be a log message for "pnet_application_ready" call. In default log FATAL configuration I do not think any message will be seen related to to application ready which is an key state transition

"Set application ready"

Copy link
Collaborator Author

@pyhys pyhys Mar 24, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already in PR #383
Done

* true also if only the IOPS is set.*/
p_iodata = &p_ar->iocrs[ix].data_desc[iy];

/* Users are limited to setting data for a specific subslot.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would go for "Application is" and avoid "users", "you" and references to persons in the log messages and comments.

Also what the checks below actually test is a bit unclear. Are they a workaround or a final solution?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated comment.
Done

@pyhys pyhys force-pushed the move_states_to_ar branch from df2aa5c to b505872 Compare March 24, 2021 08:46
@pyhys pyhys requested a review from hefloryd March 24, 2021 08:47
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 pyhys force-pushed the move_states_to_ar branch from b505872 to fbd08f4 Compare March 24, 2021 11:24
@pyhys
Copy link
Collaborator Author

pyhys commented Mar 24, 2021

Rebased

@hefloryd hefloryd merged commit 9857aba into rtlabs-com:master Mar 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mutiple ar connect one io-device error Fails at mixed startup
3 participants