Advanced Search

Search Results (Searched for: )

  • tommylight
  • tommylight's Avatar
04 Mar 2026 22:14
Replied by tommylight on topic 7i92T and mx3660 request for help

7i92T and mx3660 request for help

Category: PnCConf Wizard


Funny, the homing was INVERTED in Stepconf, but now is not in Pnnconf. Also the latest Pnnconf instructions do not match the Pnnconf I see on my machine. ????? documentation must be lagging I guess, realize everybody is busy and this is a free program......

 


Parallel port requires pulling inputs down to trigger,
Mesa can have inputs set for pull down or pull up, in hal
Mesa can use all pins as inputs or as outputs, in any combination, and they are much, much faster than parallel port, so it is impossible to have all possible combinations in a wizard.
  • ClarkSavage
  • ClarkSavage
04 Mar 2026 21:27
Replied by ClarkSavage on topic 7i92T and mx3660 request for help

7i92T and mx3660 request for help

Category: PnCConf Wizard

Ok, changed all in_out to in and the axes and everything stays enabled - I can jog them. They go in the right direction.

Since I have changed all the limit settings will revisit that later. Many thanks. Your in the run.

Now I need to play with getting my homing back to normal and get the axes unlimited and start uncommenting other stuff too.

Funny, the homing was INVERTED in Stepconf, but now is not in Pnnconf. Also the latest Pnnconf instructions do not match the Pnnconf I see on my machine. ????? documentation must be lagging I guess, realize everybody is busy and this is a free program......

Thanks again.

Thanks again, will report back once I can settle down and get this part straightened out. 

 
  • Lcvette
  • Lcvette's Avatar
04 Mar 2026 21:24
Replied by Lcvette on topic Probe Basic DRO display appears blank

Probe Basic DRO display appears blank

Category: QtPyVCP

kcjengr.github.io/probe_basic/update_notes_stable.html

follow the docs for sa new installation and machine configuration setup. the instructions are there to setup as is needed.
  • hitchhiker
  • hitchhiker
04 Mar 2026 21:23

EMCO Compact 5 cnc Turret with dc motor and no feedback

Category: Advanced Configuration

I start with a pyvcp panel...
Drive fwd 1 station button calls in section in my comp
Set tool 1 button calls m61q1

Then i add buttons tool1 tool2.... tool6 to call m6 t1....t6

If i hit drive fwd 1 station it rotates exact 1 station fwd. goes then backward and reduce pwm to get it locked against the pawl.

Now i check temperature ever 15 minutes of driver and dc motor.

Next step is calculating the distance from actual tool position to taeget tool position.. like from tool 1 to tool 6... or from tool 6 to tool 3... handling the rollover would be interesting... we will see in the next days.

If this done is the last step the movement... with the calculated distance on position to go forward i can multiplie with the forwardtime from position to position.. the locking part is not so sensitive.

So we will see... toolchanger without feedback... very oldschool... complete openloop.
  • my1987toyota
  • my1987toyota's Avatar
  • PCW
  • PCW's Avatar
04 Mar 2026 20:56
Replied by PCW on topic Trying to set up position control mode

Trying to set up position control mode

Category: HAL

Ok those work properly (step generator action is correct)
I suspect the problem is with your jogging setup.

( Which I cannot check unless you include the missing custom.hal
and custom_postgui.hal files )
  • PCW
  • PCW's Avatar
04 Mar 2026 20:17
Replied by PCW on topic 7i92T and mx3660 request for help

7i92T and mx3660 request for help

Category: PnCConf Wizard

Well the first thing is that all home switches are inverted...

The need to be false (dim red) when not activated and Yellow when activated.

(whoever chose those colors should be punished somehow...)
 
  • ClarkSavage
  • ClarkSavage
04 Mar 2026 19:27
Replied by ClarkSavage on topic 7i92T and mx3660 request for help

7i92T and mx3660 request for help

Category: PnCConf Wizard

Yes, I am just confusing myself now.

Yes, looked at Halshow - never done that before so I read a little and then picked what I thought would give the best info.

