Your main problem is what viewport the bones wer made in and how they’re parented. If you have an object in 3dsmax with no parent at all, it’s parented to the 3dsmax world instead. It’s pretty much the same as having it parented to an object with a scale of 100,100,100 a position of 0,0,0 and a rotation of 0,0,0. The problem comes in when you have an object that doesn’t have these nice clean rotations and scales.
The way 3dsmax stores the position, rotation and scale of an object is as an offset of it’s parent. For example, if you have a null that’s at 0,0,0 position and a child object that’s at 50,0,0, 3dsmax sees the child object as being 50 units away from the parent in x, 0 units in y and 0 units in z. If the parent object was at 100,0,0 and the child was still at 50,0,0, 3dsmax would see the child object as being at -50,0,0. Okay if you look at the object using world coordiates or local coordinates it’ll show it 50,0,0 in world and stil 0,0,0 in local but if you set any keyframes for the object you’ll see the position recorded as -50,0,0 in the trackview. Max is recording everything relative to the parent of the object. The coordinates of the child object are being added or subtracted from its parent.
Your issue is with your rotations. What’s happening is that when you start to parent different bones for your arm, when you take the first bone in your robot arm and make it the child of a null for example, it’s taking the rotation of the null and then figuring out what the new rotation value for the first bone now is. Your first arm might have had a nice clean rotation value of 0,0,0 but once you parent it on to the null object, if the null has anything otehr than 0,0,0 for its rotation, your arm bone will have its rotation value changed to something different. The default rotation controller in 3dsmax has flipping issues mainly due to it having to solve the x axis, then the y axis, then the z axis and there’s plenty of cases where once it’s done the x and y axis, the x might be pointing in the same direction as the z. Max freaks out and everything flips all over the place. One solution is to use quaternion rotations which fixes the flipping issues but it won’t give you function curves which is a pain to animate. The other option is to be really careful when you’re parenting your first bone to make sure that the object it’s parented to has a rotation of 0,0,0 - this way it won’t pass on any nasty rotations to your bones right at the start and max will have an easier time trying to solve its rotation. Thankfully for this you can just use a simple null so it won’t affect the look of your object, it just gives a much cleaner rotation to work with.
Last thing that you can do is when you’ve got everything parented, select all of the objects in your hierarchy, hold down alt and right click - you’ll get an optino in the top left called freeze rotation and if you choose this, it’ll reset all of the rotations of the objects to 0,0,0 and hide all of the horrible offsets so that you get fewer flipping problems.
bit of a long winded explanation but hopefully this helps!