Re: [Emc-developers] Broken master 06jan23

2023-01-13 Thread gene heskett 

On 1/13/23 15:16, Chris Morley wrote:

the -d in this line:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o 
camnumber=1 cam_align
is the debug switch - that is why qtvcp is noisy. You can remove it when all is 
good.

I have no experience with linuxcnc over ssh so cannot really help with those 
problems.
I don't know why the camera port number changes but maybe it has to do with 
ssh/logging in locally.

I'll push a change soon that trys the designated camera number and if that 
fails tries to test for a working one and use it.

Thanks for th ebug reports.
Chris


You are more than just welcome Chris, you actually fixed it I think.

History however, has had a tendency to disagree.

Take care & stay well.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-13 Thread Chris Morley 
the -d in this line:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o 
camnumber=1 cam_align
is the debug switch - that is why qtvcp is noisy. You can remove it when all is 
good.

I have no experience with linuxcnc over ssh so cannot really help with those 
problems.
I don't know why the camera port number changes but maybe it has to do with 
ssh/logging in locally.

I'll push a change soon that trys the designated camera number and if that 
fails tries to test for a working one and use it.

Thanks for th ebug reports.
Chris



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-12 Thread gene heskett 

On 1/13/23 01:45, gene heskett wrote:

On 1/12/23 23:45, Chris Morley wrote:
ok good it seems the useable camera number is 1 rather then the 
assumed 0:



Port 1 is working and reads images (480.0 x 640.0)


This can be set in the INI but looks like you need to pull in an update.
Or I can show you what to fix.

after that then you need to use this in the ini.
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o 
camnumber=1 cam_align


Chris

From: gene heskett 
Sent: January 12, 2023 5:43 PM
To: emc-developers@lists.sourceforge.net 


Subject: Re: [Emc-developers] Broken master 06jan23

On 1/11/23 16:43, Chris Morley wrote:

looks like you are using a command like this:

EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align

try changing it to:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} 
cam_align


Thats better, at least lcnc runs, but prints this on the terminal screen:

[QTvcp.QTVCP.QT_MAKEPINS][INFO]  No preference file - cannot set
preference geometry. (qt_makepins.py:160)
VIDEOIO ERROR: V4L: index 0 is not correct!
Could not open video device 0
VIDEOIO ERROR: V4L: index 0 is not correct!
Port 0 is not working.
Port 1 is working and reads images (480.0 x 640.0)
Unable to stop the stream: Invalid argument
Port 2 is not working.
VIDEOIO ERROR: V4L: index 3 is not correct!
Port 3 is not working.
VIDEOIO ERROR: V4L: index 4 is not correct!
Port 4 is not working.
VIDEOIO ERROR: V4L: index 5 is not correct!
Port 5 is not working.
VIDEOIO ERROR: V4L: index 6 is not correct!
Port 6 is not working.
[QTvcp][INFO]  Preference path: None (qtvcp:421)

So I issued a sudo reboot in case something has it running already. I'm
in the house, ssh'd into it.
so I'll restore the sshfs share, and attach the qtvcp.log. Done. I know
zip about qtvcp. Everything I done so far has been pyvcp.

Thank you Chris.  Take care & stay well.

Update, I was out in the garage, making a brass insert to install in a 
soldering iron to set heat set nuts into plastic holes as this printer 
has 75 of them to set, While the lathe was making brass dust, I logged 
into the go704 and ran it from its own keyboard, and was pleasantly 
surprised so see it work quite well, on its own monitor. The camera was 
looking at the edge grain of a 9 ply plywood shelf from about an inch 
away, and the stripes of the plywood layers and the grain of the wood 
were perfect. Hopefully I can get it mounted again and calibrated this 
time.


So on its own monitor, it works, but it does not work from an ssh -Y 
login.  I do maintenance from an easy chair here in the house, but I 
don't move a machine unless I'm there to see it get started ok.


But this has gone on for several years, works till the buildbot makes me 
a version of master and I install it, and the camera is gone again.


It takes a couple days to make one of these screws, and that once its 
running, I'm fine with walking away for a couple hours. and due to 
limits of z motion on the 6040, making the stick round is a two stage 
job, which with the teeny tool takes around 36 hours in 2 stages, I 
approach it from the side as high as it will go until its centered over 
the stick, that stage 1, stage 2 is dropping the spindle until the 2x2's 
flats are gone as stage 2, then stage 3 actually carves the 12mm pitch, 
2 start, buttress thread. That takes the final 3 or so hours, and I have 
stops at the end of each stage, so once its running. I can get some sleep.


I just updated that machine, and now the camera is working for an ssh -Y 
login. Now I wonder if it's because I am also locally logged in.


Should I go ahead and change the launch line as you suggested?



I did, still works. qtvcp is still noisy but that is probably because 
its early in getting it working.



Many many thanks for getting it going again. Take care and stay well.

Cheers, Gene Heskett.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-12 Thread gene heskett 

On 1/12/23 23:45, Chris Morley wrote:

ok good it seems the useable camera number is 1 rather then the assumed 0:


Port 1 is working and reads images (480.0 x 640.0)


This can be set in the INI but looks like you need to pull in an update.
Or I can show you what to fix.

after that then you need to use this in the ini.
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o 
camnumber=1 cam_align

Chris

From: gene heskett 
Sent: January 12, 2023 5:43 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

On 1/11/23 16:43, Chris Morley wrote:

looks like you are using a command like this:

EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align

try changing it to:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} cam_align


Thats better, at least lcnc runs, but prints this on the terminal screen:

[QTvcp.QTVCP.QT_MAKEPINS][INFO]  No preference file - cannot set
preference geometry. (qt_makepins.py:160)
VIDEOIO ERROR: V4L: index 0 is not correct!
Could not open video device 0
VIDEOIO ERROR: V4L: index 0 is not correct!
Port 0 is not working.
Port 1 is working and reads images (480.0 x 640.0)
Unable to stop the stream: Invalid argument
Port 2 is not working.
VIDEOIO ERROR: V4L: index 3 is not correct!
Port 3 is not working.
VIDEOIO ERROR: V4L: index 4 is not correct!
Port 4 is not working.
VIDEOIO ERROR: V4L: index 5 is not correct!
Port 5 is not working.
VIDEOIO ERROR: V4L: index 6 is not correct!
Port 6 is not working.
[QTvcp][INFO]  Preference path: None (qtvcp:421)

So I issued a sudo reboot in case something has it running already. I'm
in the house, ssh'd into it.
so I'll restore the sshfs share, and attach the qtvcp.log. Done. I know
zip about qtvcp. Everything I done so far has been pyvcp.

Thank you Chris.  Take care & stay well.

Update, I was out in the garage, making a brass insert to install in a 
soldering iron to set heat set nuts into plastic holes as this printer 
has 75 of them to set, While the lathe was making brass dust, I logged 
into the go704 and ran it from its own keyboard, and was pleasantly 
surprised so see it work quite well, on its own monitor. The camera was 
looking at the edge grain of a 9 ply plywood shelf from about an inch 
away, and the stripes of the plywood layers and the grain of the wood 
were perfect. Hopefully I can get it mounted again and calibrated this time.


