Home Forum Latest Post
 Gabotronics Forum
Welcome Guest   
  • «
  •  Start 
  •  Prev 
  •  1 
  •  2 
  •  3 
  •  4 
  •  5 
  •  6 
  •  7 
  •  8 
  •  9 
  •  10 
  •  Next 
  •  End 
  • »
 Subject :Re:Xminilab connection with arduino.. 2017-08-17 22:53:24 
mailmad
Joined: 2015-12-29 04:23:16
Posts: 3
Location
Forum : XMEGA Xminilab
Topic : Xminilab connection with arduino

Thanks for your quick response, and yes, it works!!! Thanks again!

 

I am owner of Xprotolab and Xminilab, and I have to mention once again, I'm so excited for both devices!

Now I try to make my own version of oscilloscope based mainly on your Xminilab module. My goal is to make some small production of this unit.

Development estimated to last few months, and if  everything go as planned will be beneficial for both of us.

 

Suggestions/corrections:

May an example like this you mention (a small piece of code), could be a good idea to be added in Xscope manual.

A tiny tiny type error founded in page 33. "using the" repeated once more.

 

Sorry for babbling!

Regards!

IP Logged
 Subject :Re:Xminilab connection with arduino.. 2017-08-17 18:54:41 
ganzziani
Joined: 2012-04-02 15:42:39
Posts: 451
Location: Sarasota, FL
 
Forum : XMEGA Xminilab
Topic : Xminilab connection with arduino

As mentioned in the manual, the command is sent in ASCII format.
To check that things work, start by sending the 'a' command. I guess it would be something like Serial.write('a');
You should receive back the firmware version.

To set the scope to XY mode, you need to modify the MFFT variable by using command 'b', the MFFT variable is in Index 8.
Try this: Serial.write('b'); Serial.write(8); Serial.write(0x40);

IP Logged
Gabriel Anzziani
 Subject :Xminilab connection with arduino.. 2017-08-16 21:50:46 
mailmad
Joined: 2015-12-29 04:23:16
Posts: 3
Location
Forum : XMEGA Xminilab
Topic : Xminilab connection with arduino

I try to send commands from an arduino to Xminilab through serial connection, according to user manual.

Arduino C provide 2 commands adequate for serial communication (if I am not mistaken):

a) Serial.print(XXX); to send an ascii character.

b) Serial.write(XXX); to send a binary character.

If for example I want to set Xminilab to X-Y mode, what should I do?

Already I have try this:

Serial.print(8);

Serial.write(X);    // Where X all possible values from 0-255

Nothing change on display.

I should note that to translate voltage between Arduino and Xminilab, I place a voltage divider with a resistor 220Ω between Arduino Tx and Xminilab Rx, and a 330Ω between Rx and GND of Xminilab.

Also I have set speed to 115000. Parity and stop bit are by default the same like those of Xminilab.

What should I do?

IP Logged
 Subject :Littlebits Oscilloscope bit.. 2017-08-12 21:26:28 
ganzziani
Joined: 2012-04-02 15:42:39
Posts: 451
Location: Sarasota, FL
 
Forum : XMEGA Xprotolab
Topic : Littlebits Oscilloscope bit

The release date is still unknown, but a handful of units were manufactured, I am selling a few here:

https://www.ebay.com/sch/gabotronics/m.html

IP Logged
Gabriel Anzziani
 Subject :Re:Help! Corrupted my firmware. How to fix?.. 2017-07-28 03:54:55 
Statik
Joined: 2017-06-08 07:06:24
Posts: 4
Location
Forum : XMEGA Xprotolab
Topic : Help! Corrupted my firmware. How to fix?

Hi all,
Since there was no reply, I had to go really digging. I did end up fixing the problem. Here's what I did, just for reference for others.
First, I had to get a PDI capable programmer since I only had ISP capable ones. I ended up ordering the ZeptoProgII from here: https://www.mattairtech.com/index.php/zeptoprog-ii.html
It is compatible with Windows and Linux(which I use).
When it arrived, I downloaded the firmware from the website for my xprotolab-plain. I soldered 6 pins into the open port at the end of the xprotolab-plain, with the pins facing the same direction as the interface pins, and connected the ZeptoProgII to the xprotolab-plain using the included 6-pin connector. I followed the trace from the PDI pin on the xprotolab-plain to figure out which pin was pin 1, which is also the pin marked with a square on the silk screening. I then used the following commands:
avrdude -c avrisp2 -p x32a4u -U application:w:Xprotolab-Plain.hex:i
avrdude -c avrisp2 -p x32a4u -U eep:w:Xprotolab-Plain.eep:i

