Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - airnocker

Pages: [1] 2 3 ... 31
1
Members Projects / Re: Spark plug story
« on: October 24, 2020, 02:10:46 am »
Wow! Congrats!

2
I uninstalled, removed all artifacts of Camotics and re-installed.  It still runs full screen, no menu items work, no way to exit, sometime Alt-Tab lets me change window apps but it is unpredictable.  Using the menu key commands also do not work.

I loaded my .nc file, set workview's z to .01", ran the simulation and this fixed the view problem I first mentioned.  The 3D view window works as expected, I just have no application Menu, when I click on a menu item it highlights but does nothing.

I'll try F11 next time I feel like messing with this.

Thanks Bubba.

So, F11 did work to exit Full Screen mode, the Menu bar then worked properly.

I found that F11 worked to return Camotics from Full Screen to run in a smaller window AND the Menu bar functionality returned along with the "Minimize, Maximize, Close" windows buttons in the upper right-hand corner of the Camotics window.  These were missing when clicking "View > Full Screen".

I'm running version 1.2.0, downloaded today and installed.  I've confirmed that of the two ways to enter Full Screen mode, one works properly, the other has a bug.  Clicking the usual window control buttons in the upper right to Maximize, Minimize and Close the Camotics window work properly and when clicking the Maximize button the maximized Camotics window retains these three window buttons and the Menu bar works properly.  However, when clicking View > Full Screen things go bad as I've described earlier, but F11 does return to a functional medium size Camotics app window.


3
I uninstalled, removed all artifacts of Camotics and re-installed.  It still runs full screen, no menu items work, no way to exit, sometime Alt-Tab lets me change window apps but it is unpredictable.  Using the menu key commands also do not work.

I loaded my .nc file, set workview's z to .01", ran the simulation and this fixed the view problem I first mentioned.  The 3D view window works as expected, I just have no application Menu, when I click on a menu item it highlights but does nothing.

I'll try F11 next time I feel like messing with this.

Thanks Bubba.

4
I tried that, but I cannot remember if I re-ran the simulation, I believe I did.

The bigger problem now is that once I selected "View > Full Screen" the program always opens full screen and nothing works, period.  This isn't ready for prime time on a Win10 Pro 64-bit system.

5
I installed the Camotics dll in CB1.0 and it seems to work fine when opening an existing .072" aluminum control panel I did recently.

I do not understand why most of the profile cuts of slots and circles do not appear to go all the way through the workpiece while only three do (to some extent), or is that the expected behavior?  Playing with the "Manual" Workpiece XYZ settings do not seem to cause greater milling depth.

My .nc files Camotics based this view on clearly have milling depths that exceed the workpiece thickness.

I need some "learnin'" here.

Thanks,

PS, ran into a possible Camotics bug.  I've posted this on the Camotics group forum but so far no responses.
I had open and closed Camotics 3 or 4 times looking at my .nc file "view" before odd behavior began after I chose to show Camotics full screen.  The app displayed full screen but then none of the menus worked properly or in some cases at all.  I could still change the "eye view" of my board though.  I had to close Camotics with Windows Task Manager.  There was no other way.  Re-opening Camotics again resulted in it dutifully displaying in full screen mode and again, the Menu bar was disfunctional and I had to close again with Task Manager.

Any ideas what might be causing this?
 

6
CamBam help (General usage) / Re: Using Cutviewer Mill with CB v1.0
« on: October 11, 2020, 17:51:56 pm »
You might want to consider reloading 0.9.8P instead of N.

7
CamBam help (General usage) / Re: Unclosed shapes in pocket ignored
« on: October 08, 2020, 17:35:46 pm »
Lines and arcs that don't actually share the same end points has been a huge problem in Cad programs forever.  I use Fillet with a radius of zero a lot to keep that from happening. It trims or extends both lines if needed and no need to zoom way in to see if they are connected.

Gary, could you give a .cb example to show what you mean?

Not in CB, but in every other software I have used.  CBs version of the fillet command only works to fillet polylines and is a bit crude. A regular fillet command that trims or extends line or polylines using a radius or just end points would be nice.

Thanks for your clarification.

8
CamBam help (General usage) / Re: Unclosed shapes in pocket ignored
« on: October 07, 2020, 18:08:03 pm »
Lines and arcs that don't actually share the same end points has been a huge problem in Cad programs forever.  I use Fillet with a radius of zero a lot to keep that from happening. It trims or extends both lines if needed and no need to zoom way in to see if they are connected.

Gary, could you give a .cb example to show what you mean?

9
CamBam help (General usage) / Re: Spot Drilling
« on: October 03, 2020, 22:06:18 pm »

10
CamBam help (General usage) / Re: Spot Drilling
« on: October 02, 2020, 03:13:39 am »
I too, use a router on my DIY CNC.  Its a Porter Cable 890 router.  I use Think & Tinker's Precise Spring Collets that provide a variety of collet sizes from .125" to .5".  In addition they have a tremendous variety of Precise Bits including micro-bits with .125" shanks.

I was able to turn my router into a speed-controlled router with the product "Super-PID" which works with Mach3's machine control software.  This gives me router spindle speed choices from a few thousand RPM up to 23,000.

11
CamBam help (General usage) / Re: Re-size moves the polyline??
« on: September 15, 2020, 18:58:59 pm »
My initial guess is that the imported primitive object (your circules) imported as "polylines" and not as "circles".  The CamBam "circle" primitive has center coordinates that remain unchanged when scaling the object, whereas "polyline" primitive objects do not.  I know in CB you can convert a "circle" to a "polyline" or "Region" but I don't see that a circular "Polyline" can be converted to a "circle".

I'm sure our experts may know a cure for your problem.

12
CamBam help (General usage) / Re: text problems
« on: September 05, 2020, 20:53:53 pm »

The Engraving MOP is maybe more popular when machining fonts because it always follows the "line stroke or outline stroke center line" of the font.

I prefer the Engraving MOP and always choose a bit diameter the font stroke width desired.




13
I started over from scratch, creating a new Win7 VM, installing dotNet 4 and CamBam. Once again the grid didn't appear with major, minor lines. But when I opened an design from 0.98, the file opened and the grid displayed correctly. Go figure.

Well sir, the don't call it "virtual" for nothin' - almost or nearly as described, but not completely or according to strict definition.


14
Thanks for the screenshot.

What is your Win10 display resolution setting?  It should be at least 1920 x 1080.

I'm running on a 4K resolution Win 10 laptop with display set to 200% so that I can actually read the screen :-)
The VM with CamBam 1.0 is a Win7 guest and is running in full screen mode at 1920x1080.

The 0.98 installation is running on an XP guest OS, also in 1920x1080 and the grid displays properly. I suppose I could install 1.0 on the same XP VM and see if the grid displays correctly.

If I understand correctly, 1.0 and .98 can coexist on the same machine.

Yes, both versions can co-exist on the same machine.  I have both on my Win10Pro.  You should try running CB 1.0 on your Win10 directly, you do not need Win7 in a VM.



15
Thanks for the screenshot.

What is your Win10 display resolution setting?  It should be at least 1920 x 1080.

Pages: [1] 2 3 ... 31