there’s 3 problems we’re facing right now that might have simple solutions we can’t see:
1 - I Imaged our '10 classmate, installed the 3 update packs (LV, utility and diver station) and LabVIEW is not opening.
It’s curious, because the imaging tool is working normally, I just imaged our cRIO… and the driver station is working normally as well.
2 - I installed everything in my notebook, I even got the cRIO communicating with LabVIEW, but now my computer can’t see it anymore (I had it working for a few hours) no matter what I do. I checked the IPs, reimaged, checked battery, changed the cable… (I’m using a cross cable from cRIO’s port1 to my notebook’s ethernet port).
3 - Not to mention the cypress board, that is perfectly recognized by the classmate’s driver station, but the driver station in my notebook can’t see. The sad part is that the PSoC programmer sees and writes normally in it.
Summarizing: we got our KOP only yesterday and we are facing problems in very fundamental steps. We have stuff working part on a notebook, part on the classmate, but not everything in one place, and the way things are, we can’t go on, because there’s no way to send code to cRIO right now
how come? there’s a folder for it and everything… and I ran the imaging tool, supposedly it wouldn’t work without labview, would it?
there’s only 1GB left on our classmate, should I delete everything labview-related and reinstall the whole thing?
None of the programming software is installed. The only thing you get is the labview tools (cRIO imager and other things) and the runtime but not labview itself. The 1GB left is due to the recovery partition. Go Here for the updated procedure and files if you want more space on your classmate.