And it successfully updated the firmware and I have my Xprotolab-Plain working again!

Hope this helps anyone else in this situation.

Statik
IP Logged
 Subject :Single red LED flash.. 2017-07-25 10:50:10 
rjweber@Berkeley.edu
Joined: 2017-07-25 15:14:00
Posts: 1
Location
Forum : XMEGA Xprotolab
Topic : Single red LED flash

I've gone through two Xprotolab Plains now in two days.  They were running OK and then stopped.  When applying power through the USB port I get a single short red LED flash, then nothing.

I tried grounding pin 1 (square pad) on the six-pad connector on the end of the board to put the processor into reprogram mode, but still I only get the single red flash, not steady red LED on.  (Cannot find the pinout or number pattern of this connector anywhere in the manual.)

Are these fried?

 

IP Logged
 Subject :Re:Question: How to read frequenct off FFT plot?.. 2017-07-14 06:55:39 
Statik
Joined: 2017-06-08 07:06:24
Posts: 4
Location
Forum : XScopes PC Interface
Topic : Question: How to read frequenct off FFT plot?

For anyone who is wondering about this, here is what I have figured out:

The FFT frequency span AND the AWG sweep function ranges are both set by the current timescale of the oscilloscope. I made the following chart during testing:

Wavegen                                    FFT Dispay             
time/div     Range Shown       Min prod    Max prod     f/div        f range     f/point
8us/div            -             000000      125000      125000       1000000     7812.5
16us/div     000000-996030       000000      125000       62500        500000     3906.25
32us/div     000000-498015       000000      125000       31250        250000     1953.125
64us/div     000000-249007       000000      125000       15625        125000      976.5625
128us/div    000000-124440       000000       62220        7777.5       62220      486.09375
256us/div    000000- 62220       000000       31110        3888.75      31110      243.046875
500us/div    000000- 31110       000000       16000        2000         16000      125
1ms/div      000000- 15937.5     000000        7968.75     996.09375     8000       62.255859375
2ms/div      000000-  7968.75    000000        4000        500           4000       31.25
5ms/div      000000-  3984.38    000000        1600        200           1600       12.5
10ms/div     000000-  1593.75    000000         800        100            800        6.25
HALF DISPLAY (4 divs only, 32 points per div)
20ms/div     000000-  1593.75    000000         800        200            800        6.25
50ms/div     000000-   796.875   000000         320         80            320        2.5
0.1s/div     000000-   318.75    000000         ??          40            160        1.25
0.2s/div     000000-   159.375   000000         79.05       20             80        0.625
0.5s/div     000000-    79.6875  000000         31.45        8             32        0.25
1s/div       000000-    31.875   000000         15.9375      4             16        0.125
2s/div       000000-    15.9375  000000                                     8
5s/div       000000-     7.905   000000                                     3.2
10s/div      000000-     3.1875  000000
20s/div      000000-     1.53    000000
50s/div      000000-     0.765   000000

 

If you look at the chart in a monospace font, it looks ok

 

Statik

IP Logged
 Subject :Help! Corrupted my firmware. How to fix?.. 2017-07-14 06:33:49 
Statik
Joined: 2017-06-08 07:06:24
Posts: 4
Location
Forum : XMEGA Xprotolab
Topic : Help! Corrupted my firmware. How to fix?

Hi all,

I'm currently in computer engineering at a Dalhousie University and we use an ATMega644A in our projects. They use a USB loader that programs the microcontroller that I use avrdude in Eclipse to program. I'm also a Linux Mint 18.2 user. I was trying to program another microcontroller I had found and accidentally had my xprotolab-plain also connected at the same time. Now the xprotolab does not function. I have the hex and eep files here but I'm not sure how to proceed.

The command that eclipse ran when both devices were connected was:

Launching /usr/bin/avrdude -p8535 -cavrftdi -Uflash:w:AT90LS8535Test.hex:a
Output:

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9303 (probably 8535)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "AT90LS8535Test.hex"
avrdude: input file AT90LS8535Test.hex auto detected as Intel Hex
avrdude: writing flash (104 bytes):

