× 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.



Bryan,

You've actually still got a wedge, the USB scanners have basically a
"software" wedge. From the applications point of view, the data has
been entered from the keyboard, just like with a hardware wedge.

So the thing to do would be to see if you can find scales with a
similar interface.

HTH,
Charles


On Wed, Mar 4, 2009 at 4:48 PM, Burns, Bryan <Bryan_Burns@xxxxxxxxxxxx> wrote:
Thanks Mark.  We have 11 final assembly workstations - all with wedges, which pass scale data to 400 files and have been doing it for years. It took me a long, long time to learn how to configure the wedges when a developer left the company.  My objective here is to make things more swappable on such critical assembly lines.  The wedges require specialized knowledge, and careful configuration and documentation.  Plus, they're somewhat costly.

By the way, when we first rolled this out years ago, we were using  undecoded bar code scanners connected to a wedge and the scale connected to the wedge and the wedge connected to a dumb terminal.  Since then, we've gone to thin clients with USB decoded bar code scanners which don't require a wedge.  So I figure, why not get rid of the wedge all together?  Perhaps we're stuck with the wedges and there's nothing wrong with your approach but I just need to confirm in my own mind that we need wedges.  The wedges do decoding?


Bryan Burns


-----Original Message-----
From: J M Plank [mailto:plank.computer@xxxxxxxxx]
Sent: Wednesday, March 04, 2009 2:28 PM
To: Burns, Bryan
Subject: Re: Getting data from a scale to a system i host

Bryan,

I took this offlist - feel free to reply on list if you think it would help.

Why are you trying to eliminate the wedge?  We just implemented a subsystem in the past two weeks where we are using our first wedges for 14 scale stations, and have another 7 to convert whenever I get sent to our LA company location.  Now I'm wondering if we made an incorrect design decision.

We had/have two C++ programs written by a consultant about 10 years ago running on Windows 98 machines.  One program is used for generating labels and outputs data that the second program pushes to a server, then that gets pulled to another server, then the 400 (er i or whatever the latest name is) retrieves the data - lots of places for errors to creep in, and they do.  I've replaced them with an RPG program using a wedge to retrieve the scale weight, and that program writes directly to the 400 files.  We also have all new XP machines now to run client access on, thank goodness.

Thanks for any advice/words of wisdom.
Mark Plank
Lead Application Support Specialist
Maple Leaf Farms
Milford, IN

On Wed, Mar 4, 2009 at 12:38 PM, Burns, Bryan < Bryan_Burns@xxxxxxxxxxxx> wrote:

Aha.  I'm beginning to see the light but it's still dark.

We want to pass a weight, 9.2 lbs for example, to the iSeries.  We're currently doing this with a keyboard wedge but want to eliminate the wedge.

Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich,  Illinois
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.