Advanced Search

There is another version of the electronics stuff that also does boards and routing, but still in infancy, getting interesting for sure.
Damn it, i wasted countless days doing electronics when i was young, had to wait till summer to go to Croatia to buy parts and books and magazines, yet it never stopped me from doing ... everything. Youth today can not figure out how to open a barn door!
But can easily figure out how to press 20-30 times on random stuff on the phone to start a useless game!

Within the space of 10 days, there is an embryonic clone of Fusion bubbling away. No CAM yet - but give it time (another week??!).



What is staggering is how rapidly this stuff is coming out - and almost from nowhere.

And on a slightly different note, if you do your own circuit and PCB design, there are some pretty interesting tools coming along, also free to use:



Give these tools another year or two and they will become much more robust and dependable. Exciting times!

Hermle_Gerald wrote:

Die Ansteuerung +/- 10 scheint bei Linux nicht sehr verbreitet zu sein. Was spricht eigentlich dagegen? 

Das funkt wunderbar mit LinuxCNC, wir haben mehrere 15 ton machinen die +/- 10V nutzen.
Mixt niht diese sache, +/-10V funkt nicht nur mit dem DM servo treiber/motoren, ales anderes ist in ordnung.

Hi tuxcnc,You are absolutely right that the simulator cannot know which physical tool has been installed if that information is never provided.I think I didn't explain one important part of our concept clearly enough.The simulator is not intended to receive all its information exclusively from LinuxCNC. It should eventually have its own virtual machine operator interface.Think of a real CNC machine with a manual tool change.LinuxCNC requests T5, moves to the tool change position, and waits for the operator. But LinuxCNC cannot physically verify which tool the operator puts into the spindle.Our simulator should behave similarly.The user would be able to select and install a physical tool through the simulator interface. That tool could be T5, but it could also be T3 by mistake.The simulator would then use the actual geometry of the installed virtual tool, independently of the tool information stored in LinuxCNC.The same principle applies to workpiece positioning, tool lengths, and eventually fixtures and collisions.Of course, this requires a virtual tool library and an operator interface, neither of which is implemented yet.Your example of the M6 REMAP moving to a toolsetter is particularly interesting. The simulator already receives the axis movements through Stepper-Ninja, so those movements do not need any special G-code handling.Once we have physical tool geometry and a virtual toolsetter, we could also simulate the actual contact with the sensor and return its signal to LinuxCNC.I agree that additional communication might be useful for automatic tool changes and other machine functions. However, I would prefer to keep the original Stepper-Ninja protocol unchanged if possible, and investigate a separate interface for simulator-specific interactions.The main idea is to simulate the physical machine independently of the controller's assumptions, including situations where the operator makes a mistake.Thank you for challenging this concept. These discussions are very helpful for defining the architecture before implementing the next features.

Ich benötige 7 Ausgänge, 18 Eingänge, 3 Poti Anschlüsse. Wegen Reserve hätte ich noch gerne etwas mehr. 
Wenn die Maschine etwas bearbeitet. Muss das 100% passen. Einen Schrittverlust kann ich mir nicht erlauben. Das Ziel ist Oldtimer Motorblöcke nacharbeiten. Die Genauigkeit hat oberste Priorität. Geschwindigkeit ist mir nicht so wichtig. 
Daher möchte ich Close Loop. Die Ansteuerung +/- 10 scheint bei Linux nicht sehr verbreitet zu sein. Was spricht eigentlich dagegen? 

Hi Peter,

thank you very much for the bitfile - and for the incredibly fast support, that was a really nice surprise!

7i96sd_pktv3x5 is flashed (user area, verify OK) and readhmid matches your pin file.
I ran a short bench test of everything in halrun (LinuxCNC 2.9.10, 1 ms servo thread, nothing connected to P1 yet), and all of it works:

- all modules show up in HAL: 6 stepgens, 2 encoders, pktuart.0 to .4, InM, SSR, OutM, PWM
- stepgen.05 on P1: 2010 counts in 2 s at 1000 steps/s
- GPIO IO36/40/41/42: output low/high with read-back OK, pull-up high as input
- with config="num_stepgens=5 num_encoders=1", IO34/35 and IO37-39 become normal GPIO
  (output/read-back OK), so the optional functions can be switched off without a new bitfile