Writing | ################################################## | 100% 0.41s

avrdude: 104 bytes of flash written
avrdude: verifying flash memory against AT90LS8535Test.hex:
avrdude: load data flash data from input file AT90LS8535Test.hex:
avrdude: input file AT90LS8535Test.hex auto detected as Intel Hex
avrdude: input file AT90LS8535Test.hex contains 104 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.10s

avrdude: verifying ...
avrdude: 104 bytes of flash verified

avrdude done.  Thank you.

avrdude finished

 

With the USB cable only connected to the xprotolab-plain, I tried running:

avrdude -px32a4u -cflip2 -U application:w:Xprotolab-Plain.hex:i

avrdude: Error: No matching USB device found
avrdude: AVR device initialized and ready to accept instructions

Reading |                                                    | 0% 0.00savrdude: error reading signature data for part "ATxmega32A4U", rc=-1
avrdude: error reading signature data, rc=-1

avrdude done.  Thank you.

So now I'm stuck. Any help appreciated.

 

Statik

IP Logged
 Subject :Re:measuring mobile battery via Xprotolab.. 2017-07-05 07:44:03 
ethan147
Joined: 2017-07-05 12:40:55
Posts: 1
Location
Forum : Project Ideas
Topic : measuring mobile battery via Xprotolab

Driven Pixel: The Pixie is a shading LED module, enabling an outside controller to change its shading and brilliance powerfully.

 

Chainable: The module is composed with the goal that you can chain a large portion of them and control every one separately. On the off chance that you know NeoPixels, this idea ought to be clear, yet in the event that you don't, envision you need to assemble a venture that requires 50 LEDs to be exclusively controlled. Gullibly, you would need to control each on of them separately, at that point associate every one of them independently to a controller.

IP Logged
Cash For Cars Culver City
 Subject :Question: How to read frequenct off FFT plot?.. 2017-07-04 03:54:22 
Statik
Joined: 2017-06-08 07:06:24
Posts: 4
Location
Forum : XScopes PC Interface
Topic : Question: How to read frequenct off FFT plot?

Hi all,

My Xprotolab Plain arrived today and I have the XScope software running on Linux Mint 18.1 flawlessly. I am wondering how one reads the frequency off the FFT plot? The manual mentions that FFT is the only way to do a frequency read on the analog inputs, so, how do you get the numbers?

 

Thanks!

Statik

IP Logged
 Subject :Re:The xMega ADC.. 2017-07-01 07:08:25 
joeroot
Joined: 2017-07-01 12:05:59
Posts: 1
Location
Forum : General Electronics
Topic : The xMega ADC

Hi Torby!

I took a look at the register setup but I can't see what's wrong, Try this:

Change:

//PORTB.PIN4CTRL = (3<<3);
to:
PORTB.PIN4CTRL = 0x07; // Digital Input Disable on pin PB4
IP Logged
writer at Accounting Assignment Help
 Subject :Re:Driver install Error.. 2017-05-17 20:39:05 
mahesh150
Joined: 2017-05-18 01:36:27
Posts: 1
Location: jaipur
Forum : AVR Xmegalab
Topic : Driver install Error

When i connect it to interestingly it is "XMEGA Oscilloscope", then i attempt to introduce the driver and get the portrayed blunder and the gadget changes to "obscure gadget".

Attempted the windows boot alternative to permit unsigned drives, yet nothing changed.

I am introducing Win XP mode and i am going to attempt it.
IP Logged
Taxi service in jaipur
 Subject :Re:serious issues after firmware upgrade.. 2017-05-16 00:39:15 
matthijs
Joined: 2014-05-05 03:29:03
Posts: 2
Location
Forum : XMEGA Xminilab
Topic : serious issues after firmware upgrade

I have the same device (Xminilab Portable, hardware version 1.1 written on the PCB) and just upgraded to 2.40 without problems, everything still works as before. Some thoughts:

- Did you use the 1.1 version of the firmware? There is also an 1.11 version inside the zip, which I presume will cause problems.

- Did you upload the .hex firmware and .eep EEPROM file?

IP Logged
 Subject :A few questions regarding Xprotolab Plain.. 2017-04-03 11:18:50 