So on its own monitor, it works, but it does not work from an ssh -Y 
login.  I do maintenance from an easy chair here in the house, but I 
don't move a machine unless I'm there to see it get started ok.


But this has gone on for several years, works till the buildbot makes me 
a version of master and I install it, and the camera is gone again.


It takes a couple days to make one of these screws, and that once its 
running, I'm fine with walking away for a couple hours. and due to 
limits of z motion on the 6040, making the stick round is a two stage 
job, which with the teeny tool takes around 36 hours in 2 stages, I 
approach it from the side as high as it will go until its centered over 
the stick, that stage 1, stage 2 is dropping the spindle until the 2x2's 
flats are gone as stage 2, then stage 3 actually carves the 12mm pitch, 
2 start, buttress thread. That takes the final 3 or so hours, and I have 
stops at the end of each stage, so once its running. I can get some sleep.


I just updated that machine, and now the camera is working for an ssh -Y 
login. Now I wonder if it's because I am also locally logged in.


Should I go ahead and change the launch line as you suggested?

Many many thanks for getting it going again. Take care and stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-12 Thread Chris Morley 
ok good it seems the useable camera number is 1 rather then the assumed 0:


Port 1 is working and reads images (480.0 x 640.0)


This can be set in the INI but looks like you need to pull in an update.
Or I can show you what to fix.

after that then you need to use this in the ini.
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o 
camnumber=1 cam_align

Chris

From: gene heskett 
Sent: January 12, 2023 5:43 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

On 1/11/23 16:43, Chris Morley wrote:
> looks like you are using a command like this:
>
> EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align
>
> try changing it to:
> EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} cam_align

Thats better, at least lcnc runs, but prints this on the terminal screen:

[QTvcp.QTVCP.QT_MAKEPINS][INFO]  No preference file - cannot set
preference geometry. (qt_makepins.py:160)
VIDEOIO ERROR: V4L: index 0 is not correct!
Could not open video device 0
VIDEOIO ERROR: V4L: index 0 is not correct!
Port 0 is not working.
Port 1 is working and reads images (480.0 x 640.0)
Unable to stop the stream: Invalid argument
Port 2 is not working.
VIDEOIO ERROR: V4L: index 3 is not correct!
Port 3 is not working.
VIDEOIO ERROR: V4L: index 4 is not correct!
Port 4 is not working.
VIDEOIO ERROR: V4L: index 5 is not correct!
Port 5 is not working.
VIDEOIO ERROR: V4L: index 6 is not correct!
Port 6 is not working.
[QTvcp][INFO]  Preference path: None (qtvcp:421)

So I issued a sudo reboot in case something has it running already. I'm
in the house, ssh'd into it.
so I'll restore the sshfs share, and attach the qtvcp.log. Done. I know
zip about qtvcp. Everything I done so far has been pyvcp.

Thank you Chris.  Take care & stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-12 Thread gene heskett 

On 1/11/23 16:43, Chris Morley wrote:

looks like you are using a command like this:

EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align

try changing it to:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} cam_align


Thats better, at least lcnc runs, but prints this on the terminal screen:

[QTvcp.QTVCP.QT_MAKEPINS][INFO]  No preference file - cannot set 
preference geometry. (qt_makepins.py:160)

VIDEOIO ERROR: V4L: index 0 is not correct!
Could not open video device 0
VIDEOIO ERROR: V4L: index 0 is not correct!
Port 0 is not working.
Port 1 is working and reads images (480.0 x 640.0)
Unable to stop the stream: Invalid argument
Port 2 is not working.
VIDEOIO ERROR: V4L: index 3 is not correct!
Port 3 is not working.
VIDEOIO ERROR: V4L: index 4 is not correct!
Port 4 is not working.
VIDEOIO ERROR: V4L: index 5 is not correct!
Port 5 is not working.
VIDEOIO ERROR: V4L: index 6 is not correct!
Port 6 is not working.
[QTvcp][INFO]  Preference path: None (qtvcp:421)

So I issued a sudo reboot in case something has it running already. I'm 
in the house, ssh'd into it.
so I'll restore the sshfs share, and attach the qtvcp.log. Done. I know 
zip about qtvcp. Everything I done so far has been pyvcp.


Thank you Chris.  Take care & stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 
2023-01-12 12:31:40,264 - QTvcp.QTVCP.QT_ISTAT - WARNING - Embeded tab configuration -invalaid number of TAB_NAMES vrs TAB_LOCATION - guessng default.
2023-01-12 12:32:07,814 - QTvcp.QTVCP.LIB.SYS_NOTIFY - WARNING - Desktop Notify not available:: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2023-01-12 12:32:08,916 - QTvcp - INFO - Logging to: /home/gene/qtvcp.log
2023-01-12 12:32:08,917 - QTvcp - INFO - Base log level set to: 10
2023-01-12 12:32:08,917 - QTvcp.QTVCP.QT_PSTAT - DEBUG - BASEPATH cam_align
2023-01-12 12:32:08,917 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for handler file in: /home/gene/linuxcnc/configs/GO704-5i25-7i76-camera/cam_align_handler.py
2023-01-12 12:32:08,917 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for default handler file in: /usr/share/qtvcp/panels/cam_align/cam_align_handler.py
2023-01-12 12:32:08,942 - QTvcp.QTVCP.QT_PSTAT - INFO - Using DEFAULT handler file path: /usr/share/qtvcp/panels/cam_align/cam_align_handler.py
2023-01-12 12:32:08,942 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for .ui in: /home/gene/linuxcnc/configs/GO704-5i25-7i76-camera/cam_align.ui
2023-01-12 12:32:08,942 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for .ui in: /usr/share/qtvcp/panels/cam_align/cam_align.ui
2023-01-12 12:32:08,943 - QTvcp.QTVCP.QT_PSTAT - INFO - Using DEFAULT ui file from: /usr/share/qtvcp/panels/cam_align/cam_align.ui
2023-01-12 12:32:08,943 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for .qss in: /home/gene/linuxcnc/configs/GO704-5i25-7i76-camera/cam_align.qss
2023-01-12 12:32:08,943 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for .qss in: /usr/share/qtvcp/panels/cam_align/cam_align.qss
2023-01-12 12:32:08,943 - QTvcp.QTVCP.QT_PSTAT - INFO - No qss file found.
2023-01-12 12:32:08,943 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for .qrc in: /home/gene/linuxcnc/configs/GO704-5i25-7i76-camera/cam_align.qrc
2023-01-12 12:32:08,944 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for .qrc in: /usr/share/qtvcp/panels/cam_align/cam_align.qrc
2023-01-12 12:32:08,944 - QTvcp.QTVCP.QT_PSTAT - INFO - No qrc file found.
2023-01-12 12:32:08,944 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for resources.py in: /home/gene/linuxcnc/configs/GO704-5i25-7i76-camera/qtvcp/panels/resources.py
2023-01-12 12:32:08,944 - QTvcp.QTVCP.QT_PSTAT - INFO - No resources.py file found, no QRC file to compile one from.
2023-01-12 12:32:08,966 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for translation file in: /home/gene/linuxcnc/configs/GO704-5i25-7i76-camera/cam_align/languages/cam_align_en.qm
2023-01-12 12:32:08,966 - QTvcp.QTVCP.QT_PSTAT - DEBUG - Checking for translation file in: /usr/share/qtvcp/screens/cam_align/languages/cam_align_en.qm
2023-01-12 12:32:08,967 - QTvcp.QTVCP.QT_PSTAT - INFO - Using no translations, default system locale is: en
2023-01-12 12:32:08,968 - QTvcp - INFO - Building A VCP Panel with: Python 3
2023-01-12 12:32:08,968 - QTvcp - INFO - No handler file specified - using: /usr/share/qtvcp/panels/cam_align/cam_align_handler.py
2023-01-12 12:32:09,061 - QTvcp.QTVCP.QT_MAKEGUI - INFO - Qsettings file path: /home/gene/.config/QtVcp/cam_align.conf
2023-01-12 12:32:09,062 - QTvcp - DEBUG - Loading the handler file.
2023-01-12 12:32:09,062 -

