Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Gene Heskett
On Monday 03 February 2020 22:55:04 Jon Elson wrote: > On 02/03/2020 08:25 PM, Jon Elson wrote: > > On 02/03/2020 06:46 PM, andy pugh wrote: > >> Is he using a 64-bit kernel? The size of integers might > >> have changed. > > Yes, the customer reports it IS a 64-bit kernel, and the > logic there

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Gene Heskett
On Monday 03 February 2020 19:46:30 andy pugh wrote: > On Fri, 31 Jan 2020 at 17:38, Jon Elson wrote: > > Hmmm, some interesting things to note. His input scale is > > 85333.33 counts/inch. > > 85333 * 50331 looks like it is very close to a 32-bit > > rollover (4294895223). > > The PPMC devices

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Jon Elson
On 02/03/2020 08:25 PM, Alec Ari via Emc-developers wrote: Would using `long long` instead of `long` be a potential fix then? I'm not a very good C coder but I've noticed higher precision using `long long` over all else, never seen `long long` fail for me. I think it is better to use

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Jon Elson
On 02/03/2020 08:25 PM, Jon Elson wrote: On 02/03/2020 06:46 PM, andy pugh wrote: Is he using a 64-bit kernel? The size of integers might have changed. Yes, the customer reports it IS a 64-bit kernel, and the logic there can't be expected to work right on a 64-bit long variable. I'll have

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Jon Elson
On 02/03/2020 06:46 PM, andy pugh wrote: On Fri, 31 Jan 2020 at 17:38, Jon Elson wrote: Hmmm, some interesting things to note. His input scale is 85333.33 counts/inch. 85333 * 50331 looks like it is very close to a 32-bit rollover (4294895223). The PPMC devices use a 24-bit hardware counter,

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Alec Ari via Emc-developers
Would using `long long` instead of `long` be a potential fix then? I'm not a very good C coder but I've noticed higher precision using `long long` over all else, never seen `long long` fail for me. The commit I referred to is this one, but andypugh probably has a better idea on this than I do,

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Jon Elson
On 02/03/2020 02:19 PM, Alec Ari via Emc-developers wrote: Hi, I encounter problems like this all the time; you use a version of software, update the software, and a bug gets introduced between versions when the code very seemingly related to the problem, HASN'T CHANGED. If the driver code

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread andy pugh
On Fri, 31 Jan 2020 at 17:38, Jon Elson wrote: > Hmmm, some interesting things to note. His input scale is > 85333.33 counts/inch. > 85333 * 50331 looks like it is very close to a 32-bit > rollover (4294895223). > The PPMC devices use a 24-bit hardware counter, and then > rollover and extension

Re: [Emc-developers] 2.9 problem

2020-02-03 Thread Alec Ari via Emc-developers
Hi, I encounter problems like this all the time; you use a version of software, update the software, and a bug gets introduced between versions when the code very seemingly related to the problem, HASN'T CHANGED. If the driver code hasn't changed, is it the same Linux kernel, distribution,

Re: [Emc-developers] Buildbot on Buster

2020-02-03 Thread N
I do build on Buster, unfortunately I did not write down which packages I had to install. Are also able to use gladevcp if installing som more packages and manually install python-gtksourceview2_2.10.1-3_amd64.deb > On Sat, 1 Feb 2020 at 04:02, Sebastian Kuzminsky > wrote: > > > > I'm

Re: [Emc-developers] Buildbot

2020-02-03 Thread andy pugh
On Sat, 1 Feb 2020 at 04:02, Sebastian Kuzminsky wrote: > > I'm working on a buildbot upgrade, in order to support Debian Buster > builds. Oooh! Thanks. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and

Re: [Emc-developers] Question for iocontrol v2

2020-02-03 Thread andy pugh
On Sat, 1 Feb 2020 at 02:28, Johannes Fassotte wrote: > > Not sure if this is an issue with a unmodified version of iocontrol v2 or > potentially related to my own version which adds some pins I suspect that there are not many users of iocontrol_v2. As far as I can see the docs don't even say