niston Posted July 23, 2024 Posted July 23, 2024 Quote here are a lot of buttons. On the right under the nixie there are 3 buttons with indicators. 7 under the tray. + power will be at the bottom in a row with them. And there are 11 buttons. Some of them will be decorative if they are not needed. Yes, it's got plenty buttons. I think 2 may be left over, we'll see. Quote Maybe the power button down in one row with the other buttons (instead of the headphone jack)? Yup seems a good idea.
South8028 Posted July 24, 2024 Author Posted July 24, 2024 (edited) 16 hours ago, niston said: Yes, it's got plenty buttons. I think 2 may be left over, we'll see. Yup seems a good idea. Draw inscriptions, which buttons are where. Edited July 24, 2024 by South8028 1
niston Posted July 24, 2024 Posted July 24, 2024 For the remaining 2 buttons: CONFIGURE doesn't need the indicator. Apart from that, the buttons are perfect.
niston Posted July 24, 2024 Posted July 24, 2024 Even better idea: Instead of CUE, label that button RANDOM
South8028 Posted July 26, 2024 Author Posted July 26, 2024 (edited) On 7/24/2024 at 9:51 PM, niston said: Even better idea: Instead of CUE, label that button RANDOM Finished it. Now we need a list with sequences for buttons and indicators. The tray should accordingly have its own animation. It can come out of the body and retract back. That means 4 sequences. For example, the standard Off, TurningOn, On, TurnigOff. Indicator labels have their own animation system. This is one indicator with 7 uv frames. The same goes for the indicators above the buttons. They can each work individually, or be one model with 7 frames. As you wish. https://disk.yandex.ru/d/PxlqFey6hqptsw Edited August 20, 2024 by South8028 1
niston Posted February 2 Posted February 2 For Virtual Circuit Module SOUL Virtual Circuit State Table State Value Description VC_STATE_NC 0 No Virtual Circuit exists (not valid circuit data). VC_STATE_REQUESTING 1 Requesting a Virtual Circuit to be established. VC_STATE_ACCEPTING 2 Accepting a Virtual Circuit request. VC_STATE_ESTABLISHED 10 Virtual Circuit is successfully established. VC_STATE_TEARDOWN 13 Signaling removal of an established Virtual Circuit. VC_STATE_ACTIVE 21 The Virtual Circuit is powered, valid, and ready for use. VC_STATE_SELECTED 22 The Virtual Circuit is actively exchanging data (e.g., selected listening source). VC_STATE_ORPHANED 99 The Virtual Circuit has been inactive for a long time, but still exists until cleared. SOUL Virtual Circuit State Machine Current State Event Trigger Next State Description VC_STATE_NC (0) Device requests a VC (PKT_SOUL_VC_REQ) VC_STATE_REQUESTING (1) A device initiates a Virtual Circuit connection. VC_STATE_REQUESTING (1) Target device accepts (PKT_SOUL_VC_ACPT) VC_STATE_ACCEPTING (2) The receiving device acknowledges the request. VC_STATE_ACCEPTING (2) Requester confirms (PKT_SOUL_VC_ACK) VC_STATE_ESTABLISHED (10) The Virtual Circuit is now fully established. VC_STATE_ESTABLISHED (10) Both devices powered & responding VC_STATE_ACTIVE (21) The Virtual Circuit is powered and ready for use. VC_STATE_ACTIVE (21) Virtual Circuit is selected for transmission VC_STATE_SELECTED (22) The Virtual Circuit is actively exchanging data (e.g., selected listening source). VC_STATE_SELECTED (22) Device signals transition to idle (PKT_SOUL_VC_HOLD) VC_STATE_ACTIVE (21) The VC remains active but is no longer exchanging data. VC_STATE_ACTIVE (21) Device loses power / disconnects VC_STATE_ESTABLISHED (10) The connection remains established but inactive. VC_STATE_ESTABLISHED (10) Device missing for an extended period VC_STATE_ORPHANED (99) The Virtual Circuit exists, but the other device has been missing too long. VC_STATE_ORPHANED (99) Device returns to network VC_STATE_ESTABLISHED (10) The missing device is back; VC can be resumed. VC_STATE_SELECTED (22) A device requests teardown (PKT_SOUL_VC_TRD) VC_STATE_TEARDOWN (13) The Virtual Circuit is waiting for disconnect confirmation. VC_STATE_ACTIVE (21) A device requests teardown (PKT_SOUL_VC_TRD) VC_STATE_TEARDOWN (13) The Virtual Circuit is waiting for disconnect confirmation. VC_STATE_TEARDOWN (13) Teardown is acknowledged (PKT_SOUL_VC_BRK) VC_STATE_NC (0) The Virtual Circuit is completely removed. VC_STATE_TEARDOWN (13) No response received (timeout) VC_STATE_NC (0) The Virtual Circuit is forcefully removed. SOUL Virtual Circuit PACKET Struct PKT_SOUL_VC Int Operation ; Specifies the action (VCC_OP_*) String VCID ; Unique Virtual Circuit identifier Int PayloadType ; Type of payload (DATA, SYNC, etc.) Var Payload ; Actual payload (passed to receiver, not interpreted by VCM) Int ReasonCode ; Reason for teardown (only used for VCC_OP_TRD) Bool FlagACPT ; Acceptance flag (only used for VCC_OP_ACPT) Bool FlagACK ; Acknowledge flag (only used for VCC_OP_ACK) Bool FlagREQ ; Request flag (used in VCC_OP_BEAT to request a reply) ; Only used during connection establishment Int SourcePort ; (REQ, ACPT, ACK only) Int DestPort ; (REQ, ACPT, ACK only) EndStruct SOUL Virtual Circuit Control (VCC) Operations Operation Value Purpose Required Fields VCC_OP_REQ 1 Request establishment of a Virtual Circuit. VCID, SourcePort, DestPort VCC_OP_ACPT 2 Accept a Virtual Circuit request. VCID, SourcePort, DestPort, FlagACPT VCC_OP_ACK 3 Acknowledge Virtual Circuit request (accepted or rejected). VCID, FlagACK, ReasonCode (if rejected) VCC_OP_DATA 4 Transmit data over the Virtual Circuit. VCID, PayloadType, Payload VCC_OP_BEAT 5 Keep the Virtual Circuit alive (heartbeat check). VCID, FlagREQ (requests BEAT reply) VCC_OP_HOLD 6 Transition VC from SELECTED → ACTIVE (stopping data exchange but keeping VC established). VCID, ReasonCode VCC_OP_SELECT 7 Transition VC from ACTIVE to SELECTED -> (VC is actively exchanging data) VCID, ReasonCode VCC_OP_TRD 8 Request Virtual Circuit teardown (disconnect). VCID, ReasonCode VCC_OP_BRK 9 Acknowledge that a Virtual Circuit has been removed. VCID
Recommended Posts