String Length Limit on AXC-232???
TurnipTruck
Junior Member
in AMX Hardware
Does anyone know what the limit is on how many character an AXC-232 can send in one transmission?
I have a system with in which about 300 characters need to go out it one transmission. From the same Netlinx master, an NXI serial port puts them all out as does an Axcent 3 in slave mode. However, an AXC-232 running in an AXF-BP with a card server from the Netlinx master seems to truncate some characters.
Thank you!
I have a system with in which about 300 characters need to go out it one transmission. From the same Netlinx master, an NXI serial port puts them all out as does an Axcent 3 in slave mode. However, an AXC-232 running in an AXF-BP with a card server from the Netlinx master seems to truncate some characters.
Thank you!
Comments
-
I can remember that somewhere in the Technotes was a table about hardware transmit and receive buffer sizes, but I haven't found it again......
AFAIK the maximum string length is 64 bytes in one SEND_STRING on the AXcess RS232 ports. -
It's tech note 156... Technically, anything pre-Netlinx shouldn't accept a SEND_STRING message longer than 64 bytes, so I'm suprised that Axcent3 works with 300!
According to the note, Netlinx processor com ports and NXC-COM2 cards can handle up to 900 bytes going out on a SEND_STRING...
- Chip -
Chip Moody wrote:It's tech note 156... Technically, anything pre-Netlinx shouldn't accept a SEND_STRING message longer than 64 bytes, so I'm suprised that Axcent3 works with 300!
According to the note, Netlinx processor com ports and NXC-COM2 cards can handle up to 900 bytes going out on a SEND_STRING...
- Chip
ARGL..... I have searched with keywords like "serial" "buffer", etc and had no hit
-
Marc Scheibein wrote:ARGL..... I have searched with keywords like "serial" "buffer", etc and had no hit

http://www.amx.com/techsupport/PDNTechNote.asp?id=156 -
In the case of needing to send a string longer than the limit for the hardware, what is the best method?
I'm thinking that one would parse out some amount of bytes less than the limit, send, then repeat until all bytes are sent. If this is the case, what would be the best way to determine that it's clear to send the next load of bytes?
Thank you. -
I think I'd estimate time needed for a WAIT or TIMELINE based on the max sized chunk of data going out at any time * baud rate... 64 bytes * 10 (rounding up) = 640 bits, even at 960 bits per 1/10 second (9600/10) means you could easilly get away with a WAIT 1...
- Chip
Leave a Comment
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums