Advanced Search

Yes, RPi suggests that parallel processing 1.5x that number of cores works well. I had also always used the number of cores.

Peter,
Thank you. I can see the logic behind that, what I think was lost is the significance of the channel numbers and why I'd have to use the third channel for this card.
I think I see it like this. The sserial instruction is to the host card ie 0, (7i92, ) in my case. Plugged into which is a daughter, could be two of them, but only one (7i77) here, and that's therefore channel 1, and lastly, the smart serial card 7i73 that hangs off the 7i77must be channel 2

I get it in version 2.9.4.
everything worked during the day, broke in the evening.
how can I fix this?
where to find "sticky threads"

The sserial_port_0 parameter sets the modes for sserial channels 0.N in
left to right order of channels so sserial_port_0=001xxxxx means set

sserial channel 0 -> mode 0
sserial channel 1 -> mode 0
sserial channel 2 -> mode 1
sserial channels 3..7 = x = disabled

The channels used in a a particular FPGA configuration can
be determined with mesaflash's --readhmid command

At the beginning of this post there was a demonstration using only USB Networking (No Ethernet).
Does this function still exist?
I was able to build and install to an ESP32-WROOM, but boardconfig keeps setting to "Wowki Simulator ESP32".

rodw wrote:

prokopcio wrote:

I suggest 20-70kHz (0-10mm) and 10kHz(or 0Hz) = collision
This is linuxcnc. We will not have collisions!
Maybe  collisions are 5 kHz and our rule is: if < 10 kHz, report a collision

in fact, anything below 20 kHz is a collision.

higher frequencies mean faster response, which is very important for collisions.

hi blazini,
I also think that digital/serial transmission is a very good solution.

I have to think about it because the output that I have available in the sensor is an open drain output and it would require a simple converter but it is not a problem to add it. These are just a few basic elements to adapt to various interfaces such as RS485, RS422, RS232 or UART TTL.

I do not foresee standard protocols such as MODBUS etc. with bidirectional communication due to the too long time of exchanging transmission frames.

I do not want to use a high transmission speed so that the quality of the connectors and cables does not affect any possible distortions.
I want to transmit every 1ms only 4 bytes (start byte, 2 data bytes, crc) at a speed of 57600 but it is possible that I will change the assumptions.
Could you handle something like this?
If you have other ideas, they will be welcome