Available from TD 8.32
TD8 makes use of the TurboExchange DLL, which provides a gateway into the Turbo Exchange Network.
A backwards compatibility layer provides seamless integration for Turbo Dispatch products. However due to the way Turbo Dispatch messages are constructed, the specification has always been open to interpretation, and so incompatibilities can arise.
TD8 exposes two compatibility modes built into the DLL client that can be enabled.
Multi Line TD Format
The Turbo Dispatch protocol does not specify a carriage-return after each data field. However all the developer examples would show data with carriage-returns, which led to confusion. Since there was a limit of 512 characters per message, these were a waste of characters, and were optionally dropped. By default TD8 drops them to avoid overrunning any buffers. TD8 can be forced to add the carriage-return's (CR LF) by adding this setting anywhere in TD8's config file:
Multi File TD Format
The maximum TD message size is 512 characters. This was the limit imposed by Mobitex. Job messages that ran over this size would have to be broken into separate messages, and a small time delay introduced to enforce packet order. Turbo Exchange does not have this limitation, and can generate TD compatible messages that break the 512 character limit. To enforce the 512 character rule, add this setting anywhere in TD's config file:
Turbo Exchange & TD8 supports PSubs. In the past Mobitex PSubs had to be set up server-side, and client-Side. Turbo Exchange PSubs are set up server-side only. If you have a PSub number for backup purposes, you may not now require one. See the Psub Numbers page for more information.