l.ramirez
Joined: 2017-05-25 23:54:38
Posts: 1
Location
Forum : XMEGA Xprotolab
Topic : A few questions regarding Xprotolab Plain

As a beginner in electronics I couldn't find better specs for a comparable price on similar oscilloscope models but had a couple questions regarding the Xprotolab Plain people here may be able to help me with:

1.- According to the manual it can measure up to +20 V signals but only goes as low as -14 V, what's the reason for this asymmetry?

2.- Is 200 KHz for analog signals the absolute highest it can go while measuring?, is there a way to make it go higher?

IP Logged
 Subject :Re:serious issues after firmware upgrade.. 2017-03-15 17:28:48 
RootlessAgrarian
Joined: 2013-11-29 00:09:38
Posts: 3
Location
Forum : XMEGA Xminilab
Topic : serious issues after firmware upgrade

Hi Gabriel...? Any update on this issue?

Is my minilab capable of running 2.40? Is it too old? Is there any way I can upgrade it to match whatever changes you have made to current version?
IP Logged
 Subject :Are you still supporting Winduhs XP SP3 or are there some archives I c.. 2017-03-12 20:07:37 
Lee Wilkerson 777
Joined: 2015-08-18 22:15:04
Posts: 3
Location
Forum : Oscilloscope Watch
Topic : Are you still supporting Winduhs XP SP3 or are there some archives I could search?

Subject :Are you still supporting Winduhs XP SP3 or are there some archives I could search?

When I attempt to run Zadig, I get an error message (Zadig Error.jpg) regarding msvcrt.dll 3 times, but it still claims success (Zadig But Still I get.jpg and Zadig.log).

After that when I attempt to run xscope.exe, I get another error regarding Qt5Gui.dll. See 86ff_appcompat.txt.

IP Logged
 Subject :Smaller buttons on the XScope screen?.. 2017-03-12 19:20:30 
Lee Wilkerson 777
Joined: 2015-08-18 22:15:04
Posts: 3
Location
Forum : Oscilloscope Watch
Topic : Smaller buttons on the XScope screen?

Those of us who are fortunate enough or geeky enough to have their computers connected to 40" screens don't really need buttons so large... Just a suggestion. BTW, I do love the program.

IP Logged
 Subject :Linux 32 bit version in future?.. 2017-03-12 19:17:41 
Lee Wilkerson 777
Joined: 2015-08-18 22:15:04
Posts: 3
Location
Forum : Oscilloscope Watch
Topic : Linux 32 bit version in future?

Since both of my 64 bit machines recently died, I must endure the bleary screen of Winduhs for running XScope. I so truly love the crisp screens of Mint. Hint, hint, please?

IP Logged
 Subject :Re:Brand new Xprotolab, auto-resetting every 5-7 seconds.. 2017-03-06 16:52:29 
bjelokur
Joined: 2017-03-05 13:16:21
Posts: 2
Location
Forum : XMEGA Xprotolab
Topic : Brand new Xprotolab, auto-resetting every 5-7 seconds [SOLVED]

Thanks Gabriel. That did solve the problem. Using FW 2.44 now.
IP Logged
 Subject :Re:serious issues after firmware upgrade.. 2017-03-05 14:22:57 
RootlessAgrarian
Joined: 2013-11-29 00:09:38
Posts: 3
Location
Forum : XMEGA Xminilab
Topic : serious issues after firmware upgrade

Ciao Gabriel, thank you for responding so quickly! In answer to your question, the display is green in colour. I just took the case apart and on the top surface of the board, above the display screen, it says Rev 1.1 -- so this is a very early unit.

xminilab

xminilab screen



It seems unlikely that it will ever run firmware 2.40, being so old. So I fear I have broken it, because even the "older hardware" firmware version I have will not flash so there is no going back (sigh). Do you have the hex and eep files still for this very early generation? Can I upgrade it to a later rev by swapping parts, or were there board design changes as well? I may just have to grit my teeth and buy an up-to-date model :-)

IP Logged
Page # 
  • «
  •  Start 
  •  Prev 
  •  1 
  •  2 
  •  3 
  •  4 
  •  5 
  •  6 
  •  7 
  •  8 
  •  9 
  •  10 
  •  Next 
  •  End 
  • »


Powered by ccBoard