Gscreen - a GTK / Glade / Python based screen
- newbynobi
- 
				  
- Offline
- Platinum Member
- 
				  
		Less
		More
		
			
	
		- Posts: 1928
- Thank you received: 393
			
	
						01 Apr 2013 04:28				#32135
		by newbynobi
	
	
		
			
				
Thanks Chris,
and gmoccapy is still under development, there are still a lot of thinks to do, like HAL Pins for hardware connections to most functions, like they are included in nearly every industrial control. And also some special settings for the GUI.
May be somebody can help about the idea "Reload Tool on start up"
How to set the tool in spindle without having the machine homed or switched on.
Norbert
					
	
			
			 		
													
	
				Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen			
			I am interested what others will build with Gscreens infrastructure. I'm very impressed with Gmoccapy.
Thanks Chris,
and gmoccapy is still under development, there are still a lot of thinks to do, like HAL Pins for hardware connections to most functions, like they are included in nearly every industrial control. And also some special settings for the GUI.
May be somebody can help about the idea "Reload Tool on start up"
How to set the tool in spindle without having the machine homed or switched on.
Norbert
Please Log in or Create an account to join the conversation.
- cmorley
- Away
- Moderator
- 
				  
		Less
		More
		
			
	
		- Posts: 7230
- Thank you received: 2106
			
	
						01 Apr 2013 13:32		 -  01 Apr 2013 13:33		#32145
		by cmorley
	
	
		
			
	
	
			 		
													
	
				Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen			
			
				tried again today to embed Onboard keyboard into Gscreen.
I have to do it by launching Onboard from within Gscreen and then reading the window id from stdin.
But when I do it blocks Gscreen permanently and never returns the id number.
I've been using variations of this:
If i comment out the id line then it launches fine and prints the id number to the screen.
I can use that number inn a socket program to embed to another window.
I just need another way to read the standard in....
post to Onboard project:
answers.launchpad.net/onboard/+question/216006
Chris M
					I have to do it by launching Onboard from within Gscreen and then reading the window id from stdin.
But when I do it blocks Gscreen permanently and never returns the id number.
I've been using variations of this:
def launch_keyboard(self,args="--xid",x="",y=""):
        print args,x,y
        try:
            self.data.ob = subprocess.Popen(["onboard",args,x,y])
            id = self.data.ob.comunicate[0]
        except:
            print _("error with 'onboard' on screen keyboard program")If i comment out the id line then it launches fine and prints the id number to the screen.
I can use that number inn a socket program to embed to another window.
I just need another way to read the standard in....
post to Onboard project:
answers.launchpad.net/onboard/+question/216006
Chris M
		Last edit: 01 Apr 2013 13:33  by cmorley.			
			Please Log in or Create an account to join the conversation.
- LAIR82
- Offline
- Elite Member
- 
				  
		Less
		More
		
			
	
		- Posts: 197
- Thank you received: 3
			
	
						01 Apr 2013 19:24				#32153
		by LAIR82
	
	
		
			
	
			
			 		
													
	
				Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen			
			
				Thanks Chris
Working on re-compiling now, as for the tool offset patch, we have our tool table set-up with tools 1-7, 11-17 and 10001-100017. The last ones, 10001-100017 are where you enter the amount of fine adjustment or "wear" to be applied to that tool. Even in Diameter mode you have to enter that value in radius though. When you call a tool say T0101 the last two numbers are what offset to call, which dosen't have to be the same as the tool number, you could theoretically use a couple different offset values, T0101, T0102, T0103, for different diameters on a single part to get every dimension dialled in exactly.
Rick
					Working on re-compiling now, as for the tool offset patch, we have our tool table set-up with tools 1-7, 11-17 and 10001-100017. The last ones, 10001-100017 are where you enter the amount of fine adjustment or "wear" to be applied to that tool. Even in Diameter mode you have to enter that value in radius though. When you call a tool say T0101 the last two numbers are what offset to call, which dosen't have to be the same as the tool number, you could theoretically use a couple different offset values, T0101, T0102, T0103, for different diameters on a single part to get every dimension dialled in exactly.
Rick
Please Log in or Create an account to join the conversation.
- cncbasher
- Offline
- Moderator
- 
				  
		Less
		More
		
			
	
		- Posts: 1021
