quarry VS pycomm3

Hey, i found out there is no way to remove that message from the game. But you can make a basic proxy to hide only that chat message: here is the repository to the api: Quarry. Note that this is only an example not the proxy you need.

Link HERE

For me it was probably quarry which taught me about protocol buffers

Probably best to start a discussion in the repo. https://github.com/ottowayi/pycomm3

If you want to see the code, it's on github. Everything starts with get_tag_list in pycomm3/logix_driver.py. And _parse_template_data has most of the logic for parsing the struct attribute definitions. The code is pretty complicated, hard to follow, and not something I'm particularly proud to show off. I've been meaning to refactor it, but I've been avoiding it since it took so long to get working.

To elaborate on what I think u/TheDevilsAutocorrect is getting at, don't do the data logging on the PanelView. Use [Pycomm3](https://github.com/ottowayi/pycomm3) or [pylogix](https://github.com/ottowayi/pycomm3) to log directly to the Raspberry Pi. You can log to CSV pretty easily with either library.

Here are the basic steps, if you have any questions feel free to ask there.

If you're using a MicroLogix with ethernet you can try pycomm3. It's a pure Python Ethernet/IP library I maintain. It started as a port of pycomm to Python 3, but since has changed significantly. It has "support" for MicroLogix thru the SLCDriver. You may need to refer to the pycomm documentation for addressing examples, though. When I was at an integrator we never used MicroLogix PLCs, so any testing was done against a SLC. If you try it out and run into any issues, feel free to open up a issue on GitHub.