Re: [Emc-developers] Broken master 06jan23

2023-01-11 Thread Chris Morley 
looks like you are using a command like this:

EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align

try changing it to:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} cam_align

From: gene heskett 
Sent: January 11, 2023 9:17 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

On 1/11/23 16:02, Chris Morley wrote:
> FileNotFoundError: [Errno 2] No such file or directory:
> '/usr/share/qtvcp/panels/-d/-d.ui'
>
> This is weird, it's picking up the -d as a panel name.
>
> Can you post a link to your INI file?
>
> Chris

I'll put it on my web page (in the sig) under the GO704 directory when I
get some food hidden. Half an hour maybe.
> 
> From: gene heskett 
> Sent: January 11, 2023 3:10 PM
> To: emc-developers@lists.sourceforge.net 
> 
> Subject: Re: [Emc-developers] Broken master 06jan23
>
> [QTvcp][CRITICAL]  Aborted from Error Dialog
>Qtvcp encountered an error.  The following information may be useful
> in troubleshooting:
> LinuxCNC Version  : 2.10.0-pre0-483-g47f4f07e2
>
> Traceback (most recent call last):
> File "/usr/bin/qtvcp", line 511, in 
>   APP = QTVCP()
> File "/usr/bin/qtvcp", line 304, in __init__
>   self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
> File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
> in __init__
>   window[pName].instance(os.path.join(path.PANELDIR , cmd, cmd+'.ui'))
> File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
> in instance
>   instance = uic.loadUi(filename, self)
> File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
> 226, in loadUi
>   return DynamicUILoader(package).loadUi(uifile, baseinstance,
> resource_suffix)
> File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
> line 72, in loadUi
>   return self.parse(filename, resource_suffix, basedir)
> File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
> 1013, in parse
>   document = parse(filename)
> File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in parse
>   tree.parse(source, parser)
> File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in parse
>   source = open(source, "rb")
> FileNotFoundError: [Errno 2] No such file or directory:
> '/usr/share/qtvcp/panels/-d/-d.ui'
>
>(qtvcp:503)
> 'QTVCP' object has no attribute 'panel'
> 'QTVCP' object has no attribute 'panel'
> Error in sys.excepthook:
> Traceback (most recent call last):
> File "/usr/bin/qtvcp", line 504, in excepthook
>   self.shutdown()
> File "/usr/bin/qtvcp", line 462, in shutdown
>   self.panel.window.sync_qsettings()
> AttributeError: 'QTVCP' object has no attribute 'panel'
>
> Original exception was:
> Traceback (most recent call last):
> File "/usr/bin/qtvcp", line 511, in 
>   APP = QTVCP()
> File "/usr/bin/qtvcp", line 304, in __init__
>   self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
> File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
> in __init__
>   window[pName].instance(os.path.join(path.PANELDIR , cmd, cmd+'.ui'))
> File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
> in instance
>   instance = uic.loadUi(filename, self)
> File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
> 226, in loadUi
>   return DynamicUILoader(package).loadUi(uifile, baseinstance,
> resource_suffix)
> File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
> line 72, in loadUi
>   return self.parse(filename, resource_suffix, basedir)
> File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
> 1013, in parse
>   document = parse(filename)
> File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in parse
>   tree.parse(source, parser)
> File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in parse
>   source = open(source, "rb")
> FileNotFoundError: [Errno 2] No such file or directory:
> '/usr/share/qtvcp/panels/-d/-d.ui'
>
>
>
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
> .

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use

Re: [Emc-developers] Broken master 06jan23

2023-01-11 Thread gene heskett 

On 1/11/23 16:18, gene heskett wrote:

On 1/11/23 16:02, Chris Morley wrote:

FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'

This is weird, it's picking up the -d as a panel name.

Can you post a link to your INI file?

Chris


I'll put it on my web page (in the sig) under the GO704 directory when I 
get some food hidden. Half an hour maybe.


Actually,I can occasionally walk and chew gum at the same time, done.


From: gene heskett 
Sent: January 11, 2023 3:10 PM
To: emc-developers@lists.sourceforge.net 


Subject: Re: [Emc-developers] Broken master 06jan23

[QTvcp][CRITICAL]  Aborted from Error Dialog
   Qtvcp encountered an error.  The following information may be useful
in troubleshooting:
LinuxCNC Version  : 2.10.0-pre0-483-g47f4f07e2

Traceback (most recent call last):
    File "/usr/bin/qtvcp", line 511, in 
  APP = QTVCP()
    File "/usr/bin/qtvcp", line 304, in __init__
  self.panel = qt_makepins.QTPanel(self.hal, PATH, window, 
opts.debug)

    File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
in __init__
  window[pName].instance(os.path.join(path.PANELDIR , cmd, 
cmd+'.ui'))

    File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
in instance
  instance = uic.loadUi(filename, self)
    File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
226, in loadUi
  return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
    File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
line 72, in loadUi
  return self.parse(filename, resource_suffix, basedir)
    File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
1013, in parse
  document = parse(filename)
    File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in 
parse

  tree.parse(source, parser)
    File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in 
parse

  source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'

   (qtvcp:503)
'QTVCP' object has no attribute 'panel'
'QTVCP' object has no attribute 'panel'
Error in sys.excepthook:
Traceback (most recent call last):
    File "/usr/bin/qtvcp", line 504, in excepthook
  self.shutdown()
    File "/usr/bin/qtvcp", line 462, in shutdown
  self.panel.window.sync_qsettings()
AttributeError: 'QTVCP' object has no attribute 'panel'

Original exception was:
Traceback (most recent call last):
    File "/usr/bin/qtvcp", line 511, in 
  APP = QTVCP()
    File "/usr/bin/qtvcp", line 304, in __init__
  self.panel = qt_makepins.QTPanel(self.hal, PATH, window, 
opts.debug)

    File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
in __init__
  window[pName].instance(os.path.join(path.PANELDIR , cmd, 
cmd+'.ui'))

    File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
in instance
  instance = uic.loadUi(filename, self)
    File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
226, in loadUi
  return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
    File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
