Advanced Search

It was related to the number of recipients per message, not total emails per day.
ie: no more than 5 recipients per message.

I was more concerned with why I was seeing it, since I'm just a pleb

I think Scotta did some work with the Pico. Might be worth a look.

github.com/scottalford75/Remora-RP2040-W5500

Fellow Aussie, there's a few of us around.

Shame you're low on space, I've got a running 7c81 clone here.
github.com/ozzyrob/Linuxcnc-FPGA

Anyways shoot us an email, that's on my github.

are you using this for C axis work or just threading ? if just threading, then, it's already handled in spindle mappings in the base config, you just need to make sure to connect it in the HAL file to the Z/index pin. If it's for C axis live tool type work, that's a bit outside of my experience as I haven't had time to finish my own work towards that myself.

WARNING:
- Do NOT go to Linux Mint forums to ask for help regarding this image, NEVER EVER!!!
=
- This is for anyone wanting to have a Working LinuxCNC installation in Minutes, has no support except here on this forum from me, uses development version so might have issues.
=
Removed Libreoffice, geoclue, redshift, flatpak, and some other useless stuff
Installed Inkscape, Blender, OBS-Studio, KdenLive, VLC, GIMP, Darktable, GNumeric
Enabled FIREWALL by default!!!
-
In Live mode when booted from USB it runs with Generic Kernel
After installation to hard drive it runs 6.10.nn RT-Preempt kernel
Warning: WiFi will probably not work with the RT kernel, so reboot and hold down right side SHIFT key, go to advanced options and choose the generic kernel, WiFi works fine with it.
-
drive.google.com/file/d/12adxkk6DU2fTYJb.../view?usp=drive_link
MD5SUM= 90d9e678a0ba1fe42b6bd7fab6ae8987 Linux_Mint_22.1_LinuxCNC_2.10.iso

Hey brains trust!

I'm currently restoring an old dental mill, converting it into a small envelope 5/6axis CNC machine for soft metals. Likely going to be put to work on making small plastic injection moulds and other little projects here and there. 

I initially started down the path of getting a Mesa card, but here in Aus the prices are insane - between the USD conversion rate and the freight I'm basically going to spend more on getting it here than I would on the board itself. I did the ring around some of their suppliers closer to home and while they were super helpful, they couldn't help me get around those two issues. Oh well, on to the next solution. 

I'm super impressed with the Remora firmware, noting Scott sounds like a fellow Aussie (G'day mate if you happen to read this!). I see that these can be flashed onto Mach cards like the EC300, EC500 and the NVEM. I had a bad experience trying to buy an NVEM from a local supplier, fortunately got my money back and now I'm back to square one with trying to get a controller. This part of the project has been the most difficult, beyond the steep learning curve of learning HAL!

My enclosure won't fit an EC500, I was going for an NVEM, but an EC300 could also fit the space I have left in my electrical cabinet. I have an STLink already that I bought years ago when I was flashing STM32 boards so I'm already pretty well across the process. I see Scott even has a few helpful videos too! I was hoping you guys might be able to guide me on a few things:

• EC300: I see on the supported hardware page that the EC300 is compatible, but I can't seem to locate any info on what's in them, are they also STM32? and can I flash them with my STLink? Assuming they also work with Remora. And if this works, are there particular versions of the board that I should look out for?
• NVEM: I notice a few threads hinting that the wiring is the same between the 4/5/6 axis boards of NVEM, but haven't found anything concrete. Is this true? In which case, the suppliers on Ali Express seem to charge an extra $20-$30 each axis I add. I'd love to just buy a 4 axis for cheaper and when I rip the Mach firmware off it in favour of Remora, I understand this will override the coding telling the device how many axes it has?  Does this differ between V2 through V5? 
• NVEM: I notice that the V5's seem to use something other the ST microcontrollers, in which case I'd probably need to re-tool which may not be ideal depending on how much their debugger/programmer units cost. I note that V2 has the STM32 chip in it, which other versions use STM chipsets?  
• In general, if I do have the choice between the two, what's better? I'm happy with stepper rates offered by NVEM, 200Khz is fine, my steppers cap at 500Khz so the Mesas would have been overkill. Both have the IO I need. 
• NVEM/EC300: It seems I need to buy from AliExpress if I want one in Aus, does anyone have experience with particular suppliers that aren't likely to rip me off or sell me the wrong thing? 
  
  Cheers guys, apologies if some of this has been covered, I did make quite the effort to read historical threads before posting, I did find clues but hoping to get some concrete confirmation. 
  
  EDITS: You'll see I've struck out a few items above. I found the video guide on Scott's channel converting an STLink to DAPLink which helps me get around the issue of ST vs NXP chipsets in either EC300 or NVEM units, no longer worried if I don't get an ST chip. Thought I'd document this here in case anyone else has the same question in future and may find this clue helpful. 

I solved the problem mentioned above. It was caused by connecting the tacho in reverse. The circuit diagram attached above seems to be correct. However, I gave up on applying it to my machine. The drive is too big and there is no space to install it.

My observation is the fastest ioc32 data rate led blicks(more speed)
the numbers of encoder read go more crazy.

try adding to the INI:
[DISPLAY]
GRAPHICAL_MAX_FILE_SIZE = 40

i have options to push the poll rate even further with PIO&DMA + using the W5100s interrupt pin.I won't be bored for a few days.

You can low pass filter the outputs
Also for noise and stability I would

1. Run the pots from the 7I73s 3.3V if you can
(Since this is the 7I73s analog input reference the reading
will be ratiometric, so a change in the 3.3V will not change the reading)

2. Low pass filter the inputs at the 7I73 (say with a 0.1 uF capacitor to 7I73 ground)

3. Low pass filter the analog hal signal (a 1 LSB  dither is expected with almost any
A-D at least at some (halfway between) input levels)

That does not set the rate though, what I did for testing was:

                if (inst->hal->rate > .001) {
                    timer = 1e9 / inst->hal->rate;
                }  else {
                    timer = 1e9 / 1000;  # 1 ms
                }      
 
 

Those *.tmax times are in CPU clock cycles and probably OK
if the CPU is ~3 GHz

First thing, get some thermal paste to put on that processor, and the one before it, both are getting very hot doing not much, some Intel processors will start throttling at 63C, some a bit later, but nearly 70 you are getting seems to high with such medium load.

try this to mesa_modbus.c.tmpl i think works?