Advanced Search

Ah I see, I was some what interrupted by The Hound whilst reading and responding, my apologies sir.

As per instructions you either set the password or username prior to writing the imagery via RPi-imager or you set the user name and password via the first boot wizard, exactly the same process as you would go through with a stock raspios image.
The change in the way the image was built was to make it easier for a user to setup thier wifi and locale, and to allow the user to select a username and password to their liking.

Hi,

After a few years I pulled out my RPi4 and Mesa 7c81 from the drawer again. I tried to install raspi os 2.9.7... And that's it. After a while of inactivity my screen locked and I was done. I searched the "entire" web, but I couldn't find the password for that awesome username anywhere.

Entschuldige bitte das ich gefragt habe.
Nicht jeder ist ein Genius wie du...

Hello,
Not sure to understand correctly:
You can have both TIM2 and TIM5 32bits encoders running in the same time right?
But it has to be on a custom board

That was very close to what you describe, i had some Serial Absolute Encoders that would cause me much grief to replace mechanically, so it was magnificent that PCW made the firmware i could use with those encoders.
BTW, that machine is still in daily use, and never gets powered off.

I was think along the lines of "I would like the mesa firmware to support this piece of hardware I have" which may or may not have been retrieved from a Soviet UFO warehouse.

From the manual, it says that it handles the passthrough power via otherwise unused pins on the cable, so that seems like a fine solution to me. As they control both sides of the board, it's not like you need to worry about things going wrong in that sense (as long as you use the appropriate cable).  It's also nice to simplify the power wiring a little bit.  

I will definitely let you know if I find some other solution that seems more appropriate for whatever reason, but I figure designed and documented in the manual is probably good to go

I would like to apologise to the OP for my remarks to his original post.

I have been shown to be unkind and unhelpful. My fellow forum members have been very gracious.

unknown wrote:

Customised firmware, based on the available source, is no issue to have built. So far I haven't seen requests for new firmware features. Maybe this has happened I can't say for sure either way.

Does this qualify:
forum.linuxcnc.org/30-cnc-machines/31792...rofit?start=20#85721

I wouldn't call my solution a preferred one, it's just the implementation I chose.
Please ask questions and do some research, I'd hate for my way to be sub par and lead another member the wrong way. So far nothing has gone wrong.
If you do find any info to the contrary I would be most appreciative if any failings in my advice were pointed out.

Rob

They do seem somewhat robust, but there is always a chance. Not to sound like a doom goblin.
Whilst I have no empirical evidence, not having the resources nor $$$ to test, I feel (for lack of a better word) that Ethernet does provide some electrical isolation as opposed to direct GPIO connection.
Ethernet also frees you from being shackled to a single platform.

Tommy provides some very good information. Whilst to forum may appear to be a little biased based it would come down to a few points.
Tommy's mention of performance.
Reliability.
Wide range of options regarding hardware.
Many many more inputs than via GPIO.
The fantastic support from PCW, even when dealing with cloned items bought off AliExpress, or those building there own custom boards using dev boards and hashed together sundry parts.
Customised firmware, based on the available source, is no issue to have built. So far I haven't seen requests for new firmware features. Maybe this has happened I can't say for sure either way.
And finally, which I almost forgot, the knowledge of many of the forum members.

forum.linuxcnc.org/10-advanced-configura...ning-detailed-how-to

I didnt expect a hickup in the virtualbox can interfere functionality of linuxcnc. But after restart, i can not reproduce this problem in axis and flexgui. 
I have  version 2.7
Lucky its solved by itself. 


 

First time retrofit to linuxCNC, using pncconf to tune the PID loop.

Any advice would be great on initial pid settings.

glentek velocity/tach servo amplifiers SMA7215 
Single ended 1000ppr encoders

Critical response achieved on each servo amp, it is not overdamped yet when i adjust I/D/BIAS/DEADBAND it overdraws

Any advice for first time setup would be very much appreciated