A question to seniors ,I am a first year student entering in ICE department.
I am very passionate to embedded systems and eager in building projects and learning or interested in research papers
Will the professors supportive or the eco system will be good to encourage research paper or building projects in the first year ?
Do the parents should compulsory attend the programme ?
In my case it is difficult for both of my parents ?
And on that day I will arrive college at early morning itself when does the College hostel will open to check in myself ?
I have doubt on going to home on government leave of two or three days or on the weekends.
Should we need to inform to the hostel management or warden with a letter or mail ?
Or the first year is restricted on those leaves.
Asking seniors how many days leave for the first sem and second semester.
How much leave they have given for diwali as this year it is on Sunday.
In the psg tech hostel what about washing the clothes,
Does there is seperate place for washing the clothes or in the common bathroom itself we need to wash ?
Does there is laundry facilities ?
How they charge for it ?what based charging?
And current cost for it.
And what about room cleaning does we need to take care of it ?
I am a first year student joing I&CE ...
MY doubt is the hostel and college is safe from theft of valuable things like laptops and phones .
How to protect it any tips and tricks
Seeking from seniors
I’ve been working on the networking layer for a larger robotics/programming ecosystem, and I realized how incredibly frustrating standard MCU-to-MCU communication is.
The Problem I have faced in my projects.....
Whenever I need to bridge two microcontrollers (like an ESP32 and a bare-metal STM32) over UART, SPI, or I2C, we usually fall into one of two traps:
The Parser Trap (JSON/ASCII):
We send data as strings. This means writing custom parsers for every single project, calling malloc(), and risking heap fragmentation or stack overflows on memory-constrained chips.
The Polling Trap (Modbus RTU):
We use industrial standards like Modbus. But Modbus is a strict Master/Slave architecture. The master has to constantly waste bus bandwidth and CPU cycles polling the slave just to ask, "Did anything change?"
The Solution:
So I started the building of a protocol
I wanted a protocol that was event-driven, required zero dynamic memory, and didn't force me to write a string parser ever again.
How the Mechanism Works
Instead of serializing strings, it uses a Shared Object Dictionary that maps directly to physical RAM. Here is the flow:
Registration:
You take a local variable in your C code (e.g., float motor_speed = 0.0;) and bind it to a unique 8-bit ID in the struct.
Transmission:
When the value changes, it takes the raw bytes of that float, wraps them in a byte-stuffed frame (with SYNC bytes, Command, ID, Length, and a CRC-16 checksum), and fires it across the bus.
Reception (The Magic):
When the target MCU receives the packet, it doesn't parse text. The state machine deframes the packet on-the-fly. If the CRC passes, it looks up the ID, briefly triggers a hardware lock (to disable interrupts), uses memcpy to paste the raw bytes directly into the local variable's RAM address, and releases the lock.
I would love to hear your thoughts, feedback, or any architectural feedback you have.
Has anyone else built something similar to avoid the JSON/Modbus trap?