We recently implemented using a weight scale and connected to the device hub and we are now noticing the scale is creating 3-6X the ERP transactions in the database. The user is simply putting box on top of scale and selecting “capture weight” then removing the box but Acumatica is seeing this as 5X the transactions instead of 1 time. Anyone else going through this dilema? We are seeing the SCALE try to poll every two seconds in some cases.
Thanks,
Nirav S.
Anyone have similar issues? the device hub SCALE is create soo many unnecessary API calls to Acumatica. Any way around this or suggestions to fix this to limit the calls?
i am doing a warehouse management project right now, and frankly I think polling the scale to grab its weight from the device directly is inefficient and error prone (there are no guarantees that the weight will be tared or stable when you decide to execute the capture process; if you have multiple scales the user can select the wrong one, etc). It is also mechanically complex to make sure the scales are always online and connected through the ERP system itself.
Instead, I wrote a simple javascript program that queries the scale (so you can control how often the data is grabbed, per your problem), and then displays a barcode that encodes that weight information on a webpage (it also shows the human readable weight that is on the scale display so user’s can make sure the data they’re capturing from the barcode matches the scale display). Then the user just scans the weight when they want to capture it and it allows them to decide not to capture if the weight coming through the software side doesn’t make sense.
Thanks
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
