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.

optimizing packets


IslandMan Aug 4, 2017 10:53 AM

I have a non-campbell packet radio that we are trying to optimize the communications with.
The max packet length in the radio is 255. The Network is:

Loggernet <---> RV50 <---> RS232 on CR1000 Base (configured as router)

COM4 on CR1000 Base is fixed 9600 into Base radio.

There are three remote radios, all with CR1000 loggers. Radio is connected to COM4 on all CR1000, 9600 fixed.

Three remotes have fixed allowed neighbors on COM4 to only communicate with base.

Base has fixed allowed neighbors to allow coms to three remote loggers.

Beacons and Verify are all default of zero.

Max packet in Loggernet is the default 998 for all CR1000 loggers.

Max packet in advanced settings in the CR1000's are the default 1000.

We are having difficulty maintaining communications with the remotes. My question is, should all the packbus packet lengths be adjusted to the max 255 of the radio, or something less?

Thanks,

Dave


JDavis Aug 4, 2017 02:52 PM

I would set the max packet size on the remotes to 250.


IslandMan Aug 4, 2017 03:18 PM

Hi Jacob,

Loggernet setup as well?

Thanks,

Dave


JDavis Aug 4, 2017 05:05 PM

The communication link between two devices uses the minimum set on either device.

If you set the max to 250 in Loggernet Setup for a remote logger, it would limit packet size to 250 when Loggernet is talking to that remote datalogger. If you set the max to 250 in the remote logger itself, packet size would be limited to 250 when it talks to anything.


IslandMan Aug 4, 2017 06:05 PM

So no matter which way I slice this, having the 250 max on the loggers is going to limit it on the RV50 communications from Loggernet into the base logger. Thanks for the help, as always, I appreciate it.

Dave


JDavis Aug 4, 2017 06:14 PM

Talking to the base logger won't be limited. You can leave that max packet size at 998 or 1000. Collecting data from the base datalogger will still use the bigger packets.

Limit the packet size for the remote, and data coming from it will be in smaller packets. 


ariklee Nov 24, 2020 09:44 PM

Follow up question on this:

When using an RF451 network, does the Loggenet maximum packet size setting on an individual logger still come into play? I.e., since the radios are doing all the routing... Does the Loggernet request for data include the packet size parameter?

Thanks,

Eric


ariklee Nov 24, 2020 10:22 PM

I'm trying to optimize data collection using RF451 network. Some sites are far and comm is poor. Whether I use 250 or 998 in the Loggernet Max Packet Size setting for a particular logger, I get the same amount of data collected in the "Val Last Collected" field in Status Monitor (SM). E.g...

Using 998, SM gives me 0 --> 728 --> 1456...

Using 250, SM gives me 0 --> 728 --> 1456...

To me this indicates that the Max Packet Size in Loggernet isn't part of the request message and isn't doing anything.

EDIT: Also does not appear to make a difference if I change the Max Packet Size of an upsteam repeater to 250. Still getting 728 values collected on first collection...


jtrauntvein Nov 25, 2020 09:51 PM

With PakBus dataloggers, which includes the CR1000 and anything newer, there are Max Packet Size settings both in LoggerNet as well as similar settings on the datalogger itself.  The setting in LoggerNet will govern the size of large, variable length messages sent by LoggerNet including anything involved with sending or receiving a file.  The datalogger setting primarily deals with the size of the messages sent by the datalogger for responses to data collection requests.  If you use the Network Planner to set up the settings for both the datalogger as well as for LoggerNet, you will find that it will generate settings for both sides.  

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