Messages

11

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: January 15, 2021, 11:05:13 AM »

MF2D
You asked: "does this board support threading (does the index support signal)?"

I'm not quite sure what you mean. by threading or signal. Please expand on your thought.
One thing, I wish I had the source code of the processor and the RNR driver.
Bill

12

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: January 13, 2021, 12:59:07 PM »

Hi two things,
As far as I know, the Bitsensor board is compatible with Mach4. It just doesn't have a manual for saying how.
Second:
I just updated my user guide for the BSMCEO4U. New name and new link. I have identical web pages on two different home servers in attempt for 100% up time. One in Chicago and the other in Rock Island, IL  (see cnc.vancura.biz and cnc.vancura-innovations.com)

http://shoelessdave.com/Vancura.Innovations/files/BSMCEO4U%20Install%20Manual-converted%20wjv%202.2.pdf

http://vancura.biz/files/BSMCEO4U%20Install%20Manual-converted%20wjv%202.2.pdf

It is in effect a full translation from the Chinese version of the manual. I put some serious time into it trying to make American English out of it. I added a few more installation diagrams and some more documentation on the ports.

What it needs now is a Mach4 addendum.  I personally don't plan to go to Mach4, but anyone willing to document their frustrations in setting it up, will be welcome to send me the procedure for publishing.
Bill

13

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: November 07, 2019, 02:27:47 PM »

To add a little more to the BSMCEO4U-PP definitions.
1) 24V: Input can be anywhere from 12V to 36V to power the digital input and outputs only. It is usually the same voltage that supplies the motor drivers, but it can be a separate supply (200ma minimum). 
2) DCM: connection is digital ground for both input switches (Limits, E-Stop, & Probe) and output loads (VFD Start, Flood, & Mist).
3) ACM is the analog ground specifically for the spindle speed control. It goes to the ACM pin on the VFD.
4) AVI: is the analog output to the spindle speed control. (not very linear). It goes to the AVI pin on the VFD.
5) 10V: is the input analog reference voltage for the spindle speed control. This should come from the VFD low voltage supply (10V to 13V) output.
6) 5V: is a low power output to supply the motor driver opto-isolators providing you use "Low-True" logic (pull to ground for ON)
7) GND: output is the ground to the motor drivers used when driving "High-True" logic (Pull to 3,3V to 5V for ON).
Note:  For the motor drivers, you will use either the 5V or the GND connection, not both. Choosing the right method may require some experimentation.

Note: DCM, ACM, and GND (all grounds) are not connected together. Each serves an isolated purpose, and their isolation is an attempt to protect your equipment. If you want everything grounded together (and you should), run a separate ground wire from each piece of equipment to a common grounding point near your master power input. This method should prevent a single failure from destroying everything. 
Thanks.
Bill

14

Mach3 under Vista / Re: New setup for USB board by BSMCEO4U-PP Bitsensor

« on: October 16, 2019, 05:39:36 PM »

Just to clear up some settings for the outputs and  inputs for the BSMCEO4U board to work.
The Mach 3 setup for ports and pins need to be set up correctly.
Outputs for the motors are simply port 0 pin 0 for X, Y, Z, and A. The drive outputs are hard coded.
Output for spindle control is Port 0-pin1 for both pulse and direction
Spindle control is set to 1000 Hz, check Use Spindle output and PWM.   
Input signals are on PORT 3; where  In1 = P3-Pin1, In2 = P3-Pin2, In3 = P3-Pin3, In4 = P3-Pin4
Output signals are also on PORT 3; where  Out1 = P3-Pin1, Out2 = P3-Pin2, Out3 = P3-Pin3, Out4 = P3-Pin4
The schematic of a typical setup has
E-STOP on Port 3, Pin 1,
Limit switches on Port 3 Pin2
Touch Plate on Port 3 Pin 4

15

Mach4 Toolbox / Re: Touch Plate Corner Finder

« on: January 02, 2019, 03:31:34 PM »

This is a valuable fix-up to Mach 4. I will definitely use it.
As far as I can tell, this code requires offsets for X and Y to be identical to work on all four corners.
The typical edge finder can be used to work on all four corners.
Here's the problem:
If an edge finder uses three different surface offsets, for example, A, B, & Z  Interestingly enough, the top left corner and the bottom right corners use the same surfaces for X and Y, which is A and B respectively. However, the top right corner and the bottom left corner use surfaces X & Y as B and A respectively. 
Should the edge finder have three different offsets for X, Y, & Z , then the code needs to compensated for differences depending on the corner being probed.
Note Z doesn't change for any corner.

Does this code take in account for using all four corners of the work piece?
Thanks,
Bill

16

General Mach Discussion / what are rules for M89 variable & subroutine numbering in external subroutines

« on: March 16, 2018, 04:21:08 PM »

Do the variables that are used in an external subroutine (like #12 = 42) affect the variables that are used in the main program with the same name (like #12 = 37.5)?
I am aware that variables in the main program are public to the entire main/local module.
Will the variable #12, if used, in both the local program and the external subroutine interfere with each other? If they do, that means each subroutine must be uniquely constructed.
I am aware that things like G52 are not buffered and if incorrectly used, will return to the main program to an incorrect pointer.

Another item that I haven't completely explored yet. Will the local subroutine numbers (like O10, O11, etc) in the external program module interfere with the main program subroutine numbers of the same number? My G-Code generator reuses local subroutine numbers on each project build, and it is highly likely that creating a general purpose subroutine will have subroutine numbers that are identical to the numbers in the main program.

I could find no documentation that lays these rules out.
What are the rules here? 
Thanks,
Bill

17

Third party software and hardware support forums. / BOBCAD V23 does not run on Win 10 (Why not?)

« on: June 19, 2016, 01:38:40 PM »

Hi,
BOBCAD V23 will not run on windows 10.
Does anyone know why and what can be done to fix this problem? The problem is consistent on two win10 PCs (laptop and desktop).

The error message comes from Microsoft visual C++ Runtime library. It suggests that the program has requested the runtime to exit in an unusual way.
It also suggests that I contact BOBCad for help. As most people know, their only suggestion is to upgrade to V28.
I could use a solution that is more productive at a lower cost.
I have tried a wide variety (if not all) of the privilege and emulation modes.   I have many C++ libraries loaded (all forced in by other programs) they are C++ 2005, 2008, 2010, 2012, 2013, & 2015.
 Thanks,
Bill

18

G-Code, CAD, and CAM discussions / Re: Ghosting movements Toolpath Doesnt match the displayed part Its wrecking parts!

« on: December 25, 2012, 06:53:34 PM »

If the only difference is the torch, chances are that you still have an electronic noise problem. This is hard to understand, because this seemingly electrically harmless change can cause problems. If you have an electrically operated torch control, it may be causing interference with one of the motor drivers, and causing it to generate phantom pulses that move the torch away from the intended path. The proof of phantom pulses is that they will cause the torch X&Y position to not return to your 0,0 reference point when you do a home. I recommend that you make sure that your cables are properly shielded and grounded.

19

LazyCam (Beta) / Re: depth works when I start at zero, but not when I change the cut start

« on: April 05, 2011, 12:03:37 PM »

The cutting depth of -.15 must be made relative to the top of the work so a cut depth of -.15 is actually 1.7323 - 0.15 = 1.5823".

If I understand the problem correctly, the other program generates G-code using 1.7323" as the top of material. 

The solution for you is to create your cutting patterns using a top of material as zero (the right way to think about cutting). Then migrate your G-code into you other program's G-code using the G52 command to offset the Z axis zero to 1.7323. The Mach3 program will do the depth of cut math for you.  Don't forget to clear the G52 command after your routine is done.

Good luck,
Bill
 

20

General Mach Discussion / Re: mach3 jog not working, timer not couting...

« on: February 19, 2011, 06:37:26 PM »

You are using a laptop computer. The newer models that still have parallel ports on them are notorious for having low power drive and auto power save. This combination makes for lousy CNC operation. Your best bet is to go back to a desktop unit with a real parallel port. As far as I know, a USB to parallel printer adapter will not work either.

With this said, I have a 8 year old laptop that runs the CNC through the parallel port just fine. So you might look for an oldie good used laptop

Good luck,
Bill