Skip to content
This repository was archived by the owner on Nov 11, 2024. It is now read-only.

Use of MAPPDK Logger #27

Open
qboticslabs opened this issue Jun 14, 2023 · 1 comment
Open

Use of MAPPDK Logger #27

qboticslabs opened this issue Jun 14, 2023 · 1 comment

Comments

@qboticslabs
Copy link

Hello

Can we omit the mappdk_logger and start only with mappdk_server to interact with the robot? Can you explain what will be the after-effects if we are not using the logger?

Also, any methods to start and stop the running mappdk_server after some time in the TP code?

@torayeff
Copy link
Owner

@qboticslabs you can do that. The only reason mappdk_logger exist is for simultaneously running robot commands and logging data. For example, if you want to perform some robotic movement motions and at the same time log the data, then you need mappdk_logger. In essence, mappdk_logger is just a copy of mappdk_server which listens on a different port.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants