Warning, the expiremental version has bugs, Guaranteed. I know hserout is broken which probably means hserin is broken, which probably means interrupts are broken. I’m making these EXP version available so I can get feed back on bugs and test some new features. This release was a major overhall of the token handler and stack handler subsystems which is why I suspect a lot will be broken and why I’m asking for some help testing it out. If you are not in the mood to deal with bugs please DO NOT USE the expiremental version. If you don’t mind helping me out with real world testing please do.
I will give it a try! One thing that would make this easier is if there was an easy way to have two versions installed. When a version is already installed, you only have the choices to Modify, Repair or Remove. It would be nice to have an option to Install to a different directory. That way more people could simply install a second copy. And give you feedback. Just a thought.
Question: Does the current semi released .7 version use the same WTIMER functionality for HSERVO as the EXP? ie will my interrupts that grab your timer values work?
Ok, I have it installed and my version of the BRAT does not compile: I receive the following error:
Tokenizing...
C:\PROGRA~1\BASICM~1\BASICA~2\bin\hbasic.lib: Assembler messages:
C:\PROGRA~1\BASICM~1\BASICA~2\bin\hbasic.lib:9098: Error: invalid operands
C:\PROGRA~1\BASICM~1\BASICA~2\bin\ld.exe : cannot open c:\users\kurt\desktop\lynxmotion\bratwithremotesave.o: No such file or directory
EDIT: I forgot to mention that this file is the same one I sent you an email last night
If you choose “custom” when you install you can select a different directory. However that only seems to work with the first install. if there is already a version installed InstallShield doesn’t give the option. I’m still trying to figure out InstallShield. Ugh.
My Rover with intercept code compiles, but so far does nothing. My LCD does not display my welcome message nor do the wheels move at all when I try moving the joystick on the Laser 6 controller.
Not sure yet if this is: hanging somewhere or not receiving the interrupts, or hservo not working or … will try to localize down some.
Lets go to PM after each time you post a specific problem. That way others won’t post the same problems but we won’t spam this thread with back and forth messages about a single problem.
Sounds good. I PMed you a second ago. Right now it looks like serout might be faulting. At first I thought it was a call/return with parameters, but now I think it is a serout;
In this sample program:
[code]’ Constant definitions
TRUE con 1
FALSE con 0
SEETRON con 1
LCDPIN con p15
;#endif #ifdef SEETRON
;LCD_BAUD con n9600
;LCD_BAUD con 206
LCD_BAUD con n2400 #else
LCD_BAUD con i2400 #endif
; variables for LCD… Not sure how to pass an array to a gosub so.
LCD_String var byte(17)
; Initialization code
sound 9,[50\3960]
low 13
gosub LCD_Init
Sound 9,[50\4450]
low 12
foo
goto foo
LCD_Init
; make sure SerLCD has a chance to finish initializing after power-up
; Reset to 9600 and powerup... - Uncomment if having problems with LCD.
;pause 100
;serout LCDPIN, I9600, [0x12]
Pause(1000)
; Now lets try setting it to 2400 baud. - uncomment if having problems
;Serout LCDPIN, I9600, [0x7c] ; 124, <control k>
;pause 2
;Serout LCDPIN, I9600, [11] ; 124, <control k>
; Output the clear screen command
gosub LCD_WriteCommand[1] ; // Clear the screen
Pause(5)
return
cmd var byte
LCD_WriteCommand[cmd] #ifdef USEHSERIAL
hserout [0xfe]
pause 10
hserout [cmd] #else
;serout LCDPIN, LCD_BAUD, [0xfe]
pause 10
;serout LCDPIN, LCD_BAUD, [cmd] #endif
return
[/code]
The code will make it to the second beep, but if I uncomment the serout’s it resets the processor.
I was made aware that there is a problem with the NAP command on the Atom Pro with 8.0.1.7. I don’t know what the problem is except it does not work.
Update… With the Atom the NAP 4 command resulted in a 288mS delay. A NAP 4 on the Pro is an 8mS delay. When we tried NAP 144 for the 288mS delay it still didn’t fix the PS2 flaky connection problem, so it looks as if NAP is broken in 8.0.1.7.
The Atom Pro manual should be updated with the correct underlying analog pin numbers on the Pro28. As per AcidTech
Pro28:
P0 = AN0
P1 = AN1
P2 = AN2
P3 = AN3
P16 = AN7
P17 = AN6
P18 = AN4
P19 = AN5
Make sure you have the status bar showing (view menu). Then the line and column number of the cursor will be shown toward the bottom right of the IDE window.
There is no button, simply some text fields. Some of the fields show if the caps lock is on, likewise for num lock and scroll lock. To the right of those status fields will be an area that shows something like:
Ln 1, Col 1
This is you are on Line 1 in column 1… Will update as you move the text cursor around in your source window…