So, I re-enabled the Y & Z both home limits. All home switches active. I made sure for each test I over road the limits and enable/active Axis display before moving any switch and I got the following. Screenshot is ENABLED base Halshow.

 

Then I methodically tripped switches + and recorded what happened.

For the limit switches at both ends of each axis:
  • joint.0.home-sw-in [my 7i92 X] yellow turns red when either switch tripped, then back to yellow on release
  • joint.1.home-sw-in [my 7i92 Y] yellow turns red when either switch tripped, then back to yellow on release
  • joint.2.home-sw-in [my 7i92 Z] yellow turns red when either switch tripped, then back to yellow on release
Charge Pump:
  • charge-pump.enable yellow
  • charge-pump.out                   blinking yellow / red
  • hm2_7i92.9.gpio.005.in         blinking yellow / red
  • hm2_7i92.9.gpio.005.in_not  blinking yellow / red opposite charge-pump.out
  • hm2_7i92.9.gpio.005.out       blinking yellow / red opposite charge-pump.out
probe:
  • hm2_7i92.9.gpio.016.in             red turns yellow when probe tripped
  • hm2_7i92.9.gpio.016.in_not      yellow turns red when probe tripped
  • motion.probe-input                    yellow turns red when probe tripped
  • probe-in                                     yellow turns red when probe tripped
ESTOP
  • hm2.7i92.0.gpio.003.in            red not change when my ESTOP button active, but changes color when axis display button pushed
  • hm2.7i92.0.gpio.003.out          yellow not change when my ESTOP button active, but changes color when axis display button pushed
  • hm2.7i92.0.gpio.003.in_not     yellow not change when my ESTOP button active, but changes color when axis display button pushed
If you can provide a few hints, I will check and report on other pins. Appears that ALL axis are enabling as long as I over ride limits, and all limit switches are fine if the color should be yellow when the machine is active.

Again, 7i92 connected with short parallel cord directly to mx3660. All limits and ESTOP run through the mx3660 and then would report back to the 7i92.

Appreciate the input. I now have a few things to learn and can see how Halshow sort of works so will check what I have which isn't much - enable, limit switches, Z probe only, external ESTOP.

Finally, I looked everything over for type mistakes but I am kinda deer in the headlights at this time so ask if you think something does not look right.
  • jblanscett
  • jblanscett
04 Mar 2026 19:11
Replied by jblanscett on topic Trying to set up position control mode

Trying to set up position control mode

Category: HAL

Here they are
  • Muecke
  • Muecke's Avatar
