Advanced Search

Thanks for your reply!
The solution seems promising. I went through the code and I see how you control the axes using jog-counts like with MPG. The only doubt I have is that whether these jog-counts will respect the coordinated motion of XY axes. Say if I change both counts at the same time in my component, will it result in synchronous movement of X and Y and will it do proper velocity & acceleration/deceleration, or will it be just a linear motion with constant velocity? Please let me know if you have any idea. Thanks!

Keep up the good work guys!
There might be obstacles but there is light at the end of the tunnel!

I just managed to reverse the 2 stlink keys but it does not appear as maintenance?

youtube.com/shorts/SjhZnoY1864

 

i use nomachine and it works great

delete all the stuff in your downloads folder via gui,
redownload nomachine
then open your file browser to the downloads folder or wherever no machine was downloaded
click the "open terminal here"

then type "sudo dpkg -i no"

after typing "no" hit the tab button and that will autofill the rest. This only works if their isnt another file in the same folder that starts with no. hence why you delete everything in the downloads folder

Lenovo T420 will not work for machine control at all dues to very bad power saving options built in.
The latency was terrible on mine, did you check yours?

Top! If you need any vector or image I can draw it for you

The cia402 component generates the necessary signalling with the drive's controlword pin.
It has the logic to do state changes and other things required by cia402. Therefore, we don't bother about that, it is all handled by the cia402 component. We just use the cia402 component.

If you want to go your own way, and do the signalling yourself to the drive you write to the drive's controlword lcec.0.0.controlword.
But that is just unnecessary, use the cia402 component instead, connect it as in the example.
You can check the source code for the cia402, it is where the example is.
 

still work in progress, but taking shape!


 

Okay understood. So you imagine something  like SCK ringing in the 20cm cable triggering your SPI logic twice? Fair enough, I'll try adding a .1n or so cap to the SCK line then, maybe that will help.

And .. yes .. as feedback on your(?) product I think it would be nice if there would be an option to have slower SPI with sampling. I have a 7i96 in use since quite a while on a 3-axis router and am quite happy with it, it works well. However, having to use USB ethernet on the other Pi I am using for that (for regular networking) is a bit of an annoyance / issue. This is why I went with the 7C80 now.

Hallo
Langsam komme auch ich zu einen Ende. Habe die Frässpindel Montiert aber den Umrichter ( A2 Serie) noch nicht eingebaut. Probelauf mit den Panel gemacht und sie läuft.
So hier die Frage: habe das Video von Talla angeschaut und will das gleiche nachmachen. Was muss in der HAL Ini alles eigestellt werden damit das vom Bildschirm aus gesteuert wird? Er hat die 5V genommen, anscheinent sind für die 7i96s die 12V zu hoch. Inverter hat einen 5V Ausgang.
Danke schon mal für die Hilfe.
Gruß Hans

Unfortunately, lowering the clock rate does not improve SI issues with the SPI clock itself.
The firmware uses an actual clock pin rather than an oversampled input so any ringing
will be an issue. Its possible to make firmware suited to longer cables but at the expense of
SPI clock rate.

 

Hey PCW,

thanks for the quick reply. Ok, I'll plan on a shorter cable.

However, just to test things out, wouldn't slowing SPI (and if necessary by a lot) help with any ringing and similar transient issues? Or am I missing something? I can only imagine strong crosstalk that would actually causes glitches between SCK and MOSI/MISO to be an issue at slow speeds - and that is surely not expected @ 20cm as it would still be way too short for that?

If you agree, would reducing the rate as I did in spi_boards.c (max in spi_boards_init) work or are there other things that would prevent such an approach?

What does

ip a

report?

I have seen a similar issue when the network GUI used was wicd
which breaks Ethernet connections when setting up a WLAN
(network manager works, wicd is broken or was broken)

All zeros data is possibly a connection or firmware issue.

I would try a short cable though

Note that a 20 CM cable is very likely to be unreliable due to signal
integrity issues (both ringing and ground bumping) The 7C80
and 7C81 are designed for the RPI to mount on top of the card with a
~40 mm cable

Works for me
www.youtube.com/shorts/ZcQjW4829R0

the modbus has some delay, thats why it is a little asynchronous


@Andrew
there is also a template now for your board, but without input yet, would be nice if you can give me your config for the inputs