Advanced Search

Hello everyone.

I have a report. The problem has been solved.

There was a misinterpretation in the HAL file I wrote.

I moved the two lines

addf motion-command-handler servo-thread and
addf motion-controller servo-thread

before the PID-related lines.

As a result, Homingd operation became normal.

I read the manual carefully and thought that if I understood it, I would not have to apologize for the order of writing.

I am Japanese, and it takes a lot of effort to understand English manuals at the same level as Japanese. Even when reading a Japanese translation, there are some parts that do not match the original English text.

If there is a part that describes the position of writing such as addf motion-command, please let me know. I would like to understand it well. Thank you for your valuable advice, andypugh.

Thank you.

That worked thank you!

If the 7I95T actually resets, that's a power supply issue.

What error?

Hi all 
after working for 1 hour without any issue the 7i95t randomly resets with error in raspi b 8gb. I have a dedicated heat sink with fans on the raspi b. I am using latest linuxcnc 2.9 image for raspi b given on the website.  Please let me know the reason if anyone has faced a similar problem

cool

Mesaflash needs the firmware file to be in the current directory (or be given a valid pathname)
Note: 7I96 uses .bit files, 7I96S uses.bin files

The firmware files can be downloaded from mesa's store
in the specifications tab. This zip file contains currently available
firmware for the card.

The actual firmware files are in the zipfile in /configs/hostmot2/
 

Oh gosh. That was a goofy mistake I made, thank you. 

Now I am getting the error '.bit file not found'. I also tried the .bin extension and got a similar error... There is a list of the possible files somewhere online right?

You always need to supply the IP address with Ethernet cards:

mesaflash --device 7i96s --addr 10.10.10.10 --write 7i96s_7i85d.bit --reload

(you also do not need sudo with Ethernet cards)

Hi Benb,

Thanks for your reply - pretty much exactly what I am planning on doing, in the past I have found that re-using the wiring loom on a machine can save days of time - particularly if it is well done in the first place. There is also the added benefit of all the high quality connectors and cabling that are already in place on the machine side.

The machine came with a fourth axis so I'm going to get that working in isolation before starting on the machine proper...

Thanks for the suggestions.
Greg

Has anyone actually run these servos? I'm trying to tune these, which was going well. However I'm having an issue where the drives randomly develop an offset. Not following error. I can use the pendant and the same offset stays.  I can manually force the motor back and forth, and the offset stays. When I turn the drives off, and on, the offset dissapears. I put a dial on and the offset is real. The encoder is not loosing position, it seems to be something in the drive. Any ideas? Anyone seeing this? Anyone not? 

Hi,

I am trying to flash my mesa 7i96s so that it can work with my 7i85. 

When I use the command 'mesaflash --device 7i96s --addr 10.10.10.10 --dbname3 7i85s --readhmid' I am getting a read out from the board (the pin funcs under 7i85d say "none". But when I use the command 'sudo mesaflash --device 7i96s --write 7i96s_7i85d.bit' mesaflash is saying "No 7I96S board found".

Does anyone know what is going on here? Thank you.

You could try reducing the servo thread rate to 2 ms
(and all stepgen P terms to 500)

You could also see if pinning the Ethernet IRQ to the top processor helps:

 

first chmod +x pinirq.txt
then
sudo pinirq.txt [ethernet device name]

And see if that helps (it will only last until a reboot)


 

Thanks
Haven't gotten back to the touch probe stuff but hope to soon.

Currently a couple other issues. The first is definitely PB related.
Every time I start PB it puts the coordinate readout in inches when linear units is set to mm in the ini.
G21 does switch it but it's still annoying. How do I set it so everything starts and always stays in mm?


The second I don't remember if this was an issue in other UIs but if I hit home x or y it does not lift Z before homing.
I see there is a go to home file in subroutines which I assume is used for home all but don't see anything specifically for individual axis. Would I need to create a subroutine for x and for y to get it to Z0 before homing them?

Hello, is it possible to create "internal buttons"? I mean not a physical button, but only in the software e.g.