Advanced Search

First Question.

For a 1mm jog, I originally set my MUX40.in1 to 1.0. This was resulting in an exact 4mm jog each count. To fix this I need to set the scale below to 0.25. While I can do this and get the result I want, it bothers me that I have to use a ratio instead of direct number and will be harder to decode at latter dates. It seem arbritary that each count would be 4mm exact.

setp mux4.0.in1 1 (jogs 4 mm per count)

setp mux4.0.in1 0.25 (Jogs 1 mm per count)

net encoder-counts  <= encoder.0.counts
net encoder-counts => axis.x.jog-counts

Question is, where is the actual jog value recorded in LinuxCNC.? I cold find nothing in the .ini or .hal files that seems to indicated it would jog exactly 4mm each jog count.



Second question,

Per the below, I am currently using mux4 to determine the jog scale. But my MPG switch does is not using an encoder switch but instead has 3 simple outputs of which I placed into input 26 (1x), 27(10x), 28(100x)

I got everything to work but can not find any details in .hal how to use something other than mux4 logic to place the correct scale into the axis jog. This seems like it should be simple. More or less just want if one of those pins are true, the correct scale is selected. Below is partial code referancing the scale portion. Note. Only using pins 26 and 27 at the moment due to the mux4 requirements. Other than this, everything is working fine.

# This sets the scale that will be used based on the input to the mux4
setp mux4.0.in0 0.025
setp mux4.0.in1 0.25
setp mux4.0.in2 2.5

# The inputs to the mux4 component
net scale1 mux4.0.sel0 <= hm2_7i76e.0.7i76.0.0.input-26
net scale2 mux4.0.sel1 <= hm2_7i76e.0.7i76.0.0.input-27

# The output from the mux4 is sent to each axis jog scale
net mpg-scale <= mux4.0.out
net mpg-scale => axis.x.jog-scale

---

Basically want:

if Pin 26 true then axis.x.jog-scale == 0.025
if pin 27 true then axis.x.jog-scale == 0.25
if pin 28 true then axis.x.jog-scale == 2.5

Hallo Michael,

Danke für deine Antwort.Ich habe damals(ca.8 Jahren) mit LinuxCNC schon angefangen.Da hatte ich ein TB6560 Board von Modellbau Letmathe.Ich begann mit einen (China)Kreuztisch.Dann baute ich mir eine Portalfräse.Irgendwie bin ich auf den Planetcnc Controller gestossen.Denn habe ich genommen.
Zum Schluß wollte ich wieder umsteigen auf LinuxCNC.Habe mir dann eine MESA 7i76E gekauf und einen VFD mit Spindel.
Dann wurde ich krank und das Geld wurde knapp.Da verkaufte ich die Karte und Spindel wieder.

Jetzt habe ich nur das USB Board,die Motortreiber(Endstufen) und meinen Schaltschrank denn ich damals gebaut habe.
Ich habe sogar einen Pendant gebaut.Als USB HID Device,mit einen Teensy 3.2 und Joystick/Keypad.

Jetzt wollte ich das WHB04-4 Handrad in Planetcnc integrieren.Geht aber irgenwie nicht.Habe die .rules geändert usw. ......

Ich habe mir gedacht,man könnte die 26pin Schnittstelle verwenden.Ohne viel umzuverdrahten.

Hab gleich einen Termin.Melde mich wieder.

Grüße-Martin

---

Hello Michael,

Thanks for your answer.I started with LinuxCNC back then (about 8 years ago).I had a TB6560 board from Modellbau Letmathe.I started with a (China) cross table.then I built myself a portal milling machine.somehow I came across the Planetcnc controller.because I took it.
Finally I wanted to switch back to LinuxCNC and bought a MESA 7i76E and a VFD with spindle.
Then I got sick and ran out of money, so I sold the board and spindle again.

Now I only have the USB board, the motor drivers (power amplifiers) and my control cabinet that I built back then.
I even built a counterpart as a USB HID device with a Teensy 3.2 and joystick/keypad.

Now I wanted to integrate the WHB04-4 handwheel into Planetcnc, but somehow I couldn't. I changed the .rules etc. ......

I thought you could use the 26pin interface without having to rewire much.

I have an appointment in a few minutes.

Greetings-Martin

For configurations with specific daughtercards, the daughtercard 
name is included in the file name and you can use the .pin file
to determine the content and pinout of the firmware, for example
the 7i76eu_7i76x1_pktv2d.pin file shows that the configuration
includes a V2 PktUART ( the TX and RX halves )

7i76eu_7i76x1_pktv2d.bin 

Would be the correct firmware

You will also need to update LinuxCNC to the lastest version
sine the hm2_modbus driver is quite new.

 

thank you.
I know I need to update / flash my 7i76eu.
The "bundle" from your webpage contains 20+ different firmware files... I would assume that 7i76eud.bin/pin are the correct ones, right? (for a standalone 7i76eu without any extensions)

Hello y'all!
I just received my new mesa 7i76eu, and I have a huge CNC with a durapulse GS10 vfd (until now it was runnnig with grblhal).

Does "pktUart" allow me to connect my GS10 vfd directly to the mesa without a usb dongle?

Regards!

Saw this old iron while entertaining the machinery buying itch today on Kijiji -- www.kijiji.ca/v-other-business-industria...i-hit-18s/1716314528

That link will go dead with time, so for the record it looks like a Hyundai HIT 18S for $2k Canadian, not working. Seller says it has some repaired drives. I probably need to ask more questions, just not sure what all the right ones are.

Seller might be asking too much, but says he's open to offers. Any thoughts from more experienced heads here, whether or not something like this is worth a look and a retrofit? Or should I be running the other way fast as I can? I don't have any impressions, good or bad, about Hyundai quality, and I'm not sure what dead machines should generally go for.

On the scale of difficulty for retrofits, where does a machine like this fall? I'm no expert with HAL but have dabbled a little. Built my own plasma table with 7i76e and a couple THCAD's by riding on the shoulders of giants on this forum.

Thanks in advance for any time you spend looking at this.

Hi langdons! Thanks for your question!
Yes the VFD has more than one output. One +24V for maybe switches or relays, two relay outputs and one +10v output that puts voltage to the electronic potentiometer on the 7i76e. The mesa doesn't have such a voltage output on board, so you have to give that from an external source (eg the VFD 10V out) to the spindle+ input. The spindle-output then gives the 0-10V voltage correspondingly to the set rpms back to the VFD's analog input and, if the FWD signal is on, the spindle turns.
In my case, the rpm output voltage AND the spindle.enable = spindle.on signal is only given out from LCNC if I do this from a file. Normally - and any time before, this works even with any MDI speed command.

So - the VFD (now) works as it should but LCNC has problems to give the right MDI Commands as ordered to the outputs of the MESA card.
The VFD had no +10V on its H output as it came to me, from the dealer, new product, no NOS, freshly produced 3 years ago. I wasn't ready to build that thing in because I was busy with the mechanic part of my CNC. I put some parameters in the first weeks, but no real testing with any controller, so I didn't mention that problem. I found that few weeks ago, as I installed the VFD and tried to get the spindle turning. And found that there is no +10V at Out H. Then, the external 10V source, but I wanted the VFD beeing allright, so I sent it to Hitachi for Service.

I wasn't able to go down to my machine the last days, but I will make a video of that process the next days.

Kind regards!