line 72, in loadUi
  return self.parse(filename, resource_suffix, basedir)
    File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
1013, in parse
  document = parse(filename)
    File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in 
parse

  tree.parse(source, parser)
    File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in 
parse

  source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.


Cheers, Gene Heskett.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-11 Thread gene heskett 

On 1/11/23 16:02, Chris Morley wrote:

FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'

This is weird, it's picking up the -d as a panel name.

Can you post a link to your INI file?

Chris


I'll put it on my web page (in the sig) under the GO704 directory when I 
get some food hidden. Half an hour maybe.


From: gene heskett 
Sent: January 11, 2023 3:10 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

[QTvcp][CRITICAL]  Aborted from Error Dialog
   Qtvcp encountered an error.  The following information may be useful
in troubleshooting:
LinuxCNC Version  : 2.10.0-pre0-483-g47f4f07e2

Traceback (most recent call last):
File "/usr/bin/qtvcp", line 511, in 
  APP = QTVCP()
File "/usr/bin/qtvcp", line 304, in __init__
  self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
in __init__
  window[pName].instance(os.path.join(path.PANELDIR , cmd, cmd+'.ui'))
File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
in instance
  instance = uic.loadUi(filename, self)
File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
226, in loadUi
  return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
line 72, in loadUi
  return self.parse(filename, resource_suffix, basedir)
File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
1013, in parse
  document = parse(filename)
File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in parse
  tree.parse(source, parser)
File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in parse
  source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'

   (qtvcp:503)
'QTVCP' object has no attribute 'panel'
'QTVCP' object has no attribute 'panel'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/bin/qtvcp", line 504, in excepthook
  self.shutdown()
File "/usr/bin/qtvcp", line 462, in shutdown
  self.panel.window.sync_qsettings()
AttributeError: 'QTVCP' object has no attribute 'panel'

Original exception was:
Traceback (most recent call last):
File "/usr/bin/qtvcp", line 511, in 
  APP = QTVCP()
File "/usr/bin/qtvcp", line 304, in __init__
  self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
in __init__
  window[pName].instance(os.path.join(path.PANELDIR , cmd, cmd+'.ui'))
File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
in instance
  instance = uic.loadUi(filename, self)
File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
226, in loadUi
  return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
line 72, in loadUi
  return self.parse(filename, resource_suffix, basedir)
File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
1013, in parse
  document = parse(filename)
File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in parse
  tree.parse(source, parser)
File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in parse
  source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-11 Thread Chris Morley 
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'

This is weird, it's picking up the -d as a panel name.

Can you post a link to your INI file?

Chris

From: gene heskett 
Sent: January 11, 2023 3:10 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

[QTvcp][CRITICAL]  Aborted from Error Dialog
  Qtvcp encountered an error.  The following information may be useful
in troubleshooting:
LinuxCNC Version  : 2.10.0-pre0-483-g47f4f07e2

Traceback (most recent call last):
   File "/usr/bin/qtvcp", line 511, in 
 APP = QTVCP()
   File "/usr/bin/qtvcp", line 304, in __init__
 self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
   File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
in __init__
 window[pName].instance(os.path.join(path.PANELDIR , cmd, cmd+'.ui'))
   File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
in instance
 instance = uic.loadUi(filename, self)
   File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
226, in loadUi
 return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
   File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
line 72, in loadUi
 return self.parse(filename, resource_suffix, basedir)
   File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
1013, in parse
 document = parse(filename)
   File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in parse
 tree.parse(source, parser)
   File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in parse
 source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'

  (qtvcp:503)
'QTVCP' object has no attribute 'panel'
'QTVCP' object has no attribute 'panel'
Error in sys.excepthook:
Traceback (most recent call last):
   File "/usr/bin/qtvcp", line 504, in excepthook
 self.shutdown()
   File "/usr/bin/qtvcp", line 462, in shutdown
 self.panel.window.sync_qsettings()
AttributeError: 'QTVCP' object has no attribute 'panel'

Original exception was:
Traceback (most recent call last):
   File "/usr/bin/qtvcp", line 511, in 
 APP = QTVCP()
   File "/usr/bin/qtvcp", line 304, in __init__
 self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
   File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 96,
in __init__
 window[pName].instance(os.path.join(path.PANELDIR , cmd, cmd+'.ui'))
   File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 382,
in instance
 instance = uic.loadUi(filename, self)
   File "/usr/lib/python3/dist-packages/PyQt5/uic/__init__.py", line
226, in loadUi
 return DynamicUILoader(package).loadUi(uifile, baseinstance,
resource_suffix)
   File "/usr/lib/python3/dist-packages/PyQt5/uic/Loader/loader.py",
line 72, in loadUi
 return self.parse(filename, resource_suffix, basedir)
   File "/usr/lib/python3/dist-packages/PyQt5/uic/uiparser.py", line
1013, in parse
 document = parse(filename)
   File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 1197, in parse
 tree.parse(source, parser)
   File "/usr/lib/python3.7/xml/etree/ElementTree.py", line 587, in parse
 source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory:
'/usr/share/qtvcp/panels/-d/-d.ui'



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-11 Thread gene heskett 
est_panel:
total 56
-rw-r--r-- 1 root root  7074 Jan 10 12:38 test_panel_handler.py
-rw-r--r-- 1 root root 46374 Jan 10 12:38 test_panel.ui

/usr/share/qtvcp/panels/test_probe:
total 12
-rw-r--r-- 1 root root 2528 Jan 10 12:38 test_probe_handler.py
-rw-r--r-- 1 root root 4828 Jan 10 12:38 test_probe.ui

/usr/share/qtvcp/panels/tool_dialog:
total 8
-rw-r--r-- 1 root root 2994 Jan 10 12:38 tool_dialog_handler.py
-rw-r--r-- 1 root root 2159 Jan 10 12:38 tool_dialog.ui

/usr/share/qtvcp/panels/vismach_5axis_gantry:
total 8
-rw-r--r-- 1 root root 2068 Jan 10 12:38 vismach_5axis_gantry_handler.py
-rw-r--r-- 1 root root 1252 Jan 10 12:38 vismach_5axis_gantry.ui

/usr/share/qtvcp/panels/vismach_fanuc_200f:
total 8
-rw-r--r-- 1 root root 2068 Jan 10 12:38 vismach_fanuc_200f_handler.py
-rw-r--r-- 1 root root 1252 Jan 10 12:38 vismach_fanuc_200f.ui

/usr/share/qtvcp/panels/vismach_millturn:
total 8
-rw-r--r-- 1 root root 2064 Jan 10 12:38 vismach_millturn_handler.py
-rw-r--r-- 1 root root 1252 Jan 10 12:38 vismach_millturn.ui

/usr/share/qtvcp/panels/vismach_mill_xyz:
total 8
-rw-r--r-- 1 root root 2064 Jan 10 12:38 vismach_mill_xyz_handler.py
-rw-r--r-- 1 root root 1252 Jan 10 12:38 vismach_mill_xyz.ui

