Advanced Search

Hello, I'm building a small CNC milling machine. The iHSV57-30-18-36-EC driver caught my eye. Since I have no experience with Linux, I struggled to get the motor running. However, the motor jumps slightly and irregularly. If you happen to have a working ini, hal, and xml file for this motor, could you help me learn from it? 

Josh 

Hi, sorry for the late reply but I was travelling.
I havent run any updates since I installed PB (never change a running system). 

What exactly do you want me do double check?

This is my config..
github.com/SebastianMusser/LinuxCNC/

regards!

Looks like installing LinuxCNC isn't as easy as installing a casual linux.I remember I had to burn DVD when I first installed it and I borrower a DVD drive to install it properly.I flashed the image using Rufus 4.7 and booted from the USB flash drive - but  then the setup mentions "your installation media coultn't be mounted". Is this a known bug? What's the workaround?Also I was unable to set the BIOS to UEFI mode only. There's no option to disable the compatibility mode - so setup outputs warnings when using USB flash drive in EFI mode.

The link in the html manual does not work. Is this spreadsheet still available?

I see. So is there something like GRBL for output, but used for encoder-inputs?
Like an Arduino or Teensy based encoder-decoder?

I just started um this old computer. There's an old Grub 1.98 with Ubuntu 13 installes. Linux 2.6.32-122-rtai (I probably installed this about 10 years ago )
Also I have to change the bios battery, since it is empty.
It has an Intel D425 installed and 4GB memory.


//Edit: github.com/AlexmagToast/LinuxCNC_ArduinoConnector
That might to the trick. I'm sure there's at least one Arduino Mega2560 within the range of two meters around me. Also I can see at least 5 Arduino Uno in front of me

Thank for the help!

As to what caused the damage, disconnecting/reconnecting the DB25 cable from the
7I77 if there is an (even small) ground potential difference between the PC and the machine
can damage interface components so should only be done with all power off.

That's probably what happened, definitely my screw-up!

Tomorrow, I can look at the schematics and see what parts on the 7I77 are in the ENCMUX
signal path (I think just one Hex inverter)

Thank you!

/Peter

After not having a single bit of Linux, let alone LinuxCNC experience beyond knowing the name, I'm quite happy with what I accomplished within the space of a few weeks. Took a CNC converted lathe and turned it into a dual head urethane grinder with notching and grooving cutting. I'll take what wins I can get at the moment. I'm fairly certain as time progresses and my understanding expands, I'll look back on what I did and facepalm at my "work". For now, I have to stick with the old saying: If it's stupid and it works, it's still stupid and you're lucky.
Thanks for the resource, I will go through it as I have other homework sources I need to review to gain a better understanding of this system.

Basically as I said before, this points to an issue with ENCMUX. 

It may be a damaged 7I77 buffer chip for this signal
or in may be an on board 7I77 issue. The ENCMUX
signal is om DB25 pin 17. 

A 5i25 problem is still possible but less likely (damaged I/O pins
tend to be stuck low so can be detected with the simple mesaflash test)

I would definitely scope/trace the encmux signal.

As to what caused the damage, disconnecting/reconnecting the DB25 cable from the
7I77 if there is an (even small) ground potential difference between the PC and the machine
can damage interface components so should only be done with all power off.

Tomorrow, I can look at the schematics and see what parts on the 7I77 are in the ENCMUX
signal path (I think just one Hex inverter)
 
 

Hi,

I updated ProbyBasic to the newest dev version and I am facing two Issues. After the update, I deleted all my old folders (user tabs, subroutines, python etc...) with the new folders from the example config. I am currently trying out the ATC Rack tool Changer. 

Issue1:
For this, I am trying to modify my linuxcnc.var file, manually changing the following Parameter:

"3973    10.000000
3979    1.000000
3981    -76.000000
3982    0.000000
3983    1137.000000
3984    615.680000
3985    1137.000000
3986    565.680000
3987    1097.000000
3988    615.680000"

