Advanced Search

That is a cool trick! Glad to know about Show Hal Configuration. Thanks.

I am using the Axis GUI.

When I watch the ESTOP-ext variable (is variable the correct term here?) I see that it changes state when I toggle the hardware ESTOP. Hal Show Configuration shows yellow when the hardware ESTOP is not active and red when the hardware ESTOP is active. That seems right to me.

When I watch ESTOP-out, it just stays red the whole time regardless of what I do in hardware or software. This seems wrong to me, but it is also consistent with the problem I am having.

I don't have any of the qtpyvcp pins listed in any of my hal files - but they're still loading.

I get that connections to any of the qtpyvcp hal pins needs to be done in post-gui.hal.

Would you mind trying to create a qtpyvcp hal pin like I'm attempting and see if you can make it work?

I don't want to start fiddling with the main probe_basic.ui file, but you or one of the other devs might have some test configs to see if you all can figure out if this is just me or a bug.

the user tabs get loaded after so they may need to be loaded through post gui hal so they get initialized during startup otherwise they may be created after the initial ui loads but before the child ui is loaded. but just guessing as i have not tried what you are doing before with halpins,. if you have them listed in the main hal file i would move them to the post gui and retest.

just loaded up a new computer today and copied and pasted the config and it just works.  conversational stuff all works fine.  which shows there are not library's that are needed.  its all internal to the config files

the file auto loads also with axis load remote file feature.  so i am not getting the bug that tuxcnc got earlier.  however i am using axis gui so other gui's might have issues.  can't be bothered currently supporting the other gui's but i might if more people post here and are using the software.  but no stress.
 

If using Axis GUI (other GUI's may also have this), use the "show hal configuration" from the machine menu to see if the hal stuff is working correctly, on the left side choose the pins to watch on the right side, then toggle e-stop and see what toggles and what not.

Here is fixed firmware fro the 7I76EU/7I76U that fixes the MPG encmode
parameter direction issue. This is the full image that needs a PIC programmer
to install. Will have a bin file for remote updating soon.

 

Now is it possible you have a 7I85S instead of a 7I85?
(look at the paper label on the back of the card)

That would show these symptoms ( only the last sserial channel works
as TB1 pin 17..24 is the only serial port on a 7I85S )

 

OK tested a 7i76E with 7i76e_7i76x1_7i85x1D.bit firmware:

md5sum 7i76e_7i76x1_7i85x1D.bit
0d0922e5c4306ceba4e077fff3c02097  7i76e_7i76x1_7i85x1D.bit

And it works as expected, that is sserial devices 0..6 work

SSerial channels are organized as follows:

0 Local 7I76E field I/O
1 7I76E Serial expansion slot TB3 15..20
2 7I85 Serial 0 TB2 9..16
3 7I85 Serial 1 TB2 17..24
4 7I85 Serial 2 TB1 1..8
5 7I85 Serial 3 TB1 9..16
6 7I85 Serial 4 TB1 17..24

 

I also use DeskProto, and it's impossible to configure it the way you want. One axis, either X or Y, is always static above the rotation axis, and in that case, you won't be able to create undercuts.

I recently created my own program that could move in both X and Y simultaneously, but so far I haven't succeeded (with a helper, of course). One cool thing I managed to achieve is variable milling density, depending on the slope of the milled slope, so that on flat sections, the milling isn't too dense, but on steep slopes, it's not too sparse. I haven't seen this in other programs, although I haven't seen everything. The program works well, but it won't create undercuts. Maybe someday I'll resume working on true four-axis machining.

Sind die servos die step/dir oder analog eingang?
Wen step/dir dan Mesa 7i95T ist die beste losung und die infachste zum werbinden, aber schwer zu finden...
Gluck, es gibt beim Welecctron im Deutschland
www.welectron.com/Mesa-Electronics-7i95T...-Ethernet-Controller
Fohr die analog, dan die 7i97T ist die selbe wie oben mit analog ausgange stat step/dir und 6 encoder eingange.

Ja bezüglich der mesa karte, wie ist das mit Latenzen? Welche würdest du empfehlen für 5achsen servos mit encodern?

Dear PCW,
1.) Ok, understood. Since I connected 3 boards (2x 7i84, 1x 7i87) I should thus see only 3 SSerial. I was confused as the pins from one of the 7i84 connected to SSerial position 4 on the 7i85 is visible under this name: "sserial device at channel 6: 7I84 (unit 0x1800C0A7)" (string taken from --sserial command using mesaflash).
2) Yes I read this also somewhere else on the forum and made a new machine configuration in pncconf using this option. If I look in the hal file made afterward I indeed see a modified config string in loadrt hm2_eth:  'sserial_port_0=0000000x' and the number of encoders increased. However, unfortunately the other 7i84 and the 7i87 are stil not visible (these are connected via other SSerial channels on the 7i85 other than the one numbered 4 in the manual.
3) This evening I wired an encoder and checked it on all the 4 available enc positions (0, 1, 2, 3). I do see the steps increase/decrease in the watch window of halconfig. The signal pin names I look at are: hm2_7i76e.0.encoder.00.count up to hm2_7i76e.0.encoder.05.count. The enc. 0 (identifier from MESA manual image) corresponds to ....00.count and enc 4 to ....03.count. All seem to work nicely (cool to see this work!)
4) Off course I would appreciate this a lot. I also looked at the naming of a digital input from one of the 7i84 when connected via SSerial 4 (MESA manual image) on the 7i85 and this shows as : hm2_7i76e.0.7i84.0.6.input-00 and so on. These digital pins also work in this configuration Again I don't understand where the 6 comes from. In case I connect the same board to any of the other SSerial positions on the 7i85 than they don't show up at all.

To add to Todd's list:
-most often and by far the main reason such transformers fail is incorrect wiring, and no i do not mean messing the 3 wire plus ground wiring, i mean the input wiring on such transformers, reason being they all have multiple input voltages that can and should be set by moving metal bars on certain screw posts for certain voltages, giving two failure options:
1. incorrect voltage selection set - when set lower than actual voltage causes higher current draw and subsequent heat, so failure is slow and usually ignored until to late
2. incorrect windings set with the metal bars causing huge current draw and distinct buzzing noise from the transformer, leading to overheating and burning of the windings in a short time.
The thing is, in both cases the machine works, and due to the noises all machines make drowns the transformer noise, leading to failed transformer noticed only when it is to late to do anything about it.
-
Personally from experience, that is the first thing i check on any machine with input transformer, seen to many go to waste as local "experts" will never learn that we do not have 3x220V here, we have 3x380V here, only when using neutral we have 220V. It is sickening the amount of transformers and spindles/VFD and servo motors/drives i have seen burned here because of that.

Ich kan nicht uber die EtherCat garnicht sagen, aber fuhr Mesa hab ich uber 20 machinen umgerustet, und nie ein fehler gehabt, mehr als 15 jahre lang.

Hi, 

I am retro-fitting my 1968 Bridgeport Series 1 Papertape NC machine with rpi5/Mesa7i96s/Gecko203v.

I've got everything working pretty well it seems, except for the ESTOP.

I have (and want) an external/manual ESTOP-in button.  It is currently setup Normally Closed and appears to be successfully plumbed through to the GUI, which is to say that the GUI ESTOP button tracks the status of the hardware ESTOP-in button perfectly.

The issue is that my ESTOP-out is no-longer tracking either the GUI ESTOP or the hardware ESTOP-in.  It just stays asserted all the time with no change of state.

To be clear, before I attempted to plumb in the hardware ESTOP-in button, my GUI ESTOP was correctly plumbed through to my ESTOP-out so that it would allow me to disable the steppers.

Aside: I have not been able to find any documentation that really explains how ESTOP is expected to work?  I'm unclear on if I should work with estop_latch or not?  The estop_latch documentation is also pretty thin and does not appear to include any examples for either simple or complex configurations?

Here is my current configuration... (generated by pncconf)
Thanks,

B