/usr/share/qtvcp/panels/vismach_scara:
total 8
-rw-r--r-- 1 root root 2063 Jan 10 12:38 vismach_scara_handler.py
-rw-r--r-- 1 root root 1252 Jan 10 12:38 vismach_scara.ui
gene@GO704:~/linuxcnc/configs$

It indeed is not there. What package might that stuff be in? This has a 
different flavor, and I hope all this noise is useful.


Thanks Chris. take care & stay well.




Chris


From: gene heskett 
Sent: January 7, 2023 11:27 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

And of course the camera on the go704 doesn't work making qt upset at
init time for about 40 seconds of . spew. It only worked for 3
or 4 days a couple/three months back. With cheese it Just Works. This is
upsetting, it works for 2 or 4 upgrades, then disappears again for 6
months until I start pestering the list again.

I'm as tired of that as you all are reading about my camera woes.

It never works long enough for me to get the align kit from our wiki
fully calibrated. Yet it works with cheese on any machine I plug it into.



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-11 Thread Chris Morley 
I looked at the qt camview problem. I have an installed version of linuxcnc and 
it is broken there.
Strangley I can not find where it got broken in the source.
The fix is easy
In camview.py need to change to these lines.

try:
import cv2 as CV
DEFAULT_API = CV.CAP_ANY
except:
LOG.error('Qtvcp Error with camview - is python3-opencv installed?')
LIB_GOOD = False
DEFAULT_API = 0 # CV.CAP_ANY

Chris


From: gene heskett 
Sent: January 7, 2023 11:27 PM
To: emc-developers@lists.sourceforge.net 
Subject: Re: [Emc-developers] Broken master 06jan23

And of course the camera on the go704 doesn't work making qt upset at
init time for about 40 seconds of . spew. It only worked for 3
or 4 days a couple/three months back. With cheese it Just Works. This is
upsetting, it works for 2 or 4 upgrades, then disappears again for 6
months until I start pestering the list again.

I'm as tired of that as you all are reading about my camera woes.

It never works long enough for me to get the align kit from our wiki
fully calibrated. Yet it works with cheese on any machine I plug it into.



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-09 Thread Sebastian Kuzminsky 
I believe a root cause of this breakage was the difficulty of merging 
the docs from 2.9 to master.


The merge resulted in a bunch of awkward conflicts.  As always, the 
conflicts were caused by files being changed in the same place in both 
branches.  In this case, the conflicts came from a couple of misplaced 
commits back in November:


8d07575ef31c0d99cd9601aabb90e5d59cea9ac5
c1668e209290693a086f99c039271a22bc5e9061

Those were big translation-motivated changes that mistakenly went into 
master, when they should have gone into 2.9.  (You can see that those 
went into master instead of 2.9 using `git branch -a --contains $SHA` to 
list all branches that have those commits in their history.)


Later, similar but slightly different translaton-motivated changes went 
into 2.9, and the following merge stopped on the conflicts.


I think we now have a consensus in place that, generally, changes to 
.adoc files go in 2.9 (unless they're describing new behavior in master, 
of course), and all changes to .po/.pot files without exceptions go in 
master.


Had we had this consensus in place back in November, the present merge 
problem would have been much smaller.


Perhaps we should have a Github Action that warns on .adoc changes in 
master or .po/.pot changes in 2.9?



--
Sebastian Kuzminsky


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-09 Thread Sebastian Kuzminsky 

On 1/8/23 11:38, Jeff Epler wrote:


On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:


I disagree with having to use pull requests for devs. (if I understood that 
right)
We already have problems getting pull request reviewed and aproved.


I will not change this without consensus.

In the long run, though, successful projects are able to review and
merge (or, when necessary, reject) pull requests in a timely fashion. In
this respect, our project's health is poor.

I think that the way that "core developers" can simply ignore the pull
request process if they choose to do so contributes to this. These core
developers can both bypass this speed bump if they choose, and ignore
pull requests from others even where their expertise can accelerate the
PR's inclusion.

In other projects where I participate (incuding my work, which is all
public on github) working via pull request is the default.  It works
well, and by numbers I believe that most PRs come from external
contributors but admittedly "the it works" depends on having ~4.5 paid
FTEs on the project.  A small number of reviewers are able to make short
work of most PRs, especially when there's a culture of doing it. I spend
maybe 5% of my time reviewing PRs, while some of my colleagues probably
spend substantially more.


My work experience is varied.  I've worked on larger teams where 
everything went through the PR process (and folks treated new PRs as 
high-priority interrupts), and on smaller teams where we all pushed 
directly to the long-lived branches without review.


The ubiquitous use of PRs is beneficial for code quality and for team 
communication, but it does introduce extra work, sometimes a significant 
amount.


Some of the extra work falls on the folks reviewing PRs, but it's 
important that the person *opening* the PR shoulder some of this burden 
too: by writing small, clean commits with good descriptive commit 
messages, and a good message in the PR explaining the high-level purpose 
of the whole branch.


This is good practice anyway, and is part of our project guidelines, 
though I sometimes get lazy and don't follow it:




I think beyond a certain project size the PR process becomes worth it. 
I think we're well beyond that project size, and I would like to see us 
at least try this.


If we can't make ourselves review each others' PRs in a timely fashion 
the experiment will have failed and we can go back to the current "push 
at will" workflow.



--
Sebastian Kuzminsky



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Chris Morley 
Thank you Jeff.
Chris

From: Jeff Epler 
Sent: January 9, 2023 3:06 AM
To: EMC developers 
Subject: Re: [Emc-developers] Broken master 06jan23

Thank you all for the discussion.

I merged #2251, closed #2250, and in a moment I'll "unlock" the master
branch.

Take care,
Jeff


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Alec Ari via Emc-developers 
Yes it is! uvcvideo! Thanks!

Alec

On Sunday, January 8, 2023 at 06:12:33 PM UTC, gene heskett 
 wrote: 





On 1/8/23 01:42, Alec Ari via Emc-developers wrote:
> Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's 
> like 90% of the way there, I have an installer and everything, just need to 
> test it on CNC hardware.. Are the cameras you guys use for camview fall under 
> UVC (USB_VIDEO_CLASS / uvcvideo) or something else? Trying to avoid 500+ 
> kernel modules lol.
> 
let me see if I can find what dmesg says about this one. brb.


[487365.330077] uvcvideo: Found UVC 1.00 device USB 2.0 PC Camera 
(058f:5608)

Is that helpful. 


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Jeff Epler 
Thank you all for the discussion.

I merged #2251, closed #2250, and in a moment I'll "unlock" the master
branch.

Take care,
Jeff


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread chris morley 



On 2023-01-08 10:38, Jeff Epler wrote:

[Chris requested that I explicitly respond to each part of his message.
I will do so even though I have little that is constructive to add]


Thank you, the discussion is important for everyone I think.


These things seem like radical responses to an uncomon mistake.
This will be only be the second time in about 15 years something like this 
happened.
You're right, in that I would like to use this as an opportunity to move
the project in a direction I think is good. The term "radical" is
charged, of course. From my point of view, I'm promoting styles of
working that are what I do everyday and which I perceive as working
well.


The word radical was not intended to be charged, feel free to use 'rash'

I was asking questions and giving my opinion.

