HI all,
we have got an UNO in one of the labs here that we are trying to use to control a couple of solenoids to automate an analysis device. Now what I have done is programmed it so that when the board receives an 'a' it switches R1 on, 'b' switches R1 off, 'c' switches R2 on and 'd' switches it off again. I am using serial.read() to read in and compare the value to a char and then use the result in a conditional to determine the output.
Now it works fine in hyperterminal, but when we use the software that we need to drive it, it does nothing. The software we are needing to use is Isodat from Thermo scientific if that helps at all(which it may...). Basically you define a device using specified comm settings and tell it to transmit a value when a button is pressed and it should replicate typing the value in using hyperterminal... but it doesn't seem to.
What I have noticed, which is the guts of my question (finally!), is that when using hyper terminal, the 'l' led stays lit and the Rx flashes when I send a value to the board, but when connected via isodat and I transmit the value the 'l' led flashes and goes out for a second or two before re-illuminating (and the Rx flashes as well). it doesn't mater which value I send to it it does this, and it never does this when using hyperterminal regardless of which value i send to it...
It seems if the command from isodat is resetting the board somehow (i can't offer anymore info about what isodat sends it other than I think it is just a single byte value that I have specified: the documentation is somewhat lacking!) as also if say R1 or R2 is on, sending a value from isodat will cause the 'l' led behaviour noted above and also turn off the relays that are on, even if the command was to turn then on (in which case it should do nothing).
Can anyone help with some insight into what problem may cause the behaviour of the 'l' light mentioned above?
any help would greatly appreciated!