V8 MES Barcode Problem

We encountered the same problem. We were able to get the screens to fill-in correctly by slowing down our scanner spreed, but it would only work for a short time. We would end up adjusting the scanner speed daily. A few weeks ago I removed the tab stops on the fields we are not using on the MES screens limiting the number of tab stops that we had to build into our barcodes. Since then our problems have not resurfaced.

--- On Thu, 1/15/09, kam4085 <kmaclennan@...> wrote:

From: kam4085 <kmaclennan@...>
Subject: [Vantage] Re: v8 MES Barcode Problem
To: vantage@yahoogroups.com
Date: Thursday, January 15, 2009, 1:16 PM






We are barcoding through MES. I have had to split up the job number
from the assembly.operation barcode. The form does not seems quick
enough to acknowledge the entry so we just enter using 2 barcodes

Kersten

--- In vantage@yahoogroups .com, "Ari Footlik" <ari@...> wrote:
>
> In trying to figure out a problem we saw with scanning our existing
(and
> working in v6) barcodes, we've been thinking we had a problem with
> system-speed. But I no longer think this is the case.
>
> The problem we see is that when opening the Start Production
program, we
> scan our barcode (job/tab/assy/ tab/op/tab) , but the cursor doesn't
move
> from one box to the next. However, if we keyboard-tab from the Job
to
> the Assy box, then back-tab to the Job box again, everything works
fine
> and we could scan code after code, until we close and re-open the
Start
> Production program.
>
> Has anyone using barcoding seen this problem and found a fix? I see
> that there are "Auto Populate" options that I think might help, but
the
> options are greyed out and cannot be selected. This is the kind of
> problem that will prevent us from going live with v8, so we're very
> hopeful that it's something simple that we're just not thinking
of...
>
> Thanks!
> --Ari
>
>
> [Non-text portions of this message have been removed]
>


















[Non-text portions of this message have been removed]
In trying to figure out a problem we saw with scanning our existing (and
working in v6) barcodes, we've been thinking we had a problem with
system-speed. But I no longer think this is the case.

The problem we see is that when opening the Start Production program, we
scan our barcode (job/tab/assy/tab/op/tab), but the cursor doesn't move
from one box to the next. However, if we keyboard-tab from the Job to
the Assy box, then back-tab to the Job box again, everything works fine
and we could scan code after code, until we close and re-open the Start
Production program.

Has anyone using barcoding seen this problem and found a fix? I see
that there are "Auto Populate" options that I think might help, but the
options are greyed out and cannot be selected. This is the kind of
problem that will prevent us from going live with v8, so we're very
hopeful that it's something simple that we're just not thinking of...

Thanks!
--Ari


[Non-text portions of this message have been removed]
We are barcoding through MES. I have had to split up the job number
from the assembly.operation barcode. The form does not seems quick
enough to acknowledge the entry so we just enter using 2 barcodes

Kersten



--- In vantage@yahoogroups.com, "Ari Footlik" <ari@...> wrote:
>
> In trying to figure out a problem we saw with scanning our existing
(and
> working in v6) barcodes, we've been thinking we had a problem with
> system-speed. But I no longer think this is the case.
>
> The problem we see is that when opening the Start Production
program, we
> scan our barcode (job/tab/assy/tab/op/tab), but the cursor doesn't
move
> from one box to the next. However, if we keyboard-tab from the Job
to
> the Assy box, then back-tab to the Job box again, everything works
fine
> and we could scan code after code, until we close and re-open the
Start
> Production program.
>
> Has anyone using barcoding seen this problem and found a fix? I see
> that there are "Auto Populate" options that I think might help, but
the
> options are greyed out and cannot be selected. This is the kind of
> problem that will prevent us from going live with v8, so we're very
> hopeful that it's something simple that we're just not thinking
of...
>
> Thanks!
> --Ari
>
>
> [Non-text portions of this message have been removed]
>
Kersten -

That would be a wonderful solution if we weren't upgrading from v6, but
we have hundreds (thousands) of old job-travelers that will still need
to be read in v8.

A few minutes after my last post, we found the application that lets us
set configuration options via GUI and print the codes, and we changed
some of the delays. We changed the delay between characters and the
delay between/after tabs.

Delay between characters is referred to as "Intercharacter Delay" which
we set to 5 (and is multiplied by 5ms, making 25ms between characters)
Delay between tabs is referred to as "Interfunction Delay" which we set
to 85 (and is multiplied by 5ms, making 425ms between tabs)