We can't move forward without discussion - I am interested in your and 
others point of view.



If you want to talk merge strategies see my other maillist talk.
The jest of is - why merge released branches into master at all.

As my colleague said, the idea to end the project's long-standing policy
of merging from stable to main seems like a "radical [response] to an
uncomon mistake."


Yes It is radical change to current norms but not without precedence.

IIRC with cvs , we did not merge branch upto branch, only feature branch 
to branch.


Also my suggestion was before the problem occurred - so not a radical 
_response_ :)


Chris



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Steffen Möller 



> Gesendet: Sonntag, 08. Januar 2023 um 03:34 Uhr
> Von: "Jeff Epler" 
> An: "EMC developers" 
> Betreff: Re: [Emc-developers] Broken master 06jan23
>
> Thanks for speaking up about the problem as soon as you realized it.
> I have temporarily locked the "master" branch on github until this
> problem is resolved.

+1

> I understand that the idea of force-pushing master to 1d836df^ before
> the problem was discussed and dismissed (on IRC?). I did not see this
> discussion.
>
> Seb and I have each prepared PRs that approach fixing the problem. I
> have a third, non-pull-request suggestion.
>
> https://github.com/LinuxCNC/linuxcnc/pull/2250 --
>
> Seb re-cherry-picks work from 2.9, excluding doc work that did not apply
> cleanly. This would mean the doc work is lost from master if nobody else
> steps up to cherry-pick and pull request the changes to master too:

All the changes to the documentation that is not describing new functionality 
should have gone to 2.9, so we improve the upcoming release to the best of our 
abilities.
Any loss of that work likely stops the influx of improvements to 2.9.

> https://github.com/LinuxCNC/linuxcnc/pull/2251 --
> I merge 2.9 into 1d836df^ (git notation for "the commit before 1d836df),
> doing my best to take the better side of each conflict in the
> documentation (usually it was pretty clear; a total of 4 files had
> conflicts), then merge 1d836df with the "ours" strategy (to effectively
> discard its version of the changes), and then cherry-pick commits
> subsequent to 1d836df, only one of which introduced changes.  This
> hopefully catches the majority of doc work, but I merely selected one
> side or the other of the doc changes, rather than carefully merging them
> word by word.

This sounds very reasonable. What does that do to future changes to the 2.9 
documentation? Anyway - four files sounds much like a non-issue.

> The third suggestion is to use this as the moment to adopt the github
> standard "main" branch name, instead of the deprecated branch name
> "master". I would prepare a new branch similar to #2251, but NOT merge
> 1d836df in it, and push this as "main".

I think I prefer "devel". Also since this encourages the submission to 2.9.

> Besides fixing things in one of these ways, I think we should strongly
> consider using github "branch protection", so that any change to main
> and a "branch that looks like a version number" must go through the pull
> request process.  This doesn't catch all problems, and it would require
> folks to step up as pull request reviewers, but it might have avoided
> this problem.

PRs imho are very much a means of communication that I would miss if we would 
not have them.

Thank you, Jeff!
Steffen

> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Chris Morley 
Yes Andy I knew that from last time and I think it should have been stated this 
time.
But I left it open that maybe there was some other technical reason/advantage.
I am also opposed to doing a bunch of changes - with possible errors added just 
to change a word that is out of vogue.
Nothing wrong with asking the question again I suppose - maybe the project has 
changed it's mind.
But I don't think so.

Chris

From: andy pugh 
Sent: January 8, 2023 7:13 PM
To: EMC developers 
Subject: Re: [Emc-developers] Broken master 06jan23

On Sun, 8 Jan 2023 at 04:10, Chris Morley  wrote:
>
> Why would we change to 'main' ?

Github have a problem with the word "master"

I think that they are misguided in this particular case, but at the
same time I think that "main" is a clearer name than "master". Though
perhaps "dev" would be better still.

--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread andy pugh 
On Sun, 8 Jan 2023 at 04:10, Chris Morley  wrote:
>
> Why would we change to 'main' ?

Github have a problem with the word "master"

I think that they are misguided in this particular case, but at the
same time I think that "main" is a clearer name than "master". Though
perhaps "dev" would be better still.

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Jeff Epler 
[Chris requested that I explicitly respond to each part of his message.
I will do so even though I have little that is constructive to add]

On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:
> Why would we change to 'main' ?
> How does the name change fix merge problems?
> It does create doc and web reference problems.

In the long run, it's better to match standard github practice. However,
I agree that we need not do this right now. It just seemed like a nice hack
to avoid re-winding the master branch while still removing the bad merge
from project history.

> I disagree with having to use pull requests for devs. (if I understood that 
> right)
> We already have problems getting pull request reviewed and aproved.

I will not change this without consensus.

In the long run, though, successful projects are able to review and
merge (or, when necessary, reject) pull requests in a timely fashion. In
this respect, our project's health is poor.

I think that the way that "core developers" can simply ignore the pull
request process if they choose to do so contributes to this. These core
developers can both bypass this speed bump if they choose, and ignore
pull requests from others even where their expertise can accelerate the
PR's inclusion.

In other projects where I participate (incuding my work, which is all
public on github) working via pull request is the default.  It works
well, and by numbers I believe that most PRs come from external
contributors but admittedly "the it works" depends on having ~4.5 paid
FTEs on the project.  A small number of reviewers are able to make short
work of most PRs, especially when there's a culture of doing it. I spend
maybe 5% of my time reviewing PRs, while some of my colleagues probably
spend substantially more.

(And FWIW thanks for the work you did reviewing PRs over the last year,
I see you commented on or reviewed more than a few)

However, it's impossible to single-handedly establish such a culture
when a different culture is entrenched. The project would have to want
to change.

> These things seem like radical responses to an uncomon mistake.
> This will be only be the second time in about 15 years something like this 
> happened.

You're right, in that I would like to use this as an opportunity to move
the project in a direction I think is good. The term "radical" is
charged, of course. From my point of view, I'm promoting styles of
working that are what I do everyday and which I perceive as working
well.

> If you want to talk merge strategies see my other maillist talk.
> The jest of is - why merge released branches into master at all.

As my colleague said, the idea to end the project's long-standing policy
of merging from stable to main seems like a "radical [response] to an
uncomon mistake."

I do not require a response to any of these points.

Jeff


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread gene heskett 

On 1/8/23 01:42, Alec Ari via Emc-developers wrote:

Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's 
like 90% of the way there, I have an installer and everything, just need to 
test it on CNC hardware.. Are the cameras you guys use for camview fall under 
UVC (USB_VIDEO_CLASS / uvcvideo) or something else? Trying to avoid 500+ kernel 
modules lol.


let me see if I can find what dmesg says about this one. brb.

[487365.102711] usb 1-1.3: new high-speed USB device number 5 using ehci-pci
[487365.319448] usb 1-1.3: New USB device found, idVendor=058f, 
idProduct=5608, bcdDevice= 0.03
[487365.319450] usb 1-1.3: New USB device strings: Mfr=3, Product=1, 
SerialNumber=0

[487365.319451] usb 1-1.3: Product: USB 2.0 PC Camera
[487365.319452] usb 1-1.3: Manufacturer: Alcor Micro, Corp.
[487365.330077] uvcvideo: Found UVC 1.00 device USB 2.0 PC Camera 
(058f:5608)
[487365.336661] input: USB 2.0 PC Camera: USB 2.0 PC C as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input28


Is that helpful. I'm under the impression its a qtvcp problem. that is 
what pukes all over itself when LinuxCNC is launched. One thing it 
definitely doesn't do is export the video over an ssh -Y connection, I 
have to goto the computer running the machine to see it when it does 
work, which it hasn't since last summer 2 or 3 days after I posted my 
success msg.


My theory is that Murphy saw the message, and broke it again as soon as 
he could.  He seems to have taken up residence here, even drinking my 
last beer once in a while...



Thanks!

Alec

On Saturday, January 7, 2023 at 11:28:58 PM UTC, gene heskett 
 wrote:

And of course the camera on the go704 doesn't work making qt upset at
init time for about 40 seconds of . spew. It only worked for 3
or 4 days a couple/three months back. With cheese it Just Works. This is
upsetting, it works for 2 or 4 upgrades, then disappears again for 6
months until I start pestering the list again.

I'm as tired of that as you all are reading about my camera woes.

It never works long enough for me to get the align kit from our wiki
fully calibrated. Yet it works with cheese on any machine I plug it into.

Thank you.

Take care, stay warm & well Dewey.

Cheers, Gene Heskett.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread chris morley 



On 2023-01-08 06:43, Jeff Epler wrote:

On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:

AFAICT the code (I didn't look at the docs mind you) is fixed.
What is actually broken in master now?
What are we trying to fix? The history?

Content of changes in 2.9 were discarded, instead of being added to
master. This includes documentation fixes. I hope you will respect that
just like code changes, documentation changes are valuable contributions
to this project.

For a list of changes between master and jepler/alternate-bad-merge-fix
see https://gist.github.com/jepler/86390ab9be17babf0349a1a8c5198e2e --
these represent changes in 2.9 that were NOT taken by the bad merge
commit but probably should have been.

The majority are documentation changes (which does not mean they are
lower value than code changes). That said, a lot of code changes were
discarded too.  For instance, an entire config is missing.  As far as
source code goes it looks like bugfixes to gremlin, qtvcp, and others
are missing.  To get an idea this "git diff --stat" summary of
differences in lib/ src/ bin/ and scripts/ provides an overview:


I'm not sure where you got the idea I don't think docs are important. 
I've done a lot of docs myself. I only said I hadn't checked them.


Thank you for showing me there was a lot more changes then i was aware of.

You didn't address my other comments.


Chris



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-08 Thread Jeff Epler 
On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:
> AFAICT the code (I didn't look at the docs mind you) is fixed.
> What is actually broken in master now?
> What are we trying to fix? The history?

Content of changes in 2.9 were discarded, instead of being added to
master. This includes documentation fixes. I hope you will respect that
just like code changes, documentation changes are valuable contributions
to this project.

For a list of changes between master and jepler/alternate-bad-merge-fix
see https://gist.github.com/jepler/86390ab9be17babf0349a1a8c5198e2e --
these represent changes in 2.9 that were NOT taken by the bad merge
commit but probably should have been.

The majority are documentation changes (which does not mean they are
lower value than code changes). That said, a lot of code changes were
discarded too.  For instance, an entire config is missing.  As far as
source code goes it looks like bugfixes to gremlin, qtvcp, and others
are missing.  To get an idea this "git diff --stat" summary of
differences in lib/ src/ bin/ and scripts/ provides an overview:

 lib/python/glnav.py |   4 +-
 lib/python/qtvcp/qt_pstat.py|   5 +-
 .../qtvcp/widgets/camview_widget.py |   4 +-
 lib/python/qtvcp/widgets/round_gauge.py |  13 +-
 .../qtvcp/widgets/round_progress.py |   2 +-
 lib/python/vismach.py   |   2 +-
 scripts/linuxcnc.in |   4 +-
 src/Makefile|   3 +-
 src/emc/canterp/Submakefile |  16 +-
 src/emc/rs274ngc/interp_base.cc |  29 +-
 src/emc/task/emctask.cc |   4 +
 .../axis/extensions/emcmodule.cc|  22 +-
 src/emc/usr_intf/gmoccapy/getiniinfo.py |  12 +
 .../usr_intf/gmoccapy/gmoccapy.glade| 255 +
 src/emc/usr_intf/gmoccapy/gmoccapy.py   |  76 +++-
 .../usr_intf/gmoccapy/notification.py   |   7 +-
 .../usr_intf/gmoccapy/release_notes.txt |  14 +-
 src/hal/components/axistest.comp|   2 +-
 src/hal/components/bldc.comp| 161 -
 src/hal/components/feedcomp.comp|   6 +-
 src/hal/components/gantry.comp  |  34 +-
 src/hal/components/lut5.comp|  14 +-
 src/hal/components/moveoff.comp | 146 
 src/hal/components/multiswitch.comp |   7 +-
 src/hal/components/panelui.c|   2 +-
 src/hal/components/plasmac.comp |  10 +-
 src/hal/components/spindle.comp |  84 ++---
 src/hal/components/xyzab_tdr_kins.comp  | 257 ++
 src/hal/user_comps/vismach/Submakefile  |   3 +-
 .../user_comps/vismach/xyzab-tdr-gui.py | 225 
 src/libnml/os_intf/_sem.c   |   2 +-
 src/rtapi/uspace_rtapi_app.cc   |   4 +-

Jeff


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-07 Thread Alec Ari via Emc-developers 
Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's 
like 90% of the way there, I have an installer and everything, just need to 
test it on CNC hardware.. Are the cameras you guys use for camview fall under 
UVC (USB_VIDEO_CLASS / uvcvideo) or something else? Trying to avoid 500+ kernel 
modules lol.

Thanks!

Alec

On Saturday, January 7, 2023 at 11:28:58 PM UTC, gene heskett 
 wrote: 

And of course the camera on the go704 doesn't work making qt upset at 
init time for about 40 seconds of . spew. It only worked for 3 
or 4 days a couple/three months back. With cheese it Just Works. This is 
upsetting, it works for 2 or 4 upgrades, then disappears again for 6 
months until I start pestering the list again.

I'm as tired of that as you all are reading about my camera woes.

It never works long enough for me to get the align kit from our wiki 
fully calibrated. Yet it works with cheese on any machine I plug it into.

Thank you.

Take care, stay warm & well Dewey.

Cheers, Gene Heskett.


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-07 Thread Chris Morley 
AFAICT the code (I didn't look at the docs mind you) is fixed.
What is actually broken in master now?
What are we trying to fix? The history?

Why would we change to 'main' ?
How does the name change fix merge problems?
It does create doc and web reference problems.

I disagree with having to use pull requests for devs. (if I understood that 
right)
We already have problems getting pull request reviewed and aproved.

These things seem like radical responses to an uncomon mistake.
This will be only be the second time in about 15 years something like this 
happened.

If you want to talk merge strategies see my other maillist talk.
The jest of is - why merge released branches into master at all.

Thanks
Chris


From: Jeff Epler 
Sent: January 8, 2023 2:34 AM
To: EMC developers 
Subject: Re: [Emc-developers] Broken master 06jan23

Thanks for speaking up about the problem as soon as you realized it.
I have temporarily locked the "master" branch on github until this
problem is resolved.

I understand that the idea of force-pushing master to 1d836df^ before
the problem was discussed and dismissed (on IRC?). I did not see this
discussion.

Seb and I have each prepared PRs that approach fixing the problem. I
have a third, non-pull-request suggestion.

https://github.com/LinuxCNC/linuxcnc/pull/2250 --

Seb re-cherry-picks work from 2.9, excluding doc work that did not apply
cleanly. This would mean the doc work is lost from master if nobody else
steps up to cherry-pick and pull request the changes to master too:

https://github.com/LinuxCNC/linuxcnc/pull/2251 --
I merge 2.9 into 1d836df^ (git notation for "the commit before 1d836df),
doing my best to take the better side of each conflict in the
documentation (usually it was pretty clear; a total of 4 files had
conflicts), then merge 1d836df with the "ours" strategy (to effectively
discard its version of the changes), and then cherry-pick commits
subsequent to 1d836df, only one of which introduced changes.  This
hopefully catches the majority of doc work, but I merely selected one
side or the other of the doc changes, rather than carefully merging them
word by word.


The third suggestion is to use this as the moment to adopt the github
standard "main" branch name, instead of the deprecated branch name
"master". I would prepare a new branch similar to #2251, but NOT merge
1d836df in it, and push this as "main".


Besides fixing things in one of these ways, I think we should strongly
consider using github "branch protection", so that any change to main
and a "branch that looks like a version number" must go through the pull
request process.  This doesn't catch all problems, and it would require
folks to step up as pull request reviewers, but it might have avoided
this problem.


I'll check back on this thread as well as the developers IRC channel to
see if a consensus develops and then implement it.  Because this is
blocking ongoing work it's problably better to resolve it in a timely
fashion than to spend a long time figuring out the best possible
resolution.

It sounds like Seb is not available for the rest of the week-end fwiw.

Jeff


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-07 Thread Jeff Epler 
Thanks for speaking up about the problem as soon as you realized it.
I have temporarily locked the "master" branch on github until this
problem is resolved.

I understand that the idea of force-pushing master to 1d836df^ before
the problem was discussed and dismissed (on IRC?). I did not see this
discussion.

Seb and I have each prepared PRs that approach fixing the problem. I
have a third, non-pull-request suggestion.

https://github.com/LinuxCNC/linuxcnc/pull/2250 --

Seb re-cherry-picks work from 2.9, excluding doc work that did not apply
cleanly. This would mean the doc work is lost from master if nobody else
steps up to cherry-pick and pull request the changes to master too:

https://github.com/LinuxCNC/linuxcnc/pull/2251 --
I merge 2.9 into 1d836df^ (git notation for "the commit before 1d836df),
doing my best to take the better side of each conflict in the
documentation (usually it was pretty clear; a total of 4 files had
conflicts), then merge 1d836df with the "ours" strategy (to effectively
discard its version of the changes), and then cherry-pick commits
subsequent to 1d836df, only one of which introduced changes.  This
hopefully catches the majority of doc work, but I merely selected one
side or the other of the doc changes, rather than carefully merging them
word by word.


The third suggestion is to use this as the moment to adopt the github
standard "main" branch name, instead of the deprecated branch name
"master". I would prepare a new branch similar to #2251, but NOT merge
1d836df in it, and push this as "main".


Besides fixing things in one of these ways, I think we should strongly
consider using github "branch protection", so that any change to main
and a "branch that looks like a version number" must go through the pull
request process.  This doesn't catch all problems, and it would require
folks to step up as pull request reviewers, but it might have avoided
this problem.


I'll check back on this thread as well as the developers IRC channel to
see if a consensus develops and then implement it.  Because this is
blocking ongoing work it's problably better to resolve it in a timely
fashion than to spend a long time figuring out the best possible
resolution.

It sounds like Seb is not available for the rest of the week-end fwiw.

Jeff


___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Broken master 06jan23

2023-01-07 Thread gene heskett 

On 1/7/23 11:03, Dewey Garrett wrote:

Yesterday (06Jan2023), I made a bad commit that breaks
master branch updates from 2.9.

I've notified key developers with more git experience
and suggest that users of git checkouts for the *master*
branch defer updates until someone figures out how to
fix it.

Other branches (2.9 for instance) are ok as far as
i can tell.

Sorry for my mistake,
dewey


My rpi4 is updateing its git pull 4x a day Dewey, and is not showing a 
problem. So I updated it to master from the buildbot for armhf,
Get:1 http://buildbot.linuxcnc.org buster/master-rtpreempt armhf 
linuxcnc-uspace-dev armhf 1:2.10.0~pre0.457.g3d3bdb726 [299 kB]
Get:2 http://buildbot.linuxcnc.org buster/master-rtpreempt armhf 
linuxcnc-uspace-dbgsym armhf 1:2.10.0~pre0.457.g3d3bdb726 [12.2 MB]
Get:3 http://buildbot.linuxcnc.org buster/master-rtpreempt armhf 
linuxcnc-doc-en all 1:2.10.0~pre0.457.g3d3bdb726 [26.3 MB] 

Get:4 http://buildbot.linuxcnc.org buster/master-rtpreempt armhf 
linuxcnc-uspace armhf 1:2.10.0~pre0.457.g3d3bdb726 [21.2 MB] 


Fetched 60.1 MB in 1min 2s (963 kB/s)

seems to run ok. Must be the fastest fix in the west. ;o)>

However, after this update on my go704, the spindle of my go704 will not 
run, I presume because the default spindle is no longer spindle[0]?  I 
don't recall editing the .ini to match the new multispindle stuffs.


Uodated all 4 machines. The only problem after I had labeled all the 
SPINDLE stuff to SPINDLE_0 in both the .ini and .hal files on the go704,
is that there is no longer a default spindle speed by a click on the 
direction button despite there being a DEFAULT_SPINDLE_0_SPEED setting 
of 100 in the .ini file. So it now takes a click on the + button to 
actually start the SPINDLE_0. At 100 revs. The lathe(armhf-rpi4 managed) 
works normal, tlm is in mid modification of power control and has no 
motor or spindle power atm, the 6040 also works normally. Both the lathe 
and the 6040's spindles are run by vfd's. The lathe has spinx1 hardware 
interface, the 6040 an rs485.


And of course the camera on the go704 doesn't work making qt upset at 
init time for about 40 seconds of . spew. It only worked for 3 
or 4 days a couple/three months back. With cheese it Just Works. This is 
upsetting, it works for 2 or 4 upgrades, then disappears again for 6 
months until I start pestering the list again.


I'm as tired of that as you all are reading about my camera woes.

It never works long enough for me to get the align kit from our wiki 
fully calibrated. Yet it works with cheese on any machine I plug it into.


Thank you.

Take care, stay warm & well Dewey.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers