Advanced Search

I try man hm2_modbus
and man mesambccc
not exist in my linuxcnc i have the last version 2.9.4 i see in linuxcnc official site this is the last version, if there is newest version tell me please
 

Hi all,I’m running into an issue with my 7i77 analog outputs and could really use some help figuring it out.Setup:

• 7i94 + 7i77 + 7i84
• LinuxCNC with Mesa HAL configuration
• QtDragon GUI

The issue:

• When I set hm2_7i94.0.7i77.0.1.analogena to True, I measure about 0.3V on all +-10V outputs, even without setting any value on an analogout<>.
• When I set a value on one of the analogout<> pins (e.g. analogout2 = 0.1) and leave analogena False, I measure no voltage on the corresponding output.
• What I expected:
  • No voltage at the +-10V outputs just by enabling analogena.
  • A voltage at the specific output only when both analogena is enabled and an analogout<> value is set.

My question:

Is this normal behaviour, or am I missing something in the configuration or wiring? What should I check next to diagnose this? 

 



​​​​​​​ 

This is what caught my eyeMaybe the hardware has past its best before date?

I feel like when I calling Microsoft customer's support...
"We dont know what is your problem, but it works with us..."

I know how Linuxcnc does the threading, and know why it is acceptable with LPT and not acceptable with devices using ethernet link.
LPT uses base_thread, ethernet uses servo_thread, so LPT can be ten times faster.

I told you few posts ago, the servo_thread=1000000 (1 ms period) can make delay that can produce 18 degrees positon error at spindle rotates 3000 rpm.
3000 rpm => 50 rps => 20 ms per revolution.
It is mathematics, everyone can make this calculations.

The solution is not send the extended index in hope the Linuxcnc see it, and resets position to zero when received it.
The solution is send raw_count latched at every real encoder's index edge.
We can restore encoder's index (if we need) from (old != new) at the component.
And we can reset position not to zero, but to real position captured at index edge.

We can be confused, because we use "index" word for different meanings (encoder's output, program variable, hal pin) but we can not change this.

Detailed explanation:
Let's assume the encoder's index edge occurs at 1000 raw_counts.
Time goes, counter counts A/B signals.
The component requests data.
At this moment raw_counts is 1050.
We send both values, counted and latched.
The component knows, the index was 50 counts ago and sets position to 50/scale not to zero. (of course only when hal index_enable pin is set)

What don't you understand?

I didn't want attached my project as offtopic, but I see I must.

You're either missing parameters in your var file or you need to update for the latest fix which was done shortly after the latest push was released due to a format error. If you verify your car has the correct car numbers listed so parameters can be saved persistently t then it's an update you need to run to resolve.

Please upload it. Or better yet make a quick video showing your hacking so we can all learn more.

Thanks!

Hello,

I am trying to find the answer to the question why do my axis view preferences not stay persistant between sessions.
Actually some options are persistant like show offsets or alpha blend program.
But some important ones are not like display inches (always opens to mm) and show pyvcp panel.
I have searched the forum and chatted with chatgpt for a few hours now and frustratedly cannot get my machine
to turn on with inches displayed. I have tried to make .axisrc file but that never seemed to do anything.
Does anybody have any ideas? Thanks.

Interesting product. Any idea if your sensor works with PLLA (plastic/polymer)?

Can't test at the moment as the intended laser systems aren't ready yet, but might be interested in testing and/or purchasing units soon.

ok, nevermind.. I rewrote the file from scratch and now its working.. not idea what happened before.

yes. sorry. i did not mean to compare anything in a bad way. i only meant Ethernet. in fact, RIO also needs CPU for ethernet, it just placed outside of fpga in UDP2SPI Bridge with STM32.
i hope i got the difference in data frame at least, RIO has fixed static data frame while Mesa has dynamic data frame configured by reading IDROM at the driver initialization.

Posting the actual hal and ini files would be more useful.
Can't tell much from just part of the hal file.

 

Hello!
I just tried to compile a modbus file according to this documentation:
linuxcnc.org/docs/2.9/html/drivers/mesa_...#_configuration_file

I attached the file that I created, and imho it looks fine, but the compiler just throws a bunch of errors...

What am I doing wrong ?

Edit: compiling one of the modbus sample files works fine.. no idea why my file doesnt work... I copied it directly from this post from PCW (as its the same VFD)
forum.linuxcnc.org/27-driver-boards/5533...us-so?start=0#321582


 

1. Sí, puede usar la salida SSR 7I96S para encender la linterna. Sugeriría usar out4 o out5, ya que tienen un mejor aislamiento de voltaje que las salidas 0..3

2. Creo que el truco con pncconf es seleccionar primero la GUI de QtPlasmaC y, a
continuacin, configure el codificador (en la pestaa TB1,TB2) para "Voltaje de
arco"

3. Creo que la mejor manera de responder a estas preguntas es mediante una
conexin a tierra/proteccin EMI ms general Documentos. Puede hacer una bsqueda
en Google de "mquinas de plasma de puesta a tierra" o Similar
 

The OP may need to update LinuxCNC to the latest 2.9.4 or 2.10

I'm not an expert in this as I usually use a built from source RIP installation
 

Hey tux, Im getting the feeling of deja vu. Didnt we go over this a few years ago? Its been explained both times, that this is how LINUXCNC does the threading, not just remora. You are also not the only person doing threading with the EC500, Remora, or LinuxCNC. Are you sure you have the encoders setup correctly? Ive seen you mention several times you dont know how to set up the index. Maybe it would be helpful to post your ini/hal/config.txt? 

You shouldnt take it personally if we dont understand the issue you are having. If you dont like the way we conduct our selves, you are free to fork the project. This way, you do not need to feel like you are at the mercy of the author. No one needs to throw a tantrum, you can point out the issue, and if it is not addressed in a way acceptable to you, make a fork, and correct the issue and move on with your day. We appreciate your input on the issue, but dont take it personally if the issue isnt addressed in the way you want.

But you appear to be unsatisfied with every single one of the remora projects, and every opensource cnc project in general. Maybe the Remora project needs to learn by example. Feel free to fork the projects and show us how it should be managed.

I look forward to testing out your new project thought. All the best, and I assume the documentation and instructions will clear and not misleading. I have faith you will retain interest for more than 1 month before moving on.