Major MechComp powernet networking component doesnt want to work right with the nuke

[drWoof]

See title.
I've honestly tried everything.
I connect with the MechNet (mechcomp powernetworking component as said when using term_ping) to the nuke (using term_connect) and ensure that I actually connected.
I send the correct packet (

Code:

address_1=02022e93; data=(command=settime&time=31); command=term_message; sender=02022958;

).
I check the packet sniffer ( comes out as

Code:

address_1=02022e93; data=command=settime&time=31; command=term_message; sender=02022958;

) and it is COMPLETELY IDENTICAL to the packet that is sent when you connecting with a DWAINE terminal to the nuke (

Code:

address_1=02022e93; data=command=settime&time=31; command=term_message; sender=0200e1a4;

) which DOES work and SETS THE TIME and GETS A REPLY while the packet i send from the MechNet DOESNT set the time and DOESNT get a reply.
Same applies to trying to activate the nuke. The address_1 and sender are absolutely correct, I used a term_connect command with the same sender and address and it DID connect. I tried sending a packet like

Code:

address_1=02022e93&data=command=act&auth=%some master pass%&command=term_message&sender=02022958

, but it (at least) replied and gave me the bad auth error, even though the master pass WAS correct. The packet came out as

Code:

address_1=02022e93; data=command=act; auth=%maste pass%; command=term_message; sender=02022958