- hm2_modbus with 5 instances at the same time (pktuart.0 to .4): instance 0 (one A6 drive on TB2)
  stays error-free, instances 1-4 just report timeouts as expected since nothing is connected there
- max. times: read ~200-220 us, write ~50 us, servo thread ~260 us with 1 instance and ~285 us with
  5 instances; no watchdog bite

My plan for testing the multiple Modbus instances with real hardware:

1. Breadboard 3.3 V RS-485 transceivers with automatic direction control on P1 for pktuart.1, .2 and .4 - one A6 drive on each port (the real P1 interface board comes later).
2. Run all hm2_modbus instances in parallel at 1 ms servo period, each polling a single register as fast as possible plus a larger diagnostic block once per second.
3. Long run (several hours, LinuxCNC + AXIS running) while logging error counters, cycle time per port and hm2 read/thread times.
4. Check that there is no echo with the auto-direction transceivers (RX masking), unplug/replug and power-cycle a drive to see how each instance recovers, and check the behaviour after a watchdog bite.

If you would approach this differently, or if there is something specific I should watch for with several PktUARTs/hm2_modbus instances, I'd be very grateful for any tips. I'll report the results here.

Thanks again 
Thorsten

 

1. Fits easily

2. Yes, RX is masked during TX (if enabled by the driver and pretty sure hm2-modbus does this)

3.  Not sure, if hm2_modbus knows how to do full duplex, but yes at the PktUART level, you would just assert
TXEN permanently

4. We should have more 7I87s in 2 weeks


Note that normally only one PktUART is used (since you can have multiple MODBUS devices on one RS-485 bus)
so you may well uncover some bugs...

 

I did soma latency testing and tuning. What helped most was to turn off hypertheading which reducedjitter from 30 to around 22 microseconds. Other bios settings like HPET off, EPU power saving, and cpu turbo on or off in my case made little to no difference. So did isolcpus, irqaffinity, nohz_full, and rcu_nocbs. rcu_nocb_pull yielded one microsecond less, so did setting sched_rt_rumtime_us to -1.

Please note RedHat warns to do this;

Issue

Is it safe to set /proc/sys/kernel/sched_rt_runtime_us to -1?

Resolution

In short, setting sched_rt_runtime_us to -1 can be extremely dangerous. A value of -1 means no limit. In other words, a "run-away" real-time task will be permitted to monopolise a CPU which could (potentially) lock up a system. The default value for sched_rt_runtime_us is 950000 or 0.95 seconds. Broadly speaking, this allows 0.05 seconds to be used by other non-real-time tasks (i.e. SCHED_OTHER) - a small window at which to recover a system.

The kernel parameter namely /proc/sys/kernel/sched_rt_runtime_us can be set between -1 and (INT_MAX - 1).

I left it at -1 anyway. In the end I was able to reduce jitter from sightly above 30 microseconds to just below 20. All test were done with one instance of glxgears running.

The cs-d508 driver reports by led signal when no motor or just one coil is connected. When good, all coils of both motors have a resistance of 2 ohms , they should have 1,8 according to the data sheet. Inductance is perfectly 5 mH. Damaged coils in my case still show a resistance of one Ohm. Maybe this is just enough for the driver not to notice any problem like a short circuit or similar.. I had motors in the past seeing similar temperatures that did not fail that quickly.

Pin-Belegung am Steueranschluss (CN1)

Die Step/Dir-Signale werden über den I/O-Signalport CN1 eingespeist. Die relevanten Pins teilen sich wie folgt auf:
• 5V Signalebene (z.B. für Mikrocontroller / Differenzialsignale):
• Pin 43 (PULS+) / Pin 41 (PULS-) für den Schrittpuls.
• Pin 36 (SIGN+) / Pin 37 (SIGN-) für das Richtungssignal.
• 24V Signalebene (z.B. für SPS-Steuerungen / Open Collector):
• Pin 39 (24V PULS+).
• Pin 35 (24V SIGN+).
• High-Speed-Eingänge:
• Pins 38 / 29 (HPUL+ / HPUL-) und Pins 46 / 40 (HSIGN+ / HSIGN-)

