Advanced Search

Live execution of a Bambu 3D printer!!!

Actually, A neat way of dealing with this could be adding a new parameter (5391?) and modify the code so that if it was set to true, the original 2.7 buggy behaivour was restored eg
if settings->parameters[5391] == 0.0{
    settings->origin_index = 1;
    settings->parameters[5220] = 1.0;
}

Be worth playing with that.

 

Pretty sure you would just comment out these two lines
github.com/LinuxCNC/linuxcnc/blob/master...erp_convert.cc#L5177
// settings->origin_index = 1;
// settings->parameters[5220] = 1.0;

1 = G54 so this is where the reset is happening
parameters like 5220 are described here linuxcnc.org/docs/html/gcode/overview.ht...:numbered-parameters

Seems this G54 reset occurs in Interp::convert_stop()
in interp_convert.cc
github.com/LinuxCNC/linuxcnc/blob/master...erp_convert.cc#L5052
edit at your own risk

Note this is where Gcode is converted to blocks that are stored in a circular buffer and subsequently executed by motion.

I'm a bit confused, Initiially an IP address was not set but in later ip a dumps it was correctly set for a Mesa board at 10.10.10.10, It was never made clear after that if the Mesa board was pingable. I assumed it was. 
I would like to see the Hal and ini files to confirm the MESA IP address.
Can you ping the card?

Also from photos of the board, it would be great if PCW could confirm that the links are set for the 10.10.10.10 address is set correctly. W2 down, W3 Up

Also, need to check out the 5 volt power supply to the board which is usually powered form field power which seems to be the case. But are the links set correctly to send 5 volts to the logic side? Can PCW confirm?

The final thing to check on physical wiring, What is the field power voltage? What is the actual power supply? What is the power supply current available? There have been numerous instances where borderline power supplies cause network failure with Mesa cards. This must be ruled out. If need be get a good industrial power supply such as Meanwell MDR-60-24.

It might be worth setting the IP address back to automatic (DHCP) and connecting the PC to your normal network using this NIC card to confirm networking is working.

I mentioned it before but be sure to set the IP address and coalescing as shown in man hm2_eth (use your IP address and 
linuxcnc.org/docs/stable/html/man/man9/h...h%20static%20address

So if all of that checks out and a new network cable does not fix things AND the network is connecting but drops out every 45 seconds or gets error finishing read., there will likely be one of several power saving settings kicking in periodically.





 

M2 and M30 commands have the following effects:

• Origin offsets are set to the default (like G54).

linuxcnc.org/docs/devel/html/gcode/m-code.html#mcode:m2-m30

In LCNC 2.7 it fortunately did not work.
In LCNC 2.9 it UNfortunately works.

My friends used LCNC 2.7.  They used G54 for vise number 1 G55 for vise number 2 and so on. They dont use G5X in ngc files. They have many many ngc files. They were happy.

They started use Mesa cards 7i96s so they had to upgrade to LCNC 2.9. But in LCNC 2.9 automatic Ǵ54 UNfortunately works again. It is very dangerous for them. They works on vise number 2 with active G55, but after program end G54 is activated.

I need help. Where is "automatic Ǵ54 after M2/M30" in source code? I want delete it for us using.

If you are not overloading the 5V supply on the 6I25
I really don't see how any wiring or data issues can
crash the host PC.

That is, this really has nothing to do with differential
encoders at all.

I'm beginning to wonder if this is not a parity error or similar
either in the host PC or PCIE interface

Did you say the you only got the error when you changed the MPG position?

Another thing to try:
-set the Mesa encoder inputs to "single ended" for that channel (see manual)
-Wire only +5V and GND-
-wire only A+ and B+ from MPG to Mesa A+ and B+
-test
-wire only A- and B- to Mesa A- and B-
-test
?

Do you have any normal encoder, or a servo motor with encoder attached to it?
If yes, wire it and test, see if the same thing happens.
Do you have the spec for the MPG?

So this is the current setup 
And I have this HP PC here I can use for testing. 

I had a few more minutes to work on it this week - I wired the encoder via a short pigtail to the 7i77, got the same results as before. So the issue cannot be a faulty wiring connection.
I also found that my 5vdc power supply may not have been grounded, so I fixed that, no change, the PC still crashes.
I also tried all the other encoder locations on the 7i77, all producing the same issue.

I will keep updating as I do more.

Nice work, excited to test it out!

I am reminded of Excessive Overkill's youtube channel (around 18:39):  

 

Yes, this does not seem to be a latency issue but a connection issue.
Not really sure what the cause is. I have a 800 G1 here running
LinuxCNC without any Ethernet connection issues so I don't know.

Is is possible to try another PC to try and isolate the issue?



 

Rod, no amount of tuning is gona help on a disconnected link.
-
Did you change the cable?
Do you have a USB-to-LAN adapter to test with?
Do you have another PC to test with, any PC with a different cable.
-But, only after the Mesa is connected and trying to run LinuxCNC.

There are a lot more tuning settings required but lets get the main one
Can you type: echo $(nproc)
and then back in grub customizer add isolcpus=X where X = $(nproc)-1 from what is printed from the line above.
Then reboot.