Re: Command Parameter Variable Character field -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Command Parameter Variable Character field
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Tue, 30 Apr 2019 12:35:48 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 2019-04-30 7:02 AM, Spencer Elliott wrote:

Hi,
The entire command is as follows. Maybe it assumes a MAX because I
specified a MIN. The value is 0x3E8 (1000).

As far as I know, coding MIN(1) doesn't cause it to assume a higher MAX.

What is the hex value of the first say 20 bytes of the parameter? And what is the value of the parameter you're passing?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Command Parameter Variable Character field , Spencer Elliott

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.