Hi Ken,
It depends on what protocol the IO-Link Gateway device supports. You might be
lucky and have a simple JSON over HTTP (using 4D’s HTTP Get, etc), but it’s
more likely to be one of the industrial standards. For example, if it’s
Ethernet/IP (which uses CIP) you could cherry-pick and crea
Thanks Steve! Pricy for some of my clients, but sounds good for others.
Having a mini-HTML display (that presumably could display an image) is
especially useful for some applications.
Cheers!
Tony Pollard
Another Dimension Ltd
> On 30 Aug 2018, at 3:27 pm, Stephen J. Orth
> wrote:
>
> To
to include information
> about what the barcode belongs to? Or are you using it as an extended
> keyboard input?
>
> On Tue, Aug 28, 2018 at 4:19 PM Tony Pollard via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
>> If you want the bar code scanning to be independ
If you want the bar code scanning to be independent of where the user is on the
UI, then there is usually a serial port emulation available on USB.
GET SERIAL PORT MAPPING is useful for this on Mac. You can then run serial
comms in a separate process, which is handy if (for instance) the bar cod
I’d really like to be be able to see the size of a worker queue (as David Adams
and others have said in the past). In my case I want a one-shot (+1 if the
worker is running), which doesn’t look doable if the calling process is also
preemptive - unless I lob everything into the queue with a time
d with
> Unicode Mode checked in the Compatibility Settings (error -9990 Time out
> error), but works if the database is opened with Unicode unchecked. I'm
> still trying to figure out how to get Receive Packet working with Unicode
> Mode on. Ken
>
> On Mon, Oct 30, 2017 at 10
Late to the party, but I’m seeing this on v16.2 (Mac Server 64 bit, new network
layer) as well.
Tony Pollard
Another Dimension Ltd
> On 3 Oct 2017, at 9:02 pm, Dennis, Neil via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
>> I’m getting users logged in twice to 4D Server 16.2 Mac. One of the
>>
In upgrading a client from v14 to v16.2 (Mac based), I’ve noticed that RECEIVE
PACKET has become very slow, whilst RECEIVE BUFFER works fine. This is using
serial comms with a scanner (via Keyspan adaptor).
C_BLOB($rxBlob)
SET CHANNEL(101;Data bits 8+Parity none+Speed 19200+Stop bits one)
RECE
8 matches
Mail list logo