Das wärwn die STP ind dir Pins - ich habe selber ein Projekt mit einer 7i97 am laufen und würde dir dennoch zu der von mir empholenen raten das sStem kannst du später immer noch mit einer 7i77 ipgraden wenn du closedloop in linuxcnc umsetzen möchtest oder deine gms auslesen

Wieviele einausgänge brauchst denn an der Maschine? 
 

Ich habe jetzt noch einen Plan B. Wobei mir dieser besser gefällt.
Ist das richtig das +/-10 V Ansteuerung besser ist als Step/Dir?
Die Servos haben einen +/-10 Eingang. Die Ki sagt das der Anschluss V_REF+ und T_REF heißt. Diesen habe ich gefunden.

Der Mesa Jungel ist für mich noch etwas verwirrend. 
Mit der 7i97T würde ich 6x +/-10V inkl Encoder oder TTL 5V Anschlüsse haben. Das würde auch für eine Erweiterung auf 4 Achsen reichen. 
Kann ich bei der 7i97T drei Poti Anschließen?
Falls die Analogen Ein/Ausgänge nicht reichen könnte ich noch eine 7i84u oder 7i84D erweitern. 

oder ein 7i77U + 796S 

Gruß Gerald


 

Hi Peter,

I am building a small 3.5-axis mill/drill with a 7i96S and five STEPPERONLINE A6-RS servo drives (step/dir + Modbus RTU). Current setup: LinuxCNC 2.9.10 uspace on Debian 13 (PREEMPT_RT), 7i96s_pktv3.bin flashed. hm2_modbus to one A6 on TB2 works without errors (115200 8N1, rxdelay 40 / txdelay 45 / icdelay 20, about 7 ms per single-register read at 1 ms servo period).

I would like to ask for a custom bitfile with the following configuration.

TB2 and all on-board I/O: identical to 7i96s_pktv3
- StepGen 0-4 (X, Y, Z, W, spindle), QCount 0 with index (spindle), PktUART V3 on TB2 with internal TXEn, SSR, OutM, InM, PWM unchanged.

P1 (W6 set to GND, a small interface board sits directly at the header):


Notes:
- All PktUARTs V3. No TX enable pins on P1: the three Modbus ports use RS-485 transceivers with automatic direction control (e.g. MAX13487E); the lever link (PktUART 3) is full-duplex RS-422 with the driver permanently enabled, 2-5 Mbit, one packet per servo period in each direction.
- Instance numbering as in the table, please: PktUART 0 stays on TB2 (so existing configs keep working), StepGen 5 and QCount 1 are the highest instances, so I can turn them into GPIO with num_stepgens=5 / num_encoders=1 when they are not needed.
- If it does not all fit into the T20, please drop in this order: QCount 1 first, then PktUART 4, then StepGen 5. PktUARTs 1-3 are the ones I really need.

Questions:
1. Does this fit (5 PktUART V3 in total, 6 StepGens, 2 QCounts)?
2. hm2_modbus without a TX enable pin: is the receiver masked while we transmit (RXMASK driven by the internal drive enable), or should the transceiver's receiver be disabled during TX to avoid the echo?
3. Lever link: for full-duplex use I plan to set the drive enable bit statically and the auto bit off in my own HAL component. Is that the right way with PktUART V3, or would you configure it differently?
4. Is the 7I87 expected to be available again?

If it is easier for you, I can also build it myself with Efinity from the 7i96s sources - in that case a hint which PIN file to start from (PIN_7I96SD_PKTV3?) would be much appreciated.

Thank you very much for your support,
Thorsten

Same here. When I was new on Github I thought I could fork a project to my account to archive it. Nope one day I came back and discovered my unchanged fork had vanished along with the original author's interesting project.

Now it is:
cd into my NAS
git clone

I got interested in them as they are an easier option for straight forward machining rather than having to go onto my other pc in my office as i dont connect machines to my network and having to create toolpaths then load them in and if i want a change to go through a mess of work scripts i discovered are great within minutes toolpath made and loaded .

I managed to fix the issue. The diagnostics software kept reporting the AF_610 and also AF_620 faults (encoder related faults), but the reason was it could not communicate with the encoder due to a bunch of random parameters set during the failed write/download from the diagnostics software. 

However these parameters are locked out to users. However you can activate a "super user" level with code "jmc2018". This will allow you to alter the necessary P00 parameters.