However, when opening Linuxcnc, all the values are still 0. When modifying some values in the GUI, for example X Position for P1 to 1337, I get the error "Error: No Conditions Met, Rack ID Not Set" BUT when hitting "update Rack ATC Parameters" the Value is saved in the linuxcnc file (but all the other values above are overwritten to 0.

So, I would be fine with including all these in the GUI but the only value I can not change is the "ATC Rack ID", which seems to be write protected and, I assume, creates the error above.

EDIT: Okay, I filled now all Parameters and it seems to have created a RACK ID -> 4. And it is working now.

Issue 2:

I set up everything and can now manually clamp and release the tools. The Tool touch off is also working (on both ATC and Tool Tab). However, when clicking "Store Tool in Rack", I get the Error "Unknown m code used: M10" but M10 is in the subroutines folder.
Similar to clicking "Ref Rack Data" (what does it actually do?) I get "Unknown m code used: M13".



 

Cysign wrote:

Would a LPT port have enough inputs and outputs to read linear encoders for 3 axis?

Yes and no:
-Yes it can read 3 axis be it A/B or A/B/Z, so 6 or 9 inputs, but only in "IN" or "X" mode that most built in parallel ports can do but not all, and you might need more than one parallel port for everything to work.
-No as parallel port is really slow for reading encoders, especially high resolution ones.
You can use a parallel port or two to do some testing and maybe very slow work, but i would not think you can use it for a production machine.
As a reference, you can do 5000-20000 encoder pulse readings per second on a parallel port with a good latency PC, might even go to 50000 with a really good latency PC, but this is to far fetched.
And for reference Mesa can do up to 10000000 pulse readings per second. Yes, that is 10 million.

Thanks for your reply!
5i25 reported as you said 0001FFFF

I also tried with another cable without any change.

Encoder 00 and 01 show the same value, although nothing is attached to 01.
02 & 03 seems to be paired as well.
I got different reading on encoder 04 & 05, but they both changing from one encoder input.

Any further troubleshooting tips are highly appreciated! I am comfortible scopeing/soldering SMT if you think this is repairable.
/Peter

Nice idea - but that won't work, since the LPT-port is connected to the motherboard

Would a LPT port have enough inputs and outputs to read linear encoders for 3 axis?

Regarding linuxcnc.org/docs/html/hal/parallel-port.html that should work. So I coult start using the Intel Atom computer and once it's broken, I'll swap over using a Mesa card.

I guess I'll try to install a new version of LinuxCNC on the computer, connect it to the Toshiba driver board and the steppers and see if I can get it rotating.

Maybe I'll order one linear scale and test if it'll work with the LPT connection.

The following hal file is based on linuxcnc wcomp component.
linuxcnc.org/docs/2.8/html/man/man9/wcomp.9.html
The file was automatically generated by the eagle2hal script. 
 
​​​​​​​
#

---

# Load realtime Components and their counts
loadrt not          count= 1
loadrt or2          count= 1
loadrt wcomp    count= 1
#

---

# Add functions to threads
addf wcomp.0              servo-thread
addf not.0                    servo-thread 
addf or2.0                    servo-thread 
#

---

# Set parameters
setp wcomp.0.max  1600.0      
setp wcomp.0.min  900.0     
#

---

# Connect Pins using signals/wires
net axis.x.pos-cmd wcomp.0.in
net cyln.pos<max&&>min wcomp.0.out  not.0.in
net cyln.pos>max&&<min not.0.out  or2.0.in0 
net cyln.extended or2.0.in1  wcomp.0.under  
net trigger or2.0.out  hm2_7i76e.0.7i76.0.0.output-05 
 

Just discovered that the .var file was created with group and other permissions set to read only. Changing these to read and write seems to have made a difference. The probe feed speeds now seem to be updating based on values entered in the ui.

The ui entry boxes for probe feed settings in the surfacemap user tab still don't work properly. 

If the input to encoder channel 0 affects the count on encoder channel 1,
that suggest a problem with the encoder multiplexing (basically that the encoder
mux-sel signal is not getting to the 7I77) 

This could be bad cable, or cables not inserted fully, bad or damaged
5I25, or bad or damaged 7I77.

You can check the 5I25 for damage by

1. Disconnecting the DB25 cable (with all power off)
2. Running: 
sudo mesaflash --device 5i25 --rp 0x1000

This should report all highs on the I/O pins = 0x001FFFF

To diagnose the 7I77 encoder issue, I would setup halshow
to watch all 6 encoders and then try each encoder input and see:

1. If it works
2. If it affects any other channel