Current behavior
error.log
As attempting to incorporate the mettler toledo balance (similar model as A-Lab), I keep running into errors that prevent both connections and job submission. From GUI, the balance is always inactive; and when submitting a simple input script to open/close door and capture weight at stable mode, the error message as attachment shows up. Running a simple script without the AlabOS codebase yielded expected results so the web service shouldn't be the cause.
During this process, the task shows up on the experiments section in GUI while the "cancel experiment buttom" doesn't respond. RabbitMQ and mongoDB are verified to be active, and I'm running the codebase on a ubuntu virtual machine. I couldn't rule out the possibility of the internal network issues thus far. I'd appreciate any insights into this problem.
Expected Behavior
I'd expect to see the effective communication between AlabOS and hardware, or say balance shows up as an active device and AlabOS handles the instructions in job script as expected.
Minimal example
Relevant files/images/logs
No response
Current behavior
error.log
As attempting to incorporate the mettler toledo balance (similar model as A-Lab), I keep running into errors that prevent both connections and job submission. From GUI, the balance is always inactive; and when submitting a simple input script to open/close door and capture weight at stable mode, the error message as attachment shows up. Running a simple script without the AlabOS codebase yielded expected results so the web service shouldn't be the cause.
During this process, the task shows up on the experiments section in GUI while the "cancel experiment buttom" doesn't respond. RabbitMQ and mongoDB are verified to be active, and I'm running the codebase on a ubuntu virtual machine. I couldn't rule out the possibility of the internal network issues thus far. I'd appreciate any insights into this problem.
Expected Behavior
I'd expect to see the effective communication between AlabOS and hardware, or say balance shows up as an active device and AlabOS handles the instructions in job script as expected.
Minimal example
Relevant files/images/logs
No response