Advanced Search

 
Hi Guys!!

I decide to configure a 5 axis machine for my project, but my knowledge is not as those guy on youtube, but i wish the linuxcnc community could help with their knowledge.

using vismach 5 axis configuration on a mesa board 7c80. Installed linuxcnc on my rasberry 4.   
xyzac-trt.hal keep changing every time i run linuxcnc but I know that they are related with a file *.tcl on hallib but my question can I delete those files and only use *.ini, *.hal only using those files that are essentially need it. 

also do I need to use all the parameters of 7c80 to make the axis to move?
because the I had identified that the linuxcnc only used some of themhm2_7c80.0.stepgen.00.control-typehm2_7c80.0.stepgen.00.countshm2_7c80.0.stepgen.00.dbg_err_at_matchhm2_7c80.0.stepgen.00.dbg_ff_velhm2_7c80.0.stepgen.00.dbg_pos_minus_prev_cmdhm2_7c80.0.stepgen.00.dbg_s_to_matchhm2_7c80.0.stepgen.00.dbg_step_ratehm2_7c80.0.stepgen.00.dbg_vel_errorhm2_7c80.0.stepgen.00.enable               x-enablehm2_7c80.0.stepgen.00.position-cmd         not usehm2_7c80.0.stepgen.00.position-fb          x-pos-fbhm2_7c80.0.stepgen.00.position-reset       not usehm2_7c80.0.stepgen.00.velocity-cmd         x-outputhm2_7c80.0.stepgen.00.velocity-fb                  not use

Trying to configuration with xyzac-trt.ini and xyzac-trt_cmd.hal. without any success on it.
can someone help give some extra info. get the axis moving. 

thanks for your time.
 


 

hey Giovanni

did you use virtual box for your VM

i am about to try your guide again using virtual box and a stock standard linuxcnc iso 2.93 install

just thinking i could just grab your vm file and work back from there if you used virtual box

cheers

Andrew 

Yeah, i should gave the details in the previous post. Sorry. 
H-bridge in question is popular module based on two BTS7960B half bridge chips.
As per data sheet:
- PWM up to 25 kHz
- 5 V logic for control is ok
- two inputs for control should be ok: CW PWM and CCW PWM.
- two inputs for CW enable and CCW enable

Looks like i'll need 3 PWM generator pairs (used in mode 2: PWM up, PWM down) to drive 3 motors and i think i can use enable signal from LinuxCNC to drive CW/CCW enable inputs so when machine is off in LinuxCNC motor will be free rotating.

 

There is no error.  It’s informational.  There’s over twenty logs of updating to 001.017 in the update log file.

As I said, expecting handling is present:

github.com/LinuxCNC/linuxcnc/blob/0e1f56...asmac/updater.py#L31

github.com/LinuxCNC/linuxcnc/blob/0e1f56...asmac/updater.py#L42

Nonetheless all of that is irrelevant; something’s up with your installation/OS.  All of the issues you mentioned have been taken care of for some time now. 
 

update_log.txt


machine_log


Clearly there is no error reporting to the screen or to any log. I checked the screeen handler code. My comments about exception handling lacking stand.

In particular, that update is looking for 'nc_files/plasmac/m_files' in your USER_M_PATH, to be able to see the Mxxx files. It’s not seeing it so it’s trying to update the ini file to fix it.

Perfect that's where they're supposed to be:

Your previously advised location was different. What is correct?

I installed the latest package on buildbot2 for bookworm a few minutes ago, it opened the qtplasmac_l_metric simulation without issue, no update messages, etc.

That would be expected. You would need to install on 2.94 then upgrade to 2.10 to replicate the issue. Confirmed behavoiur on 2 different PC's

This was fixed on Sept 6, 2024. Commit notes:

This was not fixed for sims because I installed packages dated Feb 2025 from the buildbot. Bug remains. 

Did you think it referred to QtDragonHD, or Axis?

I suppose it could say something to the effect of "QtPlasmaC configuration changes mandated at V2.10-001.017 were applied". As a developer it's not always easy to know how the end user will interpret a message. Since January 23, 2024 you are the very first to complain.

I had no idea as Axis, QTdragon and QTplasmac.sim configs were installed on my PC.
Clearer messaging would be nice 
I had a specific reason to test upgrade from 2.9.4 to 2.10.

There must be something going on with your OS/Installation. Simulations work fine on version V2.10-008.056 for a Package install and V2.10-008.061 for RIP. No update messages.

Sadly, the buildbot must be stuck again if it is that far behind for a package install done yesterday.
You would need to build for 2.9.4, install the sim, then open the config in 2.10 to replicate this error. Installing on 2.10 proves nothing as no upgrade will be triggered.

I can't use RIP given my customer is 1000 miles away and I want him to upgrade to 2.10 becasue you are no longer supporting 2.9

PC is running Trixie with kernel 6.12. But it also happened on a Bookworm PC. I think Debian version is irrelavent. (Trixie is only a couple of months away and 2.9.4 will be in it)

Click the Statistics tab, there's a MACHINE LOG frame, it'll be there. machine_log_{date/time}.txt in the config folder also reflects the log on the Statistics tab. It's also in the "update_log.txt" file in the config folder.

There is no erors in any of the MACHINE logs. There is no information in the update logs. We need better error reporting.