Greetings;
On wheezy, running the newest r14.0.2 TDE I think, from the looks of the update done recently.
I have several other machines, all running a wheezy sourced release, customized with a special pinned rtai patched kernel because the main application they run is linuxcnc.
But they are running, generally, a simple XFCE interface. And that program runs as well as its configured to do, something I am in the middle of re-writing in an effort to fine tune the machines performance.
One of the things I like to do is configure check from this nice comfy office chair is by running it over an ssh -Y login from here.
But that has always been a problem child, a puzzling one because neither machine has in its environment, a setting for colors called FORGROUND or BACKGROUND.
But its a showstopper, and only for linuxcnc, which contains tcl scripting that bails out of the program before the gui can be drawn on this screen. Other programs which use x run just fine, at least the ones I have tried. That includes gimp, but that machine has no gimp loadable files on it.
pasted from the login screen:
_tkinter.TclError: unknown color name "BACKGROUND" Shutting down and cleaning up LinuxCNC...
If it ever gets past that, it will do the same for the FOREGROUND color. BTDT but this machine was running an older ubuntu at the time. And its been long enough since I hacked around it that today I haven't a clue what I did then.
Does anybody have any suggestions on how to deal with this?
FWIW, the "simulated machine" version of that software runs just fine on this machine.
Cheers, Gene Heskett
On Friday 11 September 2015, Gene Heskett wrote:
Greetings;
On wheezy, running the newest r14.0.2 TDE I think, from the looks of the update done recently.
I have several other machines, all running a wheezy sourced release, customized with a special pinned rtai patched kernel because the main application they run is linuxcnc.
But they are running, generally, a simple XFCE interface. And that program runs as well as its configured to do, something I am in the middle of re-writing in an effort to fine tune the machines performance.
One of the things I like to do is configure check from this nice comfy office chair is by running it over an ssh -Y login from here.
But that has always been a problem child, a puzzling one because neither machine has in its environment, a setting for colors called FORGROUND or BACKGROUND.
But its a showstopper, and only for linuxcnc, which contains tcl scripting that bails out of the program before the gui can be drawn on this screen. Other programs which use x run just fine, at least the ones I have tried. That includes gimp, but that machine has no gimp loadable files on it.
pasted from the login screen:
_tkinter.TclError: unknown color name "BACKGROUND" Shutting down and cleaning up LinuxCNC...
If it ever gets past that, it will do the same for the FOREGROUND color. BTDT but this machine was running an older ubuntu at the time. And its been long enough since I hacked around it that today I haven't a clue what I did then.
Does anybody have any suggestions on how to deal with this?
FWIW, the "simulated machine" version of that software runs just fine on this machine.
Cheers, Gene Heskett
Gene,
it might be due to the fact that I'm no native speaker but - I have no clue what you are trying to do. Can you elaborate a bit more staight forward? Where does your workflow stop during the process? What are the command lines you are using? Up to what point it works and where does it stop? And what has gimp to do with that all?
Maybe others have more intuition with your description Gerhard
BTW: You are the Gene from LAU mailing list?
On Friday 11 September 2015 11:46:43 Lisi Reisz wrote:
On Friday 11 September 2015 16:42:01 Gerhard Zintel wrote:
Gene,
it might be due to the fact that I'm no native speaker
I thought that I was a native speaker, but I didn't understand either.
Lisi
CNC machinery my dear. LinuxCNC is the machine/human interface, and it has a gui to help visualize what its doing.
Yeah, I am a JOAT too.
Cheers, Gene Heskett
Am Freitag, 11. September 2015 schrieb Gerhard Zintel:
On Friday 11 September 2015, Gene Heskett wrote:
Greetings;
On wheezy, running the newest r14.0.2 TDE I think, from the looks of the update done recently.
I have several other machines, all running a wheezy sourced release, customized with a special pinned rtai patched kernel because the main application they run is linuxcnc.
But they are running, generally, a simple XFCE interface. And that program runs as well as its configured to do, something I am in the middle of re-writing in an effort to fine tune the machines performance.
One of the things I like to do is configure check from this nice comfy office chair is by running it over an ssh -Y login from here.
But that has always been a problem child, a puzzling one because neither machine has in its environment, a setting for colors called FORGROUND or BACKGROUND.
But its a showstopper, and only for linuxcnc, which contains tcl scripting that bails out of the program before the gui can be drawn on this screen. Other programs which use x run just fine, at least the ones I have tried. That includes gimp, but that machine has no gimp loadable files on it.
pasted from the login screen:
_tkinter.TclError: unknown color name "BACKGROUND" Shutting down and cleaning up LinuxCNC...
If it ever gets past that, it will do the same for the FOREGROUND color. BTDT but this machine was running an older ubuntu at the time. And its been long enough since I hacked around it that today I haven't a clue what I did then.
Does anybody have any suggestions on how to deal with this?
FWIW, the "simulated machine" version of that software runs just fine on this machine.
Cheers, Gene Heskett
Gene,
it might be due to the fact that I'm no native speaker but - I have no clue what you are trying to do. Can you elaborate a bit more staight forward? Where does your workflow stop during the process? What are the command lines you are using? Up to what point it works and where does it stop? And what has gimp to do with that all?
Maybe others have more intuition with your description Gerhard
BTW: You are the Gene from LAU mailing list?
I'm no native speaker, but I know what Gene is talking about :-)
Hi Gene!
you may want to add this line on your remote machines .bashrc:
xrdb -all -query|sed -e '''s#[A-Z_]*BACKGROUND# gray90#''' -e '''s#[A-Z_]*FOREGROUND# Black#''' -e '''s#[A-Z_]*HIGHLIGHT#White#''' -e '''s#[A-Z_]*LOWLIGHT# Black#'''|xrdb -merge;
This has to go in one line. It's just the part of the "alias"-line I sent you ages ago to make linuxcnc work on TDE :-) This is the line as an alias:
alias linuxcnc='xrdb -all -query|sed -e '''s#[A-Z_]*BACKGROUND# gray90#''' -e '''s#[A-Z_]*FOREGROUND# Black#''' -e '''s#[A-Z_]*HIGHLIGHT# White#''' -e '''s#[A-Z_]*LOWLIGHT# Black#'''|xrdb -merge; linuxcnc'
Again, just one line :-)
Nik
On Friday 11 September 2015 17:06:23 Dr. Nikolaus Klepp wrote:
Am Freitag, 11. September 2015 schrieb Gerhard Zintel:
On Friday 11 September 2015, Gene Heskett wrote:
Greetings;
On wheezy, running the newest r14.0.2 TDE I think, from the looks of the update done recently.
I have several other machines, all running a wheezy sourced release, customized with a special pinned rtai patched kernel because the main application they run is linuxcnc.
But they are running, generally, a simple XFCE interface. And that program runs as well as its configured to do, something I am in the middle of re-writing in an effort to fine tune the machines performance.
One of the things I like to do is configure check from this nice comfy office chair is by running it over an ssh -Y login from here.
But that has always been a problem child, a puzzling one because neither machine has in its environment, a setting for colors called FORGROUND or BACKGROUND.
But its a showstopper, and only for linuxcnc, which contains tcl scripting that bails out of the program before the gui can be drawn on this screen. Other programs which use x run just fine, at least the ones I have tried. That includes gimp, but that machine has no gimp loadable files on it.
pasted from the login screen:
_tkinter.TclError: unknown color name "BACKGROUND" Shutting down and cleaning up LinuxCNC...
If it ever gets past that, it will do the same for the FOREGROUND color. BTDT but this machine was running an older ubuntu at the time. And its been long enough since I hacked around it that today I haven't a clue what I did then.
Does anybody have any suggestions on how to deal with this?
FWIW, the "simulated machine" version of that software runs just fine on this machine.
Cheers, Gene Heskett
Gene,
it might be due to the fact that I'm no native speaker but - I have no clue what you are trying to do. Can you elaborate a bit more staight forward? Where does your workflow stop during the process? What are the command lines you are using? Up to what point it works and where does it stop? And what has gimp to do with that all?
Maybe others have more intuition with your description Gerhard
BTW: You are the Gene from LAU mailing list?
I'm no native speaker, but I know what Gene is talking about :-)
Yes - it was technical knowledge that was required, not linguisitic knowledge. You have that in spades, Nik. :-)
Hi Gene!
you may want to add this line on your remote machines .bashrc:
xrdb -all -query|sed -e '''s#[A-Z_]*BACKGROUND# gray90#''' -e '''s#[A-Z_]*FOREGROUND# Black#''' -e '''s#[A-Z_]*HIGHLIGHT#White#''' -e '''s#[A-Z_]*LOWLIGHT# Black#'''|xrdb -merge;
This has to go in one line. It's just the part of the "alias"-line I sent you ages ago to make linuxcnc work on TDE :-) This is the line as an alias:
alias linuxcnc='xrdb -all -query|sed -e '''s#[A-Z_]*BACKGROUND# gray90#''' -e '''s#[A-Z_]*FOREGROUND# Black#''' -e '''s#[A-Z_]*HIGHLIGHT# White#''' -e '''s#[A-Z_]*LOWLIGHT# Black#'''|xrdb -merge; linuxcnc'
Again, just one line :-)
Nik
On Friday 11 September 2015 12:06:23 Dr. Nikolaus Klepp wrote:
Am Freitag, 11. September 2015 schrieb Gerhard Zintel:
On Friday 11 September 2015, Gene Heskett wrote:
Greetings;
On wheezy, running the newest r14.0.2 TDE I think, from the looks of the update done recently.
I have several other machines, all running a wheezy sourced release, customized with a special pinned rtai patched kernel because the main application they run is linuxcnc.
But they are running, generally, a simple XFCE interface. And that program runs as well as its configured to do, something I am in the middle of re-writing in an effort to fine tune the machines performance.
One of the things I like to do is configure check from this nice comfy office chair is by running it over an ssh -Y login from here.
But that has always been a problem child, a puzzling one because neither machine has in its environment, a setting for colors called FORGROUND or BACKGROUND.
But its a showstopper, and only for linuxcnc, which contains tcl scripting that bails out of the program before the gui can be drawn on this screen. Other programs which use x run just fine, at least the ones I have tried. That includes gimp, but that machine has no gimp loadable files on it.
pasted from the login screen:
_tkinter.TclError: unknown color name "BACKGROUND" Shutting down and cleaning up LinuxCNC...
If it ever gets past that, it will do the same for the FOREGROUND color. BTDT but this machine was running an older ubuntu at the time. And its been long enough since I hacked around it that today I haven't a clue what I did then.
Does anybody have any suggestions on how to deal with this?
FWIW, the "simulated machine" version of that software runs just fine on this machine.
Cheers, Gene Heskett
Gene,
it might be due to the fact that I'm no native speaker but - I have no clue what you are trying to do. Can you elaborate a bit more staight forward? Where does your workflow stop during the process? What are the command lines you are using? Up to what point it works and where does it stop? And what has gimp to do with that all?
Maybe others have more intuition with your description Gerhard
BTW: You are the Gene from LAU mailing list?
I'm no native speaker, but I know what Gene is talking about :-)
Hi Gene!
you may want to add this line on your remote machines .bashrc:
xrdb -all -query|sed -e '''s#[A-Z_]*BACKGROUND# gray90#''' -e '''s#[A-Z_]*FOREGROUND# Black#''' -e '''s#[A-Z_]*HIGHLIGHT#White#''' -e '''s#[A-Z_]*LOWLIGHT# Black#'''|xrdb -merge;
This has to go in one line. It's just the part of the "alias"-line I sent you ages ago to make linuxcnc work on TDE :-) This is the line as an alias:
alias linuxcnc='xrdb -all -query|sed -e '''s#[A-Z_]*BACKGROUND# gray90#''' -e '''s#[A-Z_]*FOREGROUND# Black#''' -e '''s#[A-Z_]*HIGHLIGHT# White#''' -e '''s#[A-Z_]*LOWLIGHT# Black#'''|xrdb -merge; linuxcnc'
Again, just one line :-)
Nik
Thanks Nik, the whole alias has been added, after any previous ones it may have found.
But I won't test it instantly as I left it sitting there running with all machine power turned off so it remembers where it is in the middle of a job, when my diabetic feet said it was quitting time.
Cheers, Gene Heskett
Am Samstag, 12. September 2015 schrieb Gene Heskett:
Thanks Nik, the whole alias has been added, after any previous ones it may have found.
But I won't test it instantly as I left it sitting there running with all machine power turned off so it remembers where it is in the middle of a job, when my diabetic feet said it was quitting time.
Cheers, Gene Heskett
Hi Gene!
Just a question: You run XFCE ot TDE on LinuxCNC?
Nik
On Saturday 12 September 2015 03:01:20 Dr. Nikolaus Klepp wrote:
Am Samstag, 12. September 2015 schrieb Gene Heskett:
Thanks Nik, the whole alias has been added, after any previous ones it may have found.
But I won't test it instantly as I left it sitting there running with all machine power turned off so it remembers where it is in the middle of a job, when my diabetic feet said it was quitting time.
Cheers, Gene Heskett
Hi Gene!
Just a question: You run XFCE ot TDE on LinuxCNC?
Nik
XFCE I believe as I am looking at the mouse while its initializing after my login on a reboot.
None of those machines have more than 2Gb of ram in them, so the X used is usually "lightweight". 2 of them are D-525MW Atom powered intel boards, which we found to have the lowest IRQ latency of the lot. Unfortunately its discontinued but if you can find one on ebay, the asking is about 4x what Intel sold it for 4 years back. The "bell" curve on that board peaks at around 3 microseconds. Some highly rated, and high priced boards are so poor in that regard that extra hardware help has to be installed. The problem when running stepper motors via cpu, aka with software stepping is that at say a 10 kilohertz step rate, a 10% variation in the timing of the next pulse issued costs you 50% of the motors power as it will fall behind, then be incapable of catching up so it stalls. That usually equals a wrecked part, and/or broken tooling.
So for the bigger, faster stuff, that usually is offloaded to a programmable FPGA card which does the high speed stuff, leaving the main thread to run at 1000 times a second, doing all the floating point stuff. Those accessory cards can usually move the machine 3 to 5x faster than the cpu itself can, depending on the available voltage for the motor power. At the higher speeds, motor winding inductance limits the current, and available torque. Below those speeds, the driver regulates the current so you get full torque. So voltages north of 24, on up to the 160 volt range in the bring money in little red wagons category. Those are fast, meters a minute motions, accurate to .005mm in the line they traverse while moving half a ton of machinery that fast. If cutting metal at those speeds is wanted, 25 hp water cooled 30K rpm spindles are needed.
Thanks Nik.
Cheers, Gene Heskett
On Friday 11 September 2015 11:42:01 Gerhard Zintel wrote:
On Friday 11 September 2015, Gene Heskett wrote:
Greetings;
On wheezy, running the newest r14.0.2 TDE I think, from the looks of the update done recently.
I have several other machines, all running a wheezy sourced release, customized with a special pinned rtai patched kernel because the main application they run is linuxcnc.
But they are running, generally, a simple XFCE interface. And that program runs as well as its configured to do, something I am in the middle of re-writing in an effort to fine tune the machines performance.
One of the things I like to do is configure check from this nice comfy office chair is by running it over an ssh -Y login from here.
But that has always been a problem child, a puzzling one because neither machine has in its environment, a setting for colors called FORGROUND or BACKGROUND.
But its a showstopper, and only for linuxcnc, which contains tcl scripting that bails out of the program before the gui can be drawn on this screen. Other programs which use x run just fine, at least the ones I have tried. That includes gimp, but that machine has no gimp loadable files on it.
pasted from the login screen:
_tkinter.TclError: unknown color name "BACKGROUND" Shutting down and cleaning up LinuxCNC...
If it ever gets past that, it will do the same for the FOREGROUND color. BTDT but this machine was running an older ubuntu at the time. And its been long enough since I hacked around it that today I haven't a clue what I did then.
Does anybody have any suggestions on how to deal with this?
FWIW, the "simulated machine" version of that software runs just fine on this machine.
Cheers, Gene Heskett
Gene,
it might be due to the fact that I'm no native speaker but - I have no clue what you are trying to do. Can you elaborate a bit more staight forward?
Basically, trying to run a program that uses x graphics, with the x being exported to this machine. Any other graphical output program runs fine, but not Linuxcnc.
Where does your workflow stop during the process?
I am dead in the water because I'd have to dress and walk across the back yard & up the hill to get to the building where the machine is just to test my code. At 2AM, doable without dressing, but the noise of the doors will wake my lady. So I just say to heck with it and go find my bed, not knowing if what I just wrote works or not. Being an 81 yop diabetic, I am up at 2 or 3 hour intervals in the night anyway.
What are the command lines you are using? Up to what point it works and where does it stop? And what has gimp to do with that all?
Other than to prove the x remoting works, nothing.
Maybe others have more intuition with your description Gerhard
BTW: You are the Gene from LAU mailing list?
A chance, I occasionally expound on something there. Not recently though.
Cheers, Gene Heskett