Linuxdept (Customer) asked a question.
any thought on why the click encoder seems to play catch up with its register when being requested. like it seems like it fine and then all of a sudden here another 100 encoder counts every .25 secs.. any idea's this is not a HSC
Could be noise. Check grounding. Possibly add a signal conditioner:
dont think the encoder count would just jump X ~15% of counts PPS because of noise would it >? we have the same issue with the Productivity and the HSC
well i add a non resetting timer seeing Xms gaps when the X spikes are at (edited)
switch it to a high res 1ms timer still saw it
figure maybe the resetting timer was causing hangs since it wasn't reporting em still saw it
removed all the code but the console.write still saw it
6139711 (6) Cycle Time: 0 : 501.5374
6139717 (6) Cycle Time: 0 : 507.2441
6139844 (127) Cycle Time: 0 : 633.982
6139845 (1) Cycle Time: 0 : 635.4146
6139846 (1) Cycle Time: 0 : 636.7702
then somewhere around 8ms it seems to stop
6427230 (9) Cycle Time: 0 : 57203.8065
6427237 (7) Cycle Time: 0 : 57211.3226
6427245 (8) Cycle Time: 0 : 57219.4075
6427255 (10) Cycle Time: 0 : 57229.1463
6427261 (6) Cycle Time: 0 : 57235.1911
6427269 (8) Cycle Time: 0 : 57243.1235
6427277 (8) Cycle Time: 0 : 57251.1748
6427285 (8) Cycle Time: 0 : 57259.261
6427293 (8) Cycle Time: 0 : 57267.2002
6427301 (8) Cycle Time: 0 : 57275.3449
6427311 (10) Cycle Time: 0 : 57285.5348
6427317 (6) Cycle Time: 0 : 57291.0756
6427325 (8) Cycle Time: 0 : 57299.2304
6427333 (8) Cycle Time: 0 : 57307.2161
We haven't had any reports from other customers related to your issue. I would reach out to our technical support team 1-800-633-0405 for additional assistance.
the PC was only a Very small 1.1Ghz 1Gb Ram , replaced it with 3.2Ghz 8Gb Problem went away
the PC was only a Very small 1.1Ghz 1Gb Ram , replaced it with 3.2Ghz 8Gb Problem went away