Advanced Search

thank you Peter,
That got rid of the error there but it points now to an error on Hal line 25: empty variable name. I don't know how lines are counted no matter how many ways I counted them it did not make sense to me.
I so very much appreciate your help, I have spending days with AI trying to get this figured out to no avail, you forum experts know this stuff!!!!
Grorge

Already replied on the other thread:
forum.linuxcnc.org/9-installing-linuxcnc...nc-2-9-8-mesa-7i76eu

This section of the hal file is broken in at least 3 ways:

loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS
#loadrt [KINS]KINEMATICS
loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=1 num_stepgens=4 sserial_port_0=2"
#loadrt hostmot2

1. loadrt [KINS]KINEMATICS is commented out
2. loadrt hostmot2 is commented out
3. loadrt hostmot2 is in the wrong order (it must be loaded before hm2_eth)

It should look like what pncconf creates:

loadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS
loadrt hostmot2
loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=1 num_stepgens=4 sserial_port_0=2"

Hello all,
I am a newbie and I might have posted this question on the wrong thread before so I apologize for my lack of knowledge and experience. I have got my board and pc communicatiing and I think I have fixed most of the error but until i get this one fixed I won't know. I have an error which seems to be misidentifiying my z axis. I have a xyyx router setup hopefully to get y  squaring. The error I am getting says an undefined kinematicsSwitch and it leaves my setup with undefined limit on z. All help will be greatly appreciated. I will post my ini and hal files for you to look at.
Thanks again,
George

        Thank you for for your assistance, i VERY MUCH appreciate it.I am having problems with my hal files and my ini files no matter what i do i keep getting the same error message kinematisSwitch not defined. If I could get you look at my ini and hal files I would be eternally gratful. I have got past the communication errors and my pc is able to communicate with the 7i76eu I think I have most errors fixed now but unitl I get this current error out of the way I don't know if ther are anymore. I am not sure if this is the right place to ask, so please excuse my inexperience. Thannks again
George

I am working at tuning some older digital (step/dir command) servos, that don't have any auto tuning capabilities.  In order to avoid needing to use an  oscillo scope I would like to be able to connect a square wave siggen signal to the velocity command input of an unused stepgen on a 7i76eu (I also have a 5i85 for encoder feedback.)  I loaded the siggen, and made the hal connections, set all the parameters and enabled everything from halshow.  I can see the input for the stepgen's velocity-cmd changing, but I don't think any steps are being generated (no changes of any of the stepgen's count or feedback pins.  

Where am I going wrong?  Is this another situation where changes to parameter pins are only effective in a hal file at startup?

I was hoping to just create a little hal file that I can load manually after Linuxcnc was running to set tuning parameters then plug one of the drives step/dir plugs into the testing plug to run the tuning (moving them back to their regular position when running.)

Great, i forgot to ask that

If i get a USB pendant, do i need to have an MPG interface on the controller board? (like the Mesa 7I76EU) or can i just use the USB communications into the LinuxCNC PC? Not sure if i need to connect the pendant to the PC or to the controller.
Any help would be appreciated.

Thanks.

There is no timing issue but they are only settable in the hal file (that is they are only set when the driver loads),
it may be that the way the hal file parsing order works means that they must be in the postgui hal file

Thanks for the reply PCW. The issue I'm running into is that it seems the source/sink masks are only "settable" in my postgui HAL file, which runs after the HAL and GUI start up.

If I move the setp commands to set the masks into my main HAL file, either near the top or last, they don't seem to take effect despite "getp" showing them as being set. I can't put the masked pin into the proper mode (sinking in my case).

When I put them in my postgui HAL, or manually set them with setp after linuxcnc startup, it works just fine.

I'm just wondering if there is some timing constraint when it comes to setting these masks that launching the GUI is covering up.

Thanks

One output, but three resistors...

Unlike sserial pins, you can only "setp"  sserial parameters (like the source and sink masks) in LinuxCNCs hal file,
they cannot be  changed dynamically. This is true of all sserial parameters, that is, they are only updated on driver startup.

The output modes are something typically set to match the interfaced hardware, so do not need to be changed dynamically.

 

Perfect, thanks

Yes you can use just one output

Hello all, I am trying to configure `output_sink` and `output_source` pins for my Mesa 7i76eu and I am running into some surprising behavior. My goal is to put `hm2_7i76e.0.7i76.0.0.output-11` into sink mode. 

Long story short, putting `setp hm2_7i76e.0.7i76.0.0.output_source 0x0000F7FF` and `setp hm2_7i76e.0.7i76.0.0.output_sink   0x00000800` in my HAL file after loading `hm2_eth` does not seem to have any effect, output-11 remains in sourcing mode. I spent some time debugging this and found some surprising results.

The first thing I did was attempt to setup the pins manually without changing anything in my HAL file. For this test, my HAL file did not set `output_sink` or `output_source` at all. On a fresh power cycle of both my computer and the mesa card, the following works correctly (causes output-11 to sink when TRUE).

```
halcmd setp hm2_7i76e.0.7i76.0.0.output_source 0x0000F7FF
halcmd setp hm2_7i76e.0.7i76.0.0.output_sink   0x00000800
halcmd setp hm2_7i76e.0.7i76.0.0.output-11     TRUE
```

I can toggle output-11 back and forth between TRUE and FALSE and it appears to work just fine. The strange part is that if I set output_source = 0x0000FFFF output_sink   = 0x00000000 (going back to the default value), `output-11` remains in sinking mode, it does not switch back to sourcing mode. The only way I can get it to switch back is if I power cycle the Mesa card.

The second thing I tried was setting `hm2_7i76e.0.7i76.0.0.output_source 0x0000F7FF` and `setp hm2_7i76e.0.7i76.0.0.output_sink   0x00000800` as part of my postgui HAL, the thinking being that maybe there is some timing issue for when you configure the output pin modes. This does seem to work as long as I do a power cycle of the Mesa card and computer, but it feels like a bit of a hack.

I'm using this setup to control activation of a wireless probe receiver which needs `output-11` to sink to ground in order to activate the probe, so my main worry is that I'm just hiding a timing related issue by doing this in postgui and will end up running into a crash down the line. If anyone has some insight into how `output_source` and `output_sink` are supposed to work, that would be appreciated!

Thanks!