You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
General question: How do we differ between YAP and LOG information?
In the simulation this has been solved by routing the print() methods to the console, and the write() method to the SocketServer; which may not be ideal in the architecture, but allows for nice debugging. In the target this is not possible, as both print and write are routed to the Serial interface.
Ideally the LOG information would be sent on its own YAP Data channel, meaning that the Logging Module should be able to write to the YAP Server somehow (only the App knows the YAP Server Instance, so it is not an ideal solution). And maybe only the INFO level Logs, not the DEBUG logs.
Other solution is turning Logs completely off on the target, and any information to be transmitted must be available for the App to read and re-route.
With #47 the logging will be disabled in case the socket server is started via command line. This is just a first step into this direction to make it easier for the user.
General question: How do we differ between YAP and LOG information?
In the simulation this has been solved by routing the print() methods to the console, and the write() method to the SocketServer; which may not be ideal in the architecture, but allows for nice debugging. In the target this is not possible, as both print and write are routed to the Serial interface.
Ideally the LOG information would be sent on its own YAP Data channel, meaning that the Logging Module should be able to write to the YAP Server somehow (only the App knows the YAP Server Instance, so it is not an ideal solution). And maybe only the INFO level Logs, not the DEBUG logs.
Other solution is turning Logs completely off on the target, and any information to be transmitted must be available for the App to read and re-route.
Originally posted by @gabryelreyes in #2 (comment)
The text was updated successfully, but these errors were encountered: