Hello Guest it is March 28, 2024, 04:04:27 PM

Author Topic: Newbie - LPT/Setup Question - MDFly CV2501 CNC Breakout JCut-1325B-2 table  (Read 2572 times)

0 Members and 1 Guest are viewing this topic.

Hi all!

I'm a newbie at the CNC world but a tenured IT professional. I'm trying to help a bud with his CNC/Computer problem.

He is using Mach3 on a Dell PC, XP, MDFly CV2501 CNC breakout board and a JCUT-1325B-2 CNC Table.

At one point the table did work (estimated 1 hr?). However since then the PC has been turned off for a few months, process has been forgotten and here is where I walk in.

So now I'm trying to troubleshoot the thing and it seems to have connectivity issues between the App and the table. The LPT Port is plugged up. If you adjust settings in the LPT Device Properties the table will make a grunt sound. From what I am reading, the I/O Range number needs to be in Port 1 (0x378) which I have done (and I have played with the 0x778) and I have played with the "kernel speeds" and we just can't seem to make it 'Jog' (with the Tab Button)

I have what seems to be the standard configuration options enabled.

Thoughts on what I'm not doing correct or should try next??

Thanks for your time,

Jess
« Last Edit: June 13, 2016, 04:05:50 PM by dizydiz »
More Pics!
Hi,
don't know if any of this will help but then again it may...

I note that you have set the pulse rate to 75khz. You need a REALLY CLEAN LEAN PC to achieve that sort
of speed and unless there is a good reason to have such a high rate it won't make Mach run better but
worse. Another tip is that Mach resets its kernel speed at start up, ie change the speed, shut down Mach
and restart to see the change.

Have you run the Driver test. It is not an absolute test that the PP is producing pulses but is better than naught.
What sort of report does it give?.

Another issue which has caught a few over the years (no, not me I bloody swear!!!) is the charge pump. The charge
pump is on the BOB and it monitors the PP. If the PP stops producing pulses for any length of time it shuts itself
down. A sort of failsafe,'if no one is driving this bus then I'm going to stop'. I don't know whether your BOB has a
charge pump and whether it can be disabled, I don't bother with one but others do. The output from the PP
can be assigned (port and pin) on the outputs page of the port and pins page under config tab.

I don't see on the pic of the BOB whether it has LED's on the outputs. They are invaluable for diagnosing setup
problems. In absence of an LED you will have to use a multimeter to test each motor output. Go to the direction
output of an axis, x say. On the manual input screen of Mach issue a G1 x1 command. The direction output
will read high or low depending on your set up. Then issue a G1 x-1 command. The output should change state.
You can and probably will have to repeat this for for all direction outputs. Temporarily you can reassign step output
as a direction and use the same method to check the functionality of each of your motor outputs.

On the Mach diagnostics page you should be able to 'see' the operation of each of your limit switches. With the switch
closed the diagnostic LED might be lit (depending on assignment) and not lit when open.

These steps will allow you to establish whether Mach has control of the PP and that the BOB is capable of transmitting
the pulses. If all is well you are a lot closer to running motors.

Let us know how you make out.

Craig
'I enjoy sex at 73.....I live at 71 so its not too far to walk.'
Hi,
don't know if any of this will help but then again it may...

I appreciate the post!!

I note that you have set the pulse rate to 75khz. You need a REALLY CLEAN LEAN PC to achieve that sort
of speed and unless there is a good reason to have such a high rate it won't make Mach run better but
worse. Another tip is that Mach resets its kernel speed at start up, ie change the speed, shut down Mach
and restart to see the change.

That was just me trying "all the options". I did get the "restart app to take effect" messge, so I did try restarting the app a few times. I'll try to keep it at the low Mhz setting for now. I dont think we have a "need" to make the kernel speed high.

Have you run the Driver test. It is not an absolute test that the PP is producing pulses but is better than naught.
What sort of report does it give?.

I did not try the Driver Test. Not sure how to do that. I can try to google it if you dont have a link...

Another issue which has caught a few over the years (no, not me I bloody swear!!!) is the charge pump. The charge
pump is on the BOB and it monitors the PP. If the PP stops producing pulses for any length of time it shuts itself
down. A sort of failsafe,'if no one is driving this bus then I'm going to stop'. I don't know whether your BOB has a
charge pump and whether it can be disabled, I don't bother with one but others do. The output from the PP
can be assigned (port and pin) on the outputs page of the port and pins page under config tab.

Really am new to this part of the project as well. I can check the config tab, if I can find it.

I don't see on the pic of the BOB whether it has LED's on the outputs. They are invaluable for diagnosing setup
problems. In absence of an LED you will have to use a multimeter to test each motor output. Go to the direction
output of an axis, x say. On the manual input screen of Mach issue a G1 x1 command. The direction output
will read high or low depending on your set up. Then issue a G1 x-1 command. The output should change state.
You can and probably will have to repeat this for for all direction outputs. Temporarily you can reassign step output
as a direction and use the same method to check the functionality of each of your motor outputs.

I was able to see one lil blue light but never did try to watch the lights as a "print" was happening. Good thought!


On the Mach diagnostics page you should be able to 'see' the operation of each of your limit switches. With the switch
closed the diagnostic LED might be lit (depending on assignment) and not lit when open.

These steps will allow you to establish whether Mach has control of the PP and that the BOB is capable of transmitting
the pulses. If all is well you are a lot closer to running motors.

Let us know how you make out.

Craig

I wasn't aware of the Diag page. I guess I need to study up on that too.

The whole setup is in a unique setup. No internet. I'm hoping to fix the no internet issue this weekend.

I'll post an update when I take a look at these couple things. Thanks Craig!
Hi,
we all have to start somewhere...
The config menu is next to file menu top left hand corner.
The different screens are in a row just underneath. The most often used ones when setting up as you are
MDI, that's manual data input, allows you to issue gcode commands and the diagnostics screen.
The driver test is found in the Mach3 folder on your HD. I have a shortcut on the desktop for it.
I rather doubt you want the internet on the PC running Mach3. In fact you don't really want ANYTHING
on the PC running Mach3. I don't have anything, that includes sound/video/internet/antivirus/firewall/network
I mean anything. The only other program that runs and not concurrently is notepad text editor. I have turned
off screen savers/watchdogs/powersavers and any other feature I don't use. The PC controlling my machine
is for controlling my machine and NOTHING else.
I have a second copy on my laptop for experimentation and all the CAD/CAM/viewers and all the usual apps
you find on a PC but it never goes near my controller PC, I transfer Gcode on a memory stick.
My machine despite being small is powerful as I have planetary gear reducers on the axes they produce
1500 lbf at/near to stall, easily enuf to injure. A crash can be VERY expensive, I've had a few...without injury
so far. I don't take any chances with my controller PC. I'm perhaps a little unusal in this regard but know
also that quite a few experienced Mach3 machinists are likewise.

Craig
'I enjoy sex at 73.....I live at 71 so its not too far to walk.'