fs: 50kHz
I make transformers myself.
%1 voltage regulation.
|
1
on: December 15, 2018, 03:48:00 15:48
|
||
| Started by devfirat - Last post by devfirat | ||
|
2
on: December 15, 2018, 11:33:14 11:33
|
||
| Started by biko4710 - Last post by Xwing | ||
|
Simplify3D 4.1.1 release note, installation and patch coming soon.
https://www.simplify3d.com/software/release-notes/ |
||
|
3
on: December 15, 2018, 08:50:29 08:50
|
||
| Started by metal - Last post by MetaMetal | ||
|
xc32 v2.15 is out.
medicine works fine. |
||
|
4
on: December 14, 2018, 04:49:49 16:49
|
||||||
| Started by SimonS - Last post by SimonS | ||||||
|
||||||
|
5
on: December 14, 2018, 01:55:31 13:55
|
||
| Started by vbcoder - Last post by vbcoder | ||
|
Thanks a lot Top!
That was exactly the problem. Glad I had you to get it for me  I attached the code after fixing it by enabling the interrupts() and it now works! |
||
|
6
on: December 14, 2018, 09:47:14 09:47
|
||
| Started by vbcoder - Last post by Top | ||
|
You may have noticed that if you use the internal Arduino compiler, i.e. Arduino AVR (Proteus), then your project works fine but if you use the external Arduino compiler then your project hangs.
The reason for this is that the implementation of the TimerOne library in Proteus re-enables interrupts before calling your interrupt handler. If interrupts are not enabled when you call Wire.endTransmission() then the code can hang waiting for the twi_state flag to update. To fix this, either re-enable interrupts at the start of your ISR, or, set a flag in your ISR and do the work in your main loop. |
||
|
7
on: December 14, 2018, 08:32:12 08:32
|
||
| Started by vbcoder - Last post by vbcoder | ||
|
Thanks Top again.
I am the person who wrote the firmware. I made the steps you showed me and unfortunately it hangs at either START 2 OR START 25 I attached the project after adding the code inside and compiled it with no issues. I really can't figure out what may cause that issue |
||
|
8
on: December 14, 2018, 02:02:49 02:02
|
||
| Started by mr_byte31 - Last post by CocaCola | ||
|
Why would you use barometric sensor? I wouldn't and that was what I was pointing out... For clarity, I should have also quoted an007_rld who suggested the barometric sensor as my reply was mostly towards that sensor approach and how it wouldn't resolve to the degree of accuracy, especially when combined with my agreement with you that there should be sensors on the boom and vehicle... As I said previous, if there is a $100 device already commercially designed for this application, I would not waste my time re-creating the wheel and assuming liability vs just spending $100 on the existing device and calling it a day... I hope that clarifies it... |
||
|
9
on: December 13, 2018, 10:08:05 22:08
|
||
| Started by mr_byte31 - Last post by Parmin | ||
|
Although I agree, if one is using a barometric pressure sensors all around with a +/- of 10cm for both I don't believe you can resolve to 1 degree of accuracy reliably as the error compounds across both measurements, especially true since the truck's length to height isn't enough to mitigate the +/- 10cm reading tolerance of the sensors well enough... Why would you use barometric sensor? Accelerometers are great for angle measurement. A lot are sensitive enough for even less than a quarter of a degree angle against the horizon. Posted on: 14 December 2018, 06:07:03 - Automerged The gyroscopic feature of most accelerometer is sensitive down to 200 counts per degree |
||
|
10
on: December 13, 2018, 04:24:40 16:24
|
||
| Started by vbcoder - Last post by Top | ||
|
Rename SDA to IO2 and SCL to IO3.
Right-click U3 and select Edit Source File. In New Firmware Project dialog click OK. Copy source code into the main.ino window. Start simulation, click Virtual Terminal and press *. |
||