Last post by MorganS - Today at 01:48 am
4-20 is used because anything less than 4 can be used as an error condition. You should be able to read valid values in the 4-20 range and report "not connected" when it drops below 4.
It's analog - you can't expect it to ever equal zero but more time and expense can get it closer to zero.
I wrote a load of stuff for a 6809 30? years ago which had to deal with loads of asynchronous interrupts.
So I had to make the little routines re-entrant.
Method was to add a local variable space to the stack pointer, and use stack offset backwards from that for the locals Any new interrupt grabbed it's own bit of stack in the same way , and as they finshed, all released their stack areas. Plus push and pop for the registers I needed to use.
Fortunately the interupts were sufficiently infrequent so as not to run out of stack.
In assembly, of course.
Last post by MorganS - Today at 01:45 am
Do you know where the target areas are in advance or does the vision system have to read the table markings too?
This is starting to sound like a relatively advanced vision system. Beyond the capability of a plain Arduino. Maybe a Pixy camera can help but I suspect that you'll be going for a high-end image-recognition library on a Rasberry.
Can you fix your indenting. The code is hard to follow. Use Tools, Auto Format or ctrl-t.
Last post by justone - Today at 01:40 am
Looks like you don 't have the 12v and the 5v grounds connected together.
Wow, I haven't hooked a BIOS interrupt in over 20 years.
You really want to feel old?
I might have been in diapers back then.
Or nonexistent, depending on exactly how over it is.
Last post by surbyte - Today at 01:39 am
hombre preguntas el 25 y el 26 ya estas molesto porque nadie responde. Se paciente!!
Yo simplemente con ls dos lineas de tu post#6 no se que responderte.
Arrancaste con un problema de TM1638_COLOR_NONE que era una simple variable que debió estar definida en la librería TM1638.h con un #define TM1638_COLOR_NONE 0 supongo...
y ahora sales con una pregunta que requiere entender todo tu código sin mayor explicación que dos líneas.
Esmérate un poco mas y repito, se paciente que nadie tiene obligación de responder y tu menos de enojarte.
Sino lee las normas del foro en lo que a este tema respecta.
Which libraries are you planning on using? I can take some time during the next couple days to look them over for interrupts and potential resource sharing issues.
Last post by JakeSoft - Today at 01:36 am
i sent the code in ur message, it's quite long.
OFC, any suggestion to make it better is more than welcome.
The base idea is:
After turning on the Latching button, the arduino board prepares to be used, when it's ready a sound is played.
Now with a momentary switch you can turn on the lightsaber (one click) or access the menu (hold the button for a little while).
In the menu you can change color of the blade, flickering effect, FoC, sound font, sound volume, clash/swing sensitivity, and i think is all.
I took a look at it. Where is PLAY_DURATION defined? You are using it as a delay after some of your sound play commands but I don't see that it is actually defined anywhere.
Did you push the button?