Advanced Search

en.bergerda.com/filedown.php?id=49. i do have a manual for this drive. the output #5 light does NOT come on when i turn on the spindle. the spindle output on tb2 comes on when i turn on the spindle and there is nothing connected to that pin. i guess my next step is to verify that i have the wiring correct but that doesn't explain why the spindle led on tb2 comes on when i turn on the spindle. what do i look for in hal show for the encoder for that drive? i have been reading through some of the linuxcnc documentation and one of the pages i read recommended rotating the motor with the power off and look in halshow to see if the encoder is connected to one of those pins. i am just wondering what i would look for in halshow or hal meter to see that signal? would it be a signal or a pin? or would it be something else? i have noticed looking at other hal files that their output spindle enabel has a true after is. should mine have a true after it? here is what mine says
# --- SPINDLE-ENABLE ---
net spindle-enable => [HMOT](CARD0).outm.00.out-05

tommylight wrote:

Yup, but behind a paywall.

 
It is not a paywall for personal or small business use.

Edit: "small business" should read "small scale commercial use in up to 5 machines"

Yup, but behind a paywall.

ubuntu.com/real-time
 

moretoyswins wrote:

S
Next,  I need to gut my control box to swap the DM556Ts in for the G250Xs!

I would rather get a new box, less work and leave the existing one as is since it works with GRBL, or rewire for parallel port maybe? I know i would!

Moved to "QtPyVCP" section.

Let me try once more; quite new to this--This time around: I used st-link utility, from there i plugged address
 
The first time around I had the size set to something smaller as it appeared to be null data after some point? this time i changed the size to 0x07FFFF

New version shows 511KB when unzipped (had to zip to upload here)
 

cncwhacko wrote:

 

File Attachment:

File Name: nvmpg.bin.zip
File Size:22 KB

Attaching the nvmpg .bin I was able to extract from my unit. Hope this helps debug what's going on with the TFT/display oddities!

Hi, thanks but something is not right with the file. It's only 99KB where the hex file I dumped from the MPG with ST-Link Utility is 400KB. On inspection, the file does not look like a valid bin file either.

I have a working Gmoccapy config using carousel component. Is it possible to use Probe Basic with the carousel component instead of the macros?

I'm using QTDragon for tool probing. The probing works great. The issue I'm dealing with is when I specify where the sensor is located, such as x0.3493 and y0.5298 in the user interface, and select Go To Sensor, it always goes to x0.0137 and y0.0208. Regardless of where I tell it the sensor is located, it always goes to the same X & Y location. I've searched through all the files to see if I could find somewhere it would allow me to change the settings. I cannot find where it is getting the location it's going to. I can find in the qtdragon.pref where my settings x0.3493 and y0.5298 are located but changing them never results in getting to the right location when select go to sensor. Any help?

So, as I mentioned previously:

I have not given up on the Gecko G250X, but I must get this controller working ASAP.  As such, I have ordered DM556T stepper drives, which others seem to have working with LinuxCNC and Mesa boards.  Unfortunately, it will take a few days to get them.

I ordered the DM556T last week and they got here late today.  Doing a quick test without changing any of the existing wiring other than to disconnect one G250X.  Because the G250X uses 4 leads for power and motor phase connections, I just wire nutted three of the leads on each of the split cables and nutted the signal GND, since the DM556T seems to only uses the motor power GND. I wired up one DM556T using the single lead of each of the slit cables and I added the Step - and DIR - connection.  Ran pncconf wizard, using most of the values I did for the G250X, other than not selecting the G540p as the driver.  And ...

Test motor turned both directions without issue.  It is difficult to tell if my setting are correct, but I can work on that when I have everything wired.

Next,  I need to gut my control box to swap the DM556Ts in for the G250Xs!

Again, I wish to express my appreciation to TommyLight  and PCW  for their help.  I know I still have a long way to go, but at least I feel I have moved forward.

Thanks

Well hey thanks for your helping us noobies out. I did an experiment where rather than having Spindle-CW going to pin 2 i changed it to Spindle-PWM and left Spindle-CCW on pin 3. Now the spindle starts up when running M3 S1000 only its spinning way faster than 1000 RPM. It also actuates +- about 400RPM and doesn’t sound very good either. I believe the PWM frequency is out of tune. How do I figure out the frequency settings to match for the motor so it spins at the correct speed and doesn’t fluctuate? Again thanks for your help

1. the above will not work, there can not be same lines inside a hal file
2. what drive?
We can not help without more info, and please do not make us chase info on the internet, we all volunteer out time here to help.
-
In case it ends up as you mention above in needing a PWM signal in one or the other pin, that would need a bit of hal wizardry to change from one pin to the other when changing direction, i would guess doable.
First, we have to be sure that is the case, then we can venture into hal and come up with something that works for you.
Edit:
Pictures always help.

No idea...well i have ideas from experience with serial ports, so first thing i would check is the serial comm parameters, speed, parity and stop bit.
You have to check those on the new VFD, make a note on what they are set to, and change the loadusr line accordingly.
In case you can not get those numbers, i would try
loadusr -W hy_gt_vfd -t 1 -d /dev/ttyUSB0 -p none -r 9600
then increase the speed gradually (see google for standard serial port rates)

That looks cool!  I have not seen anything like that before.  
If the hy_vfd component works on with my old YH vfd,  why would the hy_gt_vfd fail with this error, "waitpid failed hy_gt_vfd hy_gt_vfd" 
call is "loadusr -W hy_gt_vfd -t 1 -d /dev/ttyUSB0 -p none -r 38400" does that at least look correct?