GEM Network Utility - Packetize Time / Packetize Size / Idle

[TymerTopCat]

From the GEM Network Utility Ver 5.8, there are 3 settings for Comm Setting: (On Ethernet Only Tab)

Packetize Time: 10 /* Is this milliseconds */
Packetize Size: 1800 /* Is this bytes */
Idle Time: 30 /* Is this milliseconds*/

Can you please explain:
1. What each does.
2. What do the values represent? 10 / 1800 / 30
3. What are the default values?
4. Can I Read/Set these values using the API?
If so I don't see them in documentation.

[ben]

From the GEM Network Utility Ver 5.8, there are 3 settings for Comm Setting: (On Ethernet Only Tab)

Packetize Time: 10 /* Is this milliseconds */
Packetize Size: 1800 /* Is this bytes */
Idle Time: 30 /* Is this milliseconds*/

Can you please explain:
1. What each does.
2. What do the values represent? 10 / 1800 / 30
3. What are the default values?
4. Can I Read/Set these values using the API?
If so I don't see them in documentation.

Packetize Time and Size shouldn't be touched, the default values are what we found works best. We'll likely be removing them in a newer version.

Idle Time is the amount of time of inactivity the module will wait before it disconnects. This allows Mixed Mode to work. If you don't need a persistent connection to data log, it should be set to a value lower then your send interval.

The GEM doesn't control these values, it's controlled by the WiFi or Ethernet module.

[TymerTopCat]

I would ask that you not remove these settings.

Why?

I am currently writing a TCP/IP access method, to use the Data Polling API.
Since I have 4 greeneyes I was testing the TCP connection responses and I
noticed that 1 of the 4 Greeneyes was fragmenting the packets, meaning instead
of sending 625 Bytes for a BIN48-NET-Time (4) packet. I was getting 1-4 bytes
at a time instead of the usual 625 bytes. I was using the Socket Class in Microsoft
Windows Visual Studio 2010, via Socket.Read() which returns the number of bytes
read.

I fixed this by changing the values from:
Packetize Time: 0
Packetize Size: 0
Idle Time: 255

to

Packetize Time: 10
Packetize Size: 1800
Idle Time: 30

This makes for a more robust application on my side.

-Russ

[TymerTopCat]

Can you please answer Questions 2,3,4 from my original post?

Tks.

-Russ

[ben]

Can you please answer Questions 2,3,4 from my original post?

Tks.

-Russ

I don't really have a good answer for that, they're settings that come from the factory with the module. I think it's time to build a packet, and size before it spits out the packet.

EDIT:

Length (2 Bytes)
Input serial data packing length. When the input serial data length reaches to
the value, it will be sent out. Please, note that only the low 1 byte is used and
the maximum length is 0x00FF. 0 means the packing condition is disabled.

Interval (2 Bytes)
Input serial data packing interval, which indicates how long to send the input
serial data once. 0 means the condition is not used and 0xFFFF is the
maximum interval in millisecond.

They should be all set to 10/1800 (defaults in our software) as that's what we found works best also.

Check your PM for commands.

Ben