Hardware Layer Specification / Recommendations

[jackorton32 (Jack)]

Hi,

I am in the early stages of developing what I aim to be an ecosystem of devices operating on cyphal. Currently, I am designing a set of micro controllers with onboard FDCAN tranceivers, can bus voltage support etc.

I am aware of DroneCAN’s basic hardware specification / recommendations (ie Bus power levels, device current supply/draw, connectors line with CiA spec, etc), and I was wandering if there are any current plans for OpenCyphal to release a set of physical layer recomendations for each of the supported transports that I should aim to align with, or is this going to remain unspecified and down to the developers to choose what best suits?

Currently I am working to approximately the DroneCan / CiA spec in an assumption that Cyphal wont differ very far.

Cheers

[pavel.kirienko]

Please refer here for Cyphal/CAN:

Cyphal/CAN Physical Layer Specification v1.0

Today we release Cyphal/CAN Physical Layer Specification v1.0 named UCANPHY (the U is for historical reasons). The UCANPHY Specification replaces the now-defunct physical layer section of the core Cyphal Specification. UCANPHY_Specification.pdf (2.6 MB) The UCANPHY standard is open to everyone, and it will always remain this way. No authorization or approval of any kind is necessary for its implementation, distribution, or use. Discussions that shaped this standard are accessible exclusively …

For the other transports, there are currently no such recommendations, but it is desirable to commence some work towards that.

[jackorton32 (Jack)]

Ah perfect, thank you. I missed this when searching