04 Mar 2026 18:57
Replied by Muecke on topic Forum Fehler, ... :-(

Forum Fehler, ... :-(

Category: Deutsch

Ich weiß, dass du gut Deutsch lesen kannst. Wenn du Deutsch sprechen möchtest, bist du immer herzlich eingeladen. Dann können wir auch mein Projekt anschauen und weiterentwickeln. :-)Ich kann nur mit einem Übersetzer Englisch, was für mich aber in Ordnung ist.Da du Deutsch lesen kannst, antworte ich auf Deutsch, wenn das für dich in Ordnung ist. Ja, ich finde es auch merkwürdig.Screenshots habe ich im Beitrag davor angehängt, aus beiden Themen, auf die ich nicht antworten kann.Es erscheint auch keine richtige Fehlermeldung, nur der Hinweis, dass:
Error
Kunena Internal Error: Please enable Kunena Debug Mode and report problem in the www.kunena.org forum.
 
  • PCW
  • PCW's Avatar
04 Mar 2026 18:54
Replied by PCW on topic Trying to set up position control mode

Trying to set up position control mode

Category: HAL

Can you post your current hal/ini files that exhibit that behaviour?

Still sounds like a basic hal file issue
  • m0602232
  • m0602232
04 Mar 2026 18:01
Replied by m0602232 on topic Custom homing - distance coded glass scales

Custom homing - distance coded glass scales

Category: Advanced Configuration

I got it working with help of a coder brother and vscode agent by editing mwinterm 's homing files. There were several problems at start which caused inaccuracies in both encoder latched position and home position calculation but now it looks to be accurate. I uploaded quick video of the startup and homing if anyone is interested: www.youtube.com/shorts/St_XhQs68xQ . I also added some nice features;
-the machine offsets are stored within every 2 seconds and those offsets are used as machine offsets at startup before homing, so its kinda like absolute encoders but of course need to be homed to verify position
-custom .py -file checks soft limits before homing and aborts if current position is too close to limit
-also managed to remove homing final move, so minimal amount of movements in homing.

I'm considering if I should share the changed files or not, they are so machine specific. Maybe later when I find out if it's reliable and safe.

Regards
Ossi
  • jblanscett
  • jblanscett
04 Mar 2026 17:55
Replied by jblanscett on topic Trying to set up position control mode

Trying to set up position control mode

Category: HAL

So when we input a jog increment of .1in, the DRO will show a .1 in change and the motor will start moving but won’t stop. If we input an additional .1 in increment in the same direction the motor will speed up and the DRO will show a change of .2 in from the start. If we then input a .1 inch increment in the other direction the motor will slow down and the DRO will show a .1 inch change from the start. 

We don’t currently get any joint following errors. 
  • andrax
  • andrax's Avatar
04 Mar 2026 17:44 - 04 Mar 2026 17:46
Replied by andrax on topic CiA 402 Folder Missing

CiA 402 Folder Missing

Category: EtherCAT

Sorry, my mistake, I misread something.
Your sync errors are gone.
But there is another problem,
Your output ethercat pdos:
[code] RxPDO 0x1701 "RxPDO"
    PDO entry 0x6040:00, 16 bit, "ControlWord"
    PDO entry 0x607a:00, 32 bit, "Target position"
    PDO entry 0x60b8:00, 16 bit, "Touch probe function"
    PDO entry 0x6060:00,  8 bit, "Modes of operation"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
SM3: PhysAddr 0x1400, DefaultSize   15, ControlRegister 0x20, Enable 1
  TxPDO 0x1b01 "TxPDO"
    PDO entry 0x603f:00, 16 bit, "Error Code"
    PDO entry 0x6041:00, 16 bit, "statusWord"
    PDO entry 0x6064:00, 32 bit, "Position actual value"
    PDO entry 0x6077:00, 16 bit, "Torque actual value"
    PDO entry 0x60f4:00, 32 bit, "Following error actual value"
    PDO entry 0x6061:00,  8 bit, "Modes of operation display"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
    PDO entry 0x0000:00,  0 bit, "Gap"
[/code]
Your XML:
[code][code]<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="control-word" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="control-mode" halType="s32"/>
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
<pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="target-velocity" halType="s32"/>
<pdoEntry idx="607C" subIdx="00" bitLen="32" halPin="home-offset" halType="s32"/>
<pdoEntry idx="6098" subIdx="00" bitLen="8" halPin="homing-method" halType="s32"/>
<pdoEntry idx="6099" subIdx="01" bitLen="32" halPin="homing-high-velocity" halType="u32"/>
<pdoEntry idx="6099" subIdx="02" bitLen="32" halPin="homing-low-velocity" halType="u32"/>
<pdoEntry idx="609A" subIdx="00" bitLen="32" halPin="homing-acceleration" halType="u32"/>
[/code]

[/code]
[code]The addresses are missing in the pdos, which is apparently why the errors occur.
However, the addresses are found in the sdos.

I don't know if they need to be configured manually. What does the manual say?
[/code]
  • Atsu
  • Atsu
04 Mar 2026 17:43 - 04 Mar 2026 17:47

Probe Basic DRO display appears blank

Category: QtPyVCP

Hello,

I recently upgraded LinuxCNC from version 2.9.4 to 2.9.8 and updated Probe Basic to the latest version as well. I'm currently experiencing an issue where the DRO display in the Probe Basic GUI appears blank.

Has anyone encountered this before and could point me in the right direction to find a fix? The Probe Basic simulation configuration works fine and the DRO is visible there, which leads me to believe my configuration file is the main culprit. That said, this same configuration worked without issues prior to the update.

I've attached the machine HAL and INI files in case they're helpful.
Displaying 76 - 90 out of 18411 results.
Time to create page: 0.244 seconds
Powered by Kunena Forum