Values as low as 5 and 50 worked directly on the server, but on our test
workstation we had to increase the IF delay to 85. We're about to
conduct tests on our remaining MES stations (including one MES station
that connects to our network via wireless) and I'll post the results.

<phew>
--Ari
________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of kam4085
Sent: Thursday, January 15, 2009 1:16 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: v8 MES Barcode Problem



We are barcoding through MES. I have had to split up the job number
from the assembly.operation barcode. The form does not seems quick
enough to acknowledge the entry so we just enter using 2 barcodes

Kersten

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Ari
Footlik" <ari@...> wrote:
>
> In trying to figure out a problem we saw with scanning our existing
(and
> working in v6) barcodes, we've been thinking we had a problem with
> system-speed. But I no longer think this is the case.
>
> The problem we see is that when opening the Start Production
program, we
> scan our barcode (job/tab/assy/tab/op/tab), but the cursor doesn't
move
> from one box to the next. However, if we keyboard-tab from the Job
to
> the Assy box, then back-tab to the Job box again, everything works
fine
> and we could scan code after code, until we close and re-open the
Start
> Production program.
>
> Has anyone using barcoding seen this problem and found a fix? I see
> that there are "Auto Populate" options that I think might help, but
the
> options are greyed out and cannot be selected. This is the kind of
> problem that will prevent us from going live with v8, so we're very
> hopeful that it's something simple that we're just not thinking
of...
>
> Thanks!
> --Ari
>
>
> [Non-text portions of this message have been removed]
>






[Non-text portions of this message have been removed]
It worked with 5 and 95 on our wireless station, but before we go live
with v8 we'll probably increase it to 10 and 99, since I'm not confident
these values will suffice when there's actual load on the server. For
the sake of consistency, we'll probably use these values on all of our
MES stations (we have 5 of them), and in the future tweak them
individually as necessary.

I found the programming manuals and the application on the HandHeld.com
website, but of course, that would be specific for our brand of
scanners.

Thanks to everyone for bearing with my rambling, and for the insight on
server performance that we were discussing yesterday.

--Ari
________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ari Footlik
Sent: Thursday, January 15, 2009 1:39 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: v8 MES Barcode Problem - Potentially Solved



Kersten -

That would be a wonderful solution if we weren't upgrading from v6, but
we have hundreds (thousands) of old job-travelers that will still need
to be read in v8.

A few minutes after my last post, we found the application that lets us
set configuration options via GUI and print the codes, and we changed
some of the delays. We changed the delay between characters and the
delay between/after tabs.

Delay between characters is referred to as "Intercharacter Delay" which
we set to 5 (and is multiplied by 5ms, making 25ms between characters)
Delay between tabs is referred to as "Interfunction Delay" which we set
to 85 (and is multiplied by 5ms, making 425ms between tabs)

Values as low as 5 and 50 worked directly on the server, but on our test
workstation we had to increase the IF delay to 85. We're about to
conduct tests on our remaining MES stations (including one MES station
that connects to our network via wireless) and I'll post the results.

<phew>
--Ari
________________________________

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of kam4085
Sent: Thursday, January 15, 2009 1:16 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: v8 MES Barcode Problem

We are barcoding through MES. I have had to split up the job number
from the assembly.operation barcode. The form does not seems quick
enough to acknowledge the entry so we just enter using 2 barcodes

Kersten

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> , "Ari
Footlik" <ari@...> wrote:
>
> In trying to figure out a problem we saw with scanning our existing
(and
> working in v6) barcodes, we've been thinking we had a problem with
> system-speed. But I no longer think this is the case.
>
> The problem we see is that when opening the Start Production
program, we
> scan our barcode (job/tab/assy/tab/op/tab), but the cursor doesn't
move
> from one box to the next. However, if we keyboard-tab from the Job
to
> the Assy box, then back-tab to the Job box again, everything works
fine
> and we could scan code after code, until we close and re-open the
Start
> Production program.
>
> Has anyone using barcoding seen this problem and found a fix? I see
> that there are "Auto Populate" options that I think might help, but
the
> options are greyed out and cannot be selected. This is the kind of
> problem that will prevent us from going live with v8, so we're very
> hopeful that it's something simple that we're just not thinking
of...
>
> Thanks!
> --Ari
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]