Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.

Log in or register to post/reply in the forum.

Baler cannot see recently added stations

pitacco Oct 19, 2020 08:39 AM

I have recenty added 5 new stations (CR300, CR1000X) to my network, that is neatly managed by LoggerNet. All of them are callback-enabled, GPRS stations, and LoggerNet (v 4.5) has not any problem in handling scheduled data collection properly. However, Baler (v 4.0, running on the same PC) apparently is not able to handle the new stations. They are not even reported in its Stations list screen.

The stations database (logger type, communication details, schedule, datatables...), as created and managed by LoggerNet/Setup is just OK. Isn't Baler looking at that, to get stations infos? Why some are not even displayed? Is it possible that new-type loggers are not properly handled by Baler, while old type (CR1000, CR3000, CR6, even CR23XPB...) do?

Best, Andrea

JDavis Oct 19, 2020 01:45 PM

Baler is a retired product, and stopped receiving updates to support additional datalogger models.

The dataloggers listed in the compatibility table should still work.


pitacco Oct 19, 2020 02:19 PM

Thank you, JDavis, your reply clarified and helped.

While I admit I do not know the deep intricacies of handling these new-type entries in the stations database, I am stil a bit confused/surprise by this rapid obsolescence of simple (and handy) software packages. Isn't it the handling of dataflow primarily managed by LoggerNet pretty similar among all dataloggers?

Should I go towards LNDB for such a (simple) task?

Best, Andrea

Log in or register to post/reply in the forum.