# LogixDriver Warnings Flooding Log File **URL:** \ **Category:** Ignition\ **Tags:** sepasoft\ **Created:** [February 10, 2023, 12:52pm UTC](https://forum.inductiveautomation.com/t/logixdriver-warnings-flooding-log-file/69688 "2023-02-10T12:52:33Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [February 10, 2023, 1:06pm UTC](https://forum.inductiveautomation.com/t/logixdriver-warnings-flooding-log-file/69688/2 "2023-02-10T13:06:25Z")
Rockwell introduced new primitive datatypes in recent firmware versions, including LTIME. If you really need these, you might consider testing my new EtherNet/IP driver, which should support these. It is in beta, and not tested much on these types, but I wouldn't mind a data point: > [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/31): > > New beta. Couple items: Suppressed a super-noisy warning that would flood the logs while connecting and probing and during even the slightest comms hiccup. Significantly reduced memory pressure throughout the module by implementing SoftReference caching for byte[] and ByteBuffer instances, using stepped sizes (8, 12, 16, 24, 32, 48, 64, 96...). The GC can still reclaim them when it needs to, but it makes it possible to skip new object creation when used and released instances are hanging… However, I suspect you aren't actually using these tags (or you'd have found this problem earlier). Which suggests that someone dragged and dropped an entire tag hierarchy from the OPC browser to Ignition's tag browser, creating subscriptions to everything. That is an extremely bad practice. --- _[View the full topic](https://forum.inductiveautomation.com/t/logixdriver-warnings-flooding-log-file/69688)._