These are chat archives for CORE-POS/IS4C

1st
Aug 2016
Andy Theuninck
@gohanman
Aug 01 2016 18:50
The printer port settings bug is patched in both master and version-2.2 branches
Finn
@thefinn93
Aug 01 2016 18:52
Cool, thanks :)
We're pretty fed up with the documentation free scale protocol
And trying to get it to work on dot net (which non of us have ever really used) is just making things more confusing
So I think we're going to try to implement our own scale driver in node or Python
Finn
@thefinn93
Aug 01 2016 18:59
Proly node so we can use nice async stuff and do websockets easily
Andy Theuninck
@gohanman
Aug 01 2016 19:00
You're certainly welcome to, but I'm kind of curious what you feel like is missing from protocol (https://github.com/CORE-POS/IS4C/wiki/SerialPortHandler) or architecture (https://github.com/CORE-POS/IS4C/wiki/Hardware-Driver) documentation.
Finn
@thefinn93
Aug 01 2016 19:01
Nothing about your protocol is missing, it's lack of docs on the hardware we're using
It doesn't seem to use a communication format anything like what you've got
And trying to reverse engineer it and add that to the existing hardware driver in a language we don't really know is just getting frustrating. Idk, not totally set on it, just something we're thinking about. I gotta go to a meeting but I'll reqd those wiki pages when I'm back
Andy Theuninck
@gohanman
Aug 01 2016 19:08
Well, if you do go that route, POS is capable of subscribing to RabbitMQ via websockets (https://github.com/CORE-POS/IS4C/blob/master/pos/is4c-nf/js/poll-scale.js#L59-L81). The message format would have to match what POS expects, but it may simplify passing information from your custom app over to the browser
Finn
@thefinn93
Aug 01 2016 20:01
Oh cool
I saw some stuff about a message queue but wasn't sure what it was exactly and didn't really persue it
Yeah we can format it to whatever format CORE expects
Andy Theuninck
@gohanman
Aug 01 2016 20:16
If node's in your guys' normal toolkit, there's also a node-webkit option that will just accept direct messages over UDP and insert them into the browser. I tend to think using RabbitMQ will be less prone to dropped messages, but node-webkit might be the best way to approach managing a second screen. There aren't all of the normal browser parent-child window rules to deal with (I have not actually tried the commented section for opening a 2nd window on a 2nd screen)
Finn
@thefinn93
Aug 01 2016 20:17
Oh interesting
danry25
@danry25
Aug 01 2016 20:38
Man, I'm just starting to remember how hard NCR is to work with
Trying to get developer docs for the NCR 7878
Finn
@thefinn93
Aug 01 2016 20:38
Thanks :)
danry25
@danry25
Aug 01 2016 20:40
Comparatively, Motorola and Honeywell are easy to talk to
Andy Theuninck
@gohanman
Aug 01 2016 20:46
NCR Scanner Programmer's Guide.PDF
Says 7870, 7875, and 7880 but a 7878 might be similar
danry25
@danry25
Aug 01 2016 20:50
@gohanman Thanks! 7870 thru present is the same protocol
Finn
@thefinn93
Aug 01 2016 20:50
now where'd you get that?
Andy Theuninck
@gohanman
Aug 01 2016 20:53
I don't remember. Google Drive says I uploaded it about a year ago. I've actually used it as a reference for scale protocol since I don't have an equivalent Datalogic guide. Other than the "S" prefix their scale protocol seems identical
Finn
@thefinn93
Aug 01 2016 20:53
huh
@danry25 got the info i needed out of that, you wanna call me?
danry25
@danry25
Aug 01 2016 20:54
yeah
you looking at 4-15
Finn
@thefinn93
Aug 01 2016 20:55
yeah, thereabouts
i read some other bits too
Finn
@thefinn93
Aug 01 2016 21:22
cool
danry25 @danry25 checks manual to see if any config changes need to be made to turn off pacesetter & bcc
^^ @asapdx
Asa
@asapdx
Aug 01 2016 23:28
We're able to see the weight from the scale in the log, but it's not showing up in CORE-POS.
Andy Theuninck
@gohanman
Aug 01 2016 23:29
How does it appear in the log?
Asa
@asapdx
Aug 01 2016 23:30
Aug 01 16:29:48 jebian-dessie mono[15833]: RECV FROM SCALE: 1440082
Aug 01 16:29:49 jebian-dessie mono[15833]: RECV FROM SCALE: 141
Aug 01 16:29:49 jebian-dessie mono[15833]: PASS TO POS: S141
Aug 01 16:29:49 jebian-dessie mono[15833]: RECV FROM SCALE: 141
Same issue with UPCs, it shows up in the log but it doesn't get into CORE-POS
Aug 01 16:33:53 jebian-dessie mono[15833]: RECV FROM SCALE: 143
Aug 01 16:33:53 jebian-dessie mono[15833]: RECV FROM SCALE: 08133780085698
Aug 01 16:33:53 jebian-dessie mono[15833]: PASS TO POS: 08133780085698
Andy Theuninck
@gohanman
Aug 01 2016 23:36
Well, with weight, the lack of a PASS TO POS line after 1440082 would explain why it's not going through. The UPC not working is confusing though
Finn
@thefinn93
Aug 01 2016 23:36
it does UDP communication on ports 9450 and 9451 right?
i could tcpdump and see if anything's getting sent
Andy Theuninck
@gohanman
Aug 01 2016 23:37
Not for scale to POS. It should be dropping files in NewMagellan/ss-output. Those get picked up (and then deleted) by AJAX calls that just poll the directory
Finn
@thefinn93
Aug 01 2016 23:37
oh right
Andy Theuninck
@gohanman
Aug 01 2016 23:42
It looks like the logic is off here https://github.com/CORE-POS/IS4C/blob/0ef2e33b8add60aab7885ae0a975b9de8285baff/pos/is4c-nf/scale-drivers/drivers/NewMagellan/SPH_NCR_Scale.cs#L163-L177. I can't tell from the NCR doc what the default scan formatting is supposed to be, but it looks like this just has an 08 prefix without a letter indicating the barcode type