- Thank you received: 202
			
	
						01 Apr 2013 19:58				#32154
		by cncbasher
	
	
		
			
	
			
			 		
													
	
				Replied by cncbasher on topic Gscreen - a GTK / Glade / Python based screen			
			
				Rick ,
could you kindly post a tool.tbl file , i'm trying to get head around the layout and values etc
i'm making a mistake somewhere .. haha
					could you kindly post a tool.tbl file , i'm trying to get head around the layout and values etc
i'm making a mistake somewhere .. haha
Please Log in or Create an account to join the conversation.
- LAIR82
- Offline
- Elite Member
- 
				  
		Less
		More
		
			
	
		- Posts: 197
- Thank you received: 3
			
	
						01 Apr 2013 20:12		 -  02 Apr 2013 07:28		#32155
		by LAIR82
	
	
		
			
	
	
			 		
													
	
				Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen			
			
				No Problem,
If I figured it anybody can, LOL
Rick
I don't honestly know what happened, but I swear I attached my tool file when I sent this reply. If I have a copy at home I will send it to you in a little while, if not first thing tomorrow.
Sorry about that CNCBasher
					If I figured it anybody can, LOL
Rick
I don't honestly know what happened, but I swear I attached my tool file when I sent this reply. If I have a copy at home I will send it to you in a little while, if not first thing tomorrow.
Sorry about that CNCBasher
		Last edit: 02 Apr 2013 07:28  by LAIR82.			
			Please Log in or Create an account to join the conversation.
- LAIR82
- Offline
- Elite Member
- 
				  
		Less
		More
		
			
	
		- Posts: 197
- Thank you received: 3
			
	
						01 Apr 2013 21:01				#32159
		by LAIR82
	
	
		
			
	
			
			 		
													
	
				Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen			
			
				She's up and flyin now,
Thanks for the help guys,
We will do some test trials and let you know how things go.
Thanks Again everyone,
Rick
					Thanks for the help guys,
We will do some test trials and let you know how things go.
Thanks Again everyone,
Rick
Please Log in or Create an account to join the conversation.
- LAIR82
- Offline
- Elite Member
- 
				  
		Less
		More
		
			
	
		- Posts: 197
- Thank you received: 3
			
	
						02 Apr 2013 01:39				#32162
		by LAIR82
	
	
		
			
	
			
			 		
													
	
				Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen			
			
				Hello Chris
I noticed one thing today, not a showstopper by any means, would there be a way to utilize the extra button in the debug menu to open up classicladder?
Thanks
Rick
					I noticed one thing today, not a showstopper by any means, would there be a way to utilize the extra button in the debug menu to open up classicladder?
Thanks
Rick
Please Log in or Create an account to join the conversation.
- LAIR82
- Offline
- Elite Member
- 
				  
		Less
		More
		
			
	
		- Posts: 197
- Thank you received: 3
			
	
						02 Apr 2013 07:32				#32174
		by LAIR82
	
	
		
			
	
	
			
			 		
													
	
				Replied by LAIR82 on topic Gscreen - a GTK / Glade / Python based screen			
			
				Here is my tool.tbl file in .txt format.
Thanks
Rick
					Thanks
Rick
Please Log in or Create an account to join the conversation.
- cncbasher
- Offline
- Moderator
- 
				  
		Less
		More
		
			
	
		- Posts: 1021
- Thank you received: 202
			
	
						02 Apr 2013 13:29				#32180
		by cncbasher
	
	
		
			
	
			
			 		
													
	
				Replied by cncbasher on topic Gscreen - a GTK / Glade / Python based screen			
			
				thanks Rick ,
i now know where i went wrong ! haha
					i now know where i went wrong ! haha
Please Log in or Create an account to join the conversation.
- cmorley
- Away
- Moderator
- 
				  
		Less
		More
		
			
	
		- Posts: 7230
- Thank you received: 2106
			
	
						02 Apr 2013 14:59				#32181
		by cmorley
	
	
		
			
				
Pushed this addition.
Added to debug page - let me know of any problems
Chris M
					
	
			
			 		
													
	
				Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen			
			Hello Chris
I noticed one thing today, not a showstopper by any means, would there be a way to utilize the extra button in the debug menu to open up classicladder?
Thanks
Rick
Pushed this addition.
Added to debug page - let me know of any problems
Chris M
Please Log in or Create an account to join the conversation.
		Time to create page: 0.272 seconds	
