Hey Spicer, thanx for the update. I have some questions/observations to make.
The idea of building a robot as a system with frame points has merit. The attribute distribution is what I'm very very concerned about. The skills and perks/flaws are easily balanced but I find the whole Dataware idea of attribute distribution flawed. Let me elaborate. I see no reason to have a fixed INT for a certain PL and type of proccessor, rather a range should be available. This would be easier to incorporate into the 60pt system non-robots use. The ranges themselves are also very dubious. Dataware's limits on con/str/dex (physical stats) is bizzare, there is no reason a PL5 droid with hydraulics wouldn't have 20 str or 20 con (especially if it's a 4m tall and long monster).
IMHO this - the ranges - is the point where most problems exist. Also, since robots can come with default armors on them, perhaps it is these armors that should help define constitution and other physical stats? If it's a heavy neuronite armor, then perhaps it should yield +2 con / -2 dex no matter which actuators droid uses?
Will the default power supply be compatible with warships system? This is a very interesting idea (IMHO). For exapmle, let's say a robot's mass reactor gives 2-3 warships PPs, and is actually usable as an emergency supply for a small ship. Then other systems on the robot would actually use miliPPs.
In one session a robot character I played actually helped save the ship while there was a power surge while in drivespace by literraly plugging it's mass reactor into the stardrive power supply.
The skill system you described is, as I understand, inherently different than non-robots. You'd basically redefine skill sets. Why? Why not, as you're saying you'd use firmware sets, allow robots of PL 7 and 8 to use standard proffesions as their firmware? A battle droid can certainly be seen as Combat Spec, and a PL8 C-3P0 alternative (Jeeves droid as a Dataware example) is definetly a diplomat. Why make things complex when they can be streamlined into the existing system? Or alternatively, use the skill set Dataware stated for AIs, which also does make sense - the INT skills are cheaper whle PER ones go exponentially up in cost.
What about onboard weapon systems? Dataware had absolutely no mention of them, except saying that a gun to be installed inside a droid would cost 50-100% more due to extra chips and actuators. I imagine now it's use actual frame points. Perhaps some cyberware ideas would be viable to solve this - I'm speaking of the endoskeleton and it's restrictions on maximum weapon mass. Just an idea here also, I assume if the guns would be integrated, they'd also need magazine space, wouldn't be dependant on existing clip sizes etc. This all should be addressed.
More brainstorming - dual processors - dual memory space, triple the power requirements. Integrated shields/screens.
Most importantly, what I despized about Dataware, is that you could make a 30cm droid with hydraulics and heavy neutronite armor. This droid would have STR 18 and could lift half a ton. Duh. Ok, it's quasi-viable, but there should definetly be scaling in armor protection in these kind of cases, and also scaling of physical stats (ranges) depending on chasis size!
Well, that's all for now, hope you'll paste something soon!