Advanced Search

BSOD wrote:

Please share your config, HAL and ini. (can't find them, if you did earlier.)

For the HAL and INI files, I’m using the default LinuxCNC/remora-rt1052-basic configuration. I haven’t made any changes or tweaks to it.

For the config file uploaded to the NVEM V5 board, I used LinuxCNC/nvem-rt1052.txt .

Let me know if you need any more details!
 

This seems to be somewhat tricky. It seems config.txt is created dynamically by the builder so there is nothing to edit.
I think it could be modified in a stage 3 script using sed which I know nothing about.
ref: github.com/rodw-au/rpi-img-builder-lcnc/...scripts/uscripts#L87

If you could write a bash script that makes the required changes to your pi, I'll see if I can incorporate it.
I had a look at the builder over Xmas and merged the latest upstream source which includes support for kernel 6.12.
I might try that... I think I got it to build without our customisations. It would be so much nicer if we could avoid patching the kernel.
I think there was a post that said the RT kernel needed some extra config settings set. If you know where that is, please share it.
I think we can just add them in kernel.txt
Ref: github.com/rodw-au/rpi-img-builder-lcnc/...cnc-2.9.3/kernel.txt

Ok, heißt im Klartext alles doppelte in der hanrad.hal rausschmeißen ?

      

do have work multihead cnc project ? @spumco !!

hi, I look at my bios that is so old and is not new firmware for update.
MY motherbord is pegatron ıpmıp 55 gen.Anyway, I can setup ubuntu on my pc, Previously, I used ubuntu on my pc.
Has ubuntu cnclinux program?

In the meantime, I found the information I was looking for here : wiki.linuxcnc.org/cgi-bin/wiki.pl?Spindleoverride

Please share your config, HAL and ini. (can't find them, if you did earlier.)

I finally got around to start putting wires on the MESA card. Now I came across some questions that may have simple answers.

1. Do I need to wire up the enable inputs on the stepper drivers?

• motors work fine without enable lines.
• driver reduces current to half when the motor is not moving; so no heat issue.
  
  Is there anything that I overlook that would make it adviseable to add this wiring?
  
  1.1. The 7i76 does not have an "enable Pin" on the step generator. So I then need to hook up enable to any normal I/O?
  
  2. I noticed that I can get a higher top speed when I reduce the accelleration and at lower top speed I can put in higher accelleraton values.
   For a small bench top mill should I rather focus on acceleration with lower top speed?
  
  3. Is it possible to generate a 4th axis in PNC config? I did not find it yet. Maybe someone can point me in the right direction. Do I have to add this manually to the HAL file?
  
  No idea why I could not make it work yesterday. Answers to 3. are: Yes it works with pncconf and NO manual adding it to hal from scratch is not required.  I just tried fresh again. Choose XYZA configuration and everything was fine.

It may help to mention that the 7c81, mesaflash & driver loading wise is the same. Apart from the difference in the name of the driver loaded the RPi4 is the same. You need to enable the SPI interface via config.txt

Hopefully you'll be able to put together a killer doc that people will read.

Good luck

This one is close to 30 years old, I wrote a win95 device driver in assembly many many moons ago, ones & zeros of different length. I also manged to squueze a basic master station into a 16f84 all done in assembly.
www.nmra.org/sites/default/files/standar...C/S/s-92-2004-07.pdf


www.testandmeasurementtips.com/morse-cod...munication-protocol/

Then there's "Manchester encoding" used by ethernet.

We can also encode 1 & 0 as a certain frequency or shifting the phase.

The PCIe bus transfers data serially, at far greater rates than the parallel ISA & PCI buses could.

PS/2 is another way of sending data serially.

SPI is somewhat different in that the transfer of data is controlled by a clock are controlled by a clock. Bits can be shifted in & out depending on the clock polarity, of course you wanna define this beforehand.

Human generated speech is serial in nature, supposedly Tibetan throat singers can generate more than one sound at a time. Then again sound is serial in nature, as is light.

Even the written word is serial in nature, unless of course you are some rare type that can ingest a whole page of words at once. I don't know if this is even possible.

Even the parallel port could be considered serial in nature, talking to printer requires sending the data at one byte at a time, even 32 bit transfers end up being broken into 8 bit chunks.

PAL, SECAM and NTSC sent data in a serial fashion.

This is kind of going off the rails now. I quite happy to not totally agree with you but also not think you are a fascist.

I'm using the latest nvem-rt1052 from the Remora-RT1052-cpp repo, but the issue persists. I don't think it's a config problem, as all pins are functioning properly except the output pins. It seems unlikely that this is a coincidence.

I'm starting to suspect either the HAL component or the firmware might not be working as expected with the NVEM V5 board.

Here’s a quick video demonstrating the issue:

Thank you so much for your time, really appreciate it!
 

This will because PATH.find_image_path() returned nothing.
Can you give any more information?

Cant do this anymore bye all wrote:

When setting the baud rate (divisor) on a 8250 or the later variants it will always be tied directly to the time allowed for each bit.
 

Lol yeah, that's how all asyncronous serial works. What do you think you are setting when you set "115200" on a COM port? Divide that baud rate into 1 and get the "time allowed for each bit". It's just easier to ask people to set the baud rate on the COM port than it is to say "gimme the period of time in us/ms". Anything that happens a specific number of times within a second is a period, you just forgot to do the division.

Yeah sure there are serial protocols the will define a zero has being so many us and one has being another value, which no one has yet to mention, but each period for either 1 or 0 will be an absolute value. 

Like what? What protocol is that? That would literally be something that has no predefined data rate because the rate you can transfer data specifically relies on the difference between how many 1s are in that package vs how many 0s are in that package.

Morse code is not a serial protocol, it's a method of spelling the alphabet by using human understandable events, like flashes of light or sound. There is no precise timing involved, just perception. You can't perceive the difference between 1us and 1ms and a machine would have a hard time trying to figure out what the hell some outrageously long and inconsistent "dot" is.
 

Cant do this anymore bye all wrote:

Easier than trying to edit a post.

My fork was way out of date to create a pull request and I've kind of forgotten the code structure of the Image generating program. So I started a new thread asking if the next round of images could have the spi interface enabled, I also mentioned that you were a very patient user that had been lead astray by the spidev10.0 being created with the SPI interface, I guess it would be a idea to refer to it as the SPI user usable interface.

I think it would be an idea just to keep it to that topic alone, rather than requesting other software packages and mind reading abilities to be added (rod has declined the mind reading abilities on previous occasions). Tho to be fair in would be quite unkind for the poor old Rpi to read my mind.....I barley know what direction it is going.

That sounds great, I am including this specific callout in the write-up that I am making (specifically for the 7c80, geared towards the Pi5). Since a start to finish guide doesn't exist in any single document.