You are not logged in.
I've been working with the muChameleon board communicating through the muC Control software that was sent with the board .... and I am having problems with the command set and in general getting the PWM and Digital settings to work (I have been able to read through the ADC channels). I have found that there seem to be commands not documented in the manual (in particular pin n set and pin n clear which seem to mean pin n 1 and pin n 0 values ... not a big problem). But I've put a voltmeter on the pins, and the change in logic level does not produce a change in voltage output (pullup or not).
On the control screen (screen shot attached) the list of pin states does not get updated by the pin n 1 or 0 settings (even though the pin n state setting shows that the state has been changed from high to low, etc.) and changing the red and green buttons on the monitoring display does nothing ... I get no changes in the outputs from pins 9 to 12. Similarly, the PWM commands respond that they are working, but there is no change in the voltages or output at the pins.
I suspect that the higher pins may not be working ... can you give me any insight into where I might look next? If the board is defective, could I get a replacement?
Thanks
Chris Westland
________________________________________________________________
Command stream associated with the attached screen shot
received : id µChameleon
received : reset
>pin 9 high
>pin 9 high
>pin 9 high
>pin 9 high
>pin 9 high
>pin 9 low
>pin 9 low
>pin 9 low
>pin 9 low
>pin 4 high
>pin 4 low
>pin 1 state
received : pin 1 1
>pin 1 low
pin 1 clear
pin 1 output
pin 1 set
pin 1 input
pin 1 set
pin 1 output
pin 1 clear
pin 1 set
pin 1 clear
pin 1 set
pin 1 clear
pin 1 set
pin 1 clear
pin 9 clear
pin 9 output
pin 9 set
pin 9 clear
pin 9 set
pin 9 clear
pin 9 set
pin 9 clear
pin 9 set
pin 9 clear
pin 9 set
>pin 9 monitor on
received : pin 9 1
>pin 9 high
>pin 9 low
received : pin 9 0
byte : 10
>pin 9 state
received : pin 9 0
byte : 10
>pin 9 high
received : pin 9 1
byte : 10
>pin 9 state
received : pin 9 1
>pin 9 state
received : pin 9 1
>pin 9 set
>pin 1 set
pin 1 set
pin 1 clear
pin 1 set
pin 1 clear
pin 1 set
>pin 9 state
received : pin 9 1
>pin 9 high
>pin 9 high
>pin 9 high
>pin 9 high
>pin 9 low
received : pin 9 0
>pin 9 high
received : pin 9 1
>pin 6 hith
>pin 6 high
>pin 6 set
>pin 2 set
pin 2 clear
pin 2 output
pin 2 input
pin 2 clear
pin 2 output
>pin 2 high
>pin 2 high
>pin 2 high
>pin 2 high
>pin 2 high
>pin 2 state
received : pin 2 1
byte : 10
received : id µChameleon
pin 2 set
>pin 2 state
received : pin 2 1
pin 2 clear
>pin 2 state
received : pin 2 0
pin 2 set
pin 2 clear
pin 2 set
pin 2 clear
>pin 2 set
>pin 2 state
received : pin 2 1
>pin 2 clear
>pin 2 state
received : pin 2 0
>pin 9 set
>pin 9 clear
received : pin 9 0
>pin 9 high
received : pin 9 1
byte : 10
>pin 9 low
received : pin 9 0
Offline
Chris,
I can tell you that both my µChameleon devices, one currently at com3, the other at com4, respond correctly, when I send:
pin 9 out
followed by:
pin 9 1 OR
pin 9 hi OR
pin 9 set
5 volts appears at pin 9 for any of the above
AND that for:
pin 9 0 OR
pin 9 lo OR
pin 9 clear
0 volts appears at pin 9
hint:
For the above experiment, I used Hyperterminal.
I didn't use the app included w/ µChameleon for more than about two minutes before deciding to write my own or to use Hyperterminal for quick tests.
Hope this helps.
Regards,
Bill, N4QA
Offline
Thanks Bill ... I may have a defective board ... I can't seem to get any of the digital I/O to switch ... I've sent commands with Serial Port monitor rather than hyperterminal ... I'm also presuming that the muC control app does work, as it seems to work in resetting, turning the LED's on and off and in ADCs
Chris
Offline
I uninstalled, cleared files, and reloaded the muC software again, and also (probably important) reset the board with the push button on the side. That seems to have cleared things up, but not consistently. After using the muC for a bit, I seem to lose the ability to monitor and change the logic levels. I think the problem with my serial port communication stemmed from the muC software as well (I hadn't reset ... and I'm not sure what is happening, but it may be a problem in the way Visual Basic handles the USB port, since the muC is written in VB, or at least the source code is). Anyway, I'm comfortable with it being a software problem, as I can work through this
Thanks for the help